Mar <var data-var='date'>19</var>, <var data-var='time'>12:09</var> EDT Resolved - This incident has been resolved.Mar <var data-var='date'>19</var>, <var data-var='time'>12:07</var> EDT Update - After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We apologize for any inconvenience or disruption.Mar <var data-var='date'>19</var>, <var data-var='time'>11:55</var> EDT Monitoring - We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. We are continuing to monitorMar <var data-var='date'>19</var>, <var data-var='time'>11:30</var> EDT Update - We are working to resolve an issue with delayed processing of requests to the Dodgeball services.Mar <var data-var='date'>19</var>, <var data-var='time'>11:13</var> EDT Identified - We are currently investigating performance of the Dodgeball service.

Dodgeball Checkpoint Latency

Mar <var data-var='date'>16</var>, <var data-var='time'>14:07</var> EDT Resolved - After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.Mar <var data-var='date'>16</var>, <var data-var='time'>13:51</var> EDT Monitoring - A fix has been implemented and we are monitoring to ensure services are operating correctlyMar <var data-var='date'>16</var>, <var data-var='time'>13:45</var> EDT Investigating - We are currently investigating elevated errors on API endpoints

Increased errors with Core Transactional API

Mar <var data-var='date'>12</var>, <var data-var='time'>21:00</var> EDT Completed - The scheduled maintenance has been completed.Mar <var data-var='date'>12</var>, <var data-var='time'>20:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Mar <var data-var='date'> 6</var>, <var data-var='time'>14:24</var> EST Scheduled - On March 12th, 2026, from 8:00 PM to 9:00 PM EST, our systems will undergo scheduled system maintenance. We will be performing an upgrade to our message broker for DodgeballHQ. Our team will be closely monitoring the activity throughout the maintenance window

Dodgeball maintenance

Feb <var data-var='date'>26</var>, <var data-var='time'>21:00</var> EST Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>26</var>, <var data-var='time'>19:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>20</var>, <var data-var='time'>09:20</var> EST Scheduled - On February 26th, 2026, from 7:00 PM to 11:00 PM EST, our systems will undergo scheduled database maintenance. We will be performing a follow-up action for a database version upgrade for DodgeballHQ. Our team will be closely monitoring the activity throughout the maintenance window.

Dodgeball Maintenance

Feb <var data-var='date'>26</var>, <var data-var='time'>13:44</var> EST Resolved - The storage issue affecting the Dodgeball production instance has been fully resolved. Capacity has been restored and systems are operating normally. We are no longer observing elevated error rates for customers using Dodgeball. Thank you for your patience while we worked to resolve this issue.Feb <var data-var='date'>26</var>, <var data-var='time'>11:59</var> EST Monitoring - The engineering team has successfully resolved the storage issue affecting the Dodgeball production PostgreSQL instance. Capacity has been restored and the system is now operating normally. At this time, we are not observing any elevated error rates for customers using Dodgeball. We will continue to monitor the system closely to ensure stability. Further updates will be provided if necessary.Feb <var data-var='date'>26</var>, <var data-var='time'>11:45</var> EST Investigating - We are currently investigating an issue affecting customers using Dodgeball. The production database backing Dodgeball has reached critically low available storage, which is expected to result in elevated error rates. Customers may begin experiencing errors within the next 10 minutes as the system’s ability to process requests degrades. Our engineering team is actively investigating and working to restore normal capacity as quickly as possible. We will provide further updates as more information becomes available.

Dodgeball Production Instance Storage Critically Low

Feb <var data-var='date'>25</var>, <var data-var='time'>16:52</var> EST Resolved - After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.Feb <var data-var='date'>25</var>, <var data-var='time'>15:35</var> EST Monitoring - Service has resumed and we are monitoring for further impact. We apologize for any inconvenience this has causedFeb <var data-var='date'>25</var>, <var data-var='time'>14:48</var> EST Identified - We are working to resolve an issue with processing of Checkpoints that is causing latency and errors for requests to the Dodgeball services.Feb <var data-var='date'>25</var>, <var data-var='time'>14:18</var> EST Investigating - We are currently investigating performance of the Dodgeball service.

Feb <var data-var='date'>23</var>, <var data-var='time'>23:00</var> EST Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>23</var>, <var data-var='time'>19:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>16</var>, <var data-var='time'>17:38</var> EST Scheduled - On February 23rd, 2026, from 7:00 PM to 11:00 PM EST, our systems will undergo scheduled database maintenance. We will be performing a database version upgrade for DodgeballHQ. Our team will be closely monitoring the activity throughout the maintenance window

Dodgeball Database Maintenance

Feb <var data-var='date'>18</var>, <var data-var='time'>11:00</var> EST Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>18</var>, <var data-var='time'>10:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>13</var>, <var data-var='time'>10:06</var> EST Scheduled - On February 18th, 2026, from 10:00 AM to 11:00 AM EST, our systems will undergo scheduled maintenance. We will be performing dependency upgrades to improve overall security and performance. Our team will be closely monitoring the activity throughout the maintenance window If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our Support team will be happy to assist.

System Maintenance

Feb <var data-var='date'>17</var>, <var data-var='time'>11:00</var> EST Completed - The scheduled maintenance has been completed.Feb <var data-var='date'>17</var>, <var data-var='time'>10:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Feb <var data-var='date'>10</var>, <var data-var='time'>16:56</var> EST Scheduled - On February 17th 2026 from 10 am ET to 11am ET, our systems will undergo scheduled Annual Rotation of Mastercard Network Token keys. Note that while transactions attempted with a Mastercard network token during this rotation will not be rejected, attempts to provision a network token with a Mastercard card will not succeed during the key rotation portion of this activity. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will be happy to assist.

Mastercard Network Tokenization Scheduled Maintenance

Feb <var data-var='date'> 5</var>, <var data-var='time'>12:01</var> EST Resolved - After monitoring the system post-deploy, we’re no longer seeing errors related to credits referencing Capture transactions, and processing has returned to normal. Thank you for your patience.Feb <var data-var='date'> 5</var>, <var data-var='time'>11:25</var> EST Monitoring - We’ve deployed a revert to address the issue where credit transactions referencing Capture transactions were failing. We’re actively monitoring to ensure credit requests referencing Captures are processing as expected. At this time, we’re not seeing further errors related to this behavior.Feb <var data-var='date'> 5</var>, <var data-var='time'>10:56</var> EST Investigating - We are currently investigating an issue where credit transactions referencing Capture transactions are failing in production. Some customers may see errors when attempting to issue credits against Capture transactions. Capture transactions themselves are processing successfully. Our engineering team is actively investigating this behavior to determine the cause and confirm whether this is a regression or an unintended change. We will provide updates as soon as more information is available.

Credits Referencing Capture Transactions Failing

Feb <var data-var='date'> 4</var>, <var data-var='time'>14:56</var> EST Resolved - This incident has been resolved.Feb <var data-var='date'> 4</var>, <var data-var='time'>14:52</var> EST Monitoring - We are no longer seeing errors at this time, and the issue appears to have subsided. We are working with Payflow Pro to identify the root cause. Our team continues to monitor the situation closely to ensure stability. Please continue to follow our StatusPage for the latest updates.Feb <var data-var='date'> 4</var>, <var data-var='time'>13:15</var> EST Investigating - Spreedly has detected an issue that is affecting multiple customers using Payflow Pro where some transactions fail with the error: “Invalid Request. Malicious string found in XML document”. While we are providing an early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact and will provide an update as soon as more details are available. Thank you for your patience.

Multiple merchants using Payflow Pro with experiencing intermittent payment failures

Jan <var data-var='date'>27</var>, <var data-var='time'>15:12</var> EST Resolved - We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We apologize for any inconvenience or disruption.Jan <var data-var='date'>27</var>, <var data-var='time'>14:59</var> EST Investigating - Spreedly has detected an issue related to a dodgeball component experiencing a partial outage. While we are providing an early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact and will provide an update as soon as more details are available. Thank you for your patience.

Dodgeball: Elevated levels of latency for Checkpoints

Jan <var data-var='date'>27</var>, <var data-var='time'>14:29</var> EST Resolved - After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected. We are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.Jan <var data-var='date'>27</var>, <var data-var='time'>14:25</var> EST Monitoring - We’ve implemented a fix and stabilized the 3DS2 Global transactions. Our team is monitoring the situation closely to ensure there are no additional impacts. Please continue to follow our StatusPage for the latest update.Jan <var data-var='date'>27</var>, <var data-var='time'>14:08</var> EST Investigating - Spreedly has detected an issue potentially resulting in a high number of pending 3DS2 Global transactions. While we are providing an early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact and will provide an update as soon as more details are available. Thank you for your patience.

3DS2 Global Transactions Pending

Jan <var data-var='date'>21</var>, <var data-var='time'>23:00</var> EST Completed - The scheduled maintenance has been completed.Jan <var data-var='date'>21</var>, <var data-var='time'>12:47</var> EST Update - The scheduled database maintenance window on January 21st, 2026 has been extended. Maintenance is now expected to continue until 11:00 PM EST. Our team continues to closely monitor the activity and work to complete the upgrades as quickly as possible. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our Support team will be happy to assist.Jan <var data-var='date'>21</var>, <var data-var='time'>08:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Jan <var data-var='date'>20</var>, <var data-var='time'>14:23</var> EST Scheduled - On January 21st, 2026, from 8:00 AM to 2:00 PM EST, our systems will undergo scheduled database maintenance. We will be upgrading our database cluster to apply routine updates and improve overall performance. Our team will be closely monitoring the activity throughout the maintenance window. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our Support team will be happy to assist.

Database Maintenance

Jan <var data-var='date'> 9</var>, <var data-var='time'>14:10</var> EST Resolved - After a period of monitoring, we have confirmed that the issue has been resolved and systems are operating normally. If you continue to experience any issues, please reach out to Support.Jan <var data-var='date'> 9</var>, <var data-var='time'>14:07</var> EST Monitoring - A fix has been deployed and we are seeing systems recover. We will continue to monitor to ensure stability and will provide further updates as needed.Jan <var data-var='date'> 9</var>, <var data-var='time'>13:52</var> EST Update - We are continuing to investigate this issue.Jan <var data-var='date'> 9</var>, <var data-var='time'>13:46</var> EST Investigating - We are currently investigating this issue.

Higher error rates on when using Dodgeball runtime

Dec <var data-var='date'>27</var>, <var data-var='time'>19:00</var> EST Resolved - Between 7:00 PM EST on Saturday, December 27th, and 1:00 AM EST on Sunday, December 28th, we identified a period of higher-than-normal latency caused by a pre-planned customer event that resulted in a significant traffic spike. Although we did not observe any service failures or timeouts, our systems experienced degraded service due to the increased latency. Systems recovered quickly once peak traffic subsided and are now operating normally. We expect performance to remain stable moving forward.

Increased Latency

Dec <var data-var='date'>16</var>, <var data-var='time'>16:56</var> EST Resolved - Between 3:59 and 4:03 EST, customers may have experienced degraded performance when processing transactions that required 3D Secure (3DS) authentication via our Global 3DS service. Performance has since returned to normal, and no further impact has been observed. If you have any questions about potential impact to your transactions during this time window, please reach out to Spreedly Support for assistance.

Delayed Processing of Some 3DS Global Transactions

Dec <var data-var='date'>10</var>, <var data-var='time'>15:04</var> EST Resolved - Our team has completed the backfill process, and all missing transaction data has now been fully restored in Spreedly reporting. Transaction reporting is up to date and functioning as expected. All primary processing systems continued to operate normally throughout this incident, and no transaction processing impact occurred.Dec <var data-var='date'>10</var>, <var data-var='time'>09:42</var> EST Monitoring - We have identified and fixed the issue that was causing some transaction data to be missing from Spreedly reporting. Our team is now working on backfilling the missing reporting data to ensure completeness and accuracy. All primary processing systems continue to operate normally, and there is no impact to transaction processing.Dec <var data-var='date'>10</var>, <var data-var='time'>01:53</var> EST Update - Our team continues to investigate the root cause of the missing transaction data appearing in Spreedly reporting. All primary datastores and transactional processing are functioning normally, and there is no indication of data loss at the source. The issue appears to be isolated to the reporting ingestion process.Dec <var data-var='date'> 9</var>, <var data-var='time'>10:58</var> EST Investigating - We are investigating an issue where roughly 30–40% of transactions are not appearing in Spreedly reporting since 12/03. Primary datastores and secondary services show no data loss, indicating the issue lies within the reporting ingestion process. Please reach out to <a href="https://support.spreedly.com/">Spreedly Support</a> if you need assistance.

Transaction Reporting Degraded

Dec <var data-var='date'> 3</var>, <var data-var='time'>10:00</var> EST Completed - The scheduled maintenance has been completed.Dec <var data-var='date'> 3</var>, <var data-var='time'>08:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'>25</var>, <var data-var='time'>11:29</var> EST Scheduled - On December 3rd, 2025, from 8:00 AM to 10:00 AM EST, our systems will undergo scheduled system maintenance. We will gradually transition traffic related to Gateway Transaction processing to increase system resiliency and improve overall performance. Our team will be closely monitoring the activity throughout the maintenance window. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our support team will be happy to assist.

Nov <var data-var='date'>18</var>, <var data-var='time'>10:00</var> EST Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>18</var>, <var data-var='time'>07:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.Nov <var data-var='date'>13</var>, <var data-var='time'>15:46</var> EST Scheduled - On November 18, 2025, from 7:00 AM to 10:00 AM EST, our systems will undergo scheduled database maintenance. We will be upgrading our database cluster to apply routine updates and improve overall performance. Our team will be closely monitoring the activity throughout the maintenance window. If you experience any unexpected impacts during this time, please <a href="https://support.spreedly.com/hc/en-us/requests/new">reach out</a> and our Support team will be happy to assist.

Oct <var data-var='date'>20</var>, <var data-var='time'>16:22</var> EDT Resolved - After closely monitoring and confirming that all systems are stabilized and functioning as expected, this incident is considered resolved. No further customer impact is expected.Oct <var data-var='date'>20</var>, <var data-var='time'>11:41</var> EDT Identified - The major AWS outage on October 20, 2025, has been largely resolved for most affected services, though some residual issues may persist. Spreedly’s core platform remains stable and fully available. However, due to downstream impact from the AWS outage, some of Spreedly’s indexing endpoints and callback processing are experiencing delays. This is related to dependencies on third-party systems that were affected by the outage and are still undergoing recovery. As a result, you may continue to see intermittent latency or delayed responses for API requests involving these systems. We are actively monitoring the situation as AWS and its downstream services continue recovery efforts. For ongoing updates, please refer to the AWS status page <a href="https://health.aws.amazon.com/health/status">here</a>

AWS Outage Impact

Sep <var data-var='date'>30</var>, <var data-var='time'>15:45</var> EDT Resolved - The incident impacting operations involving payment methods has been resolved. All services are now operating normally. During routine database maintenance, we encountered issues that affected tokenization and transactions using payment methods. We’ll share more details in the upcoming post-mortem.Sep <var data-var='date'>30</var>, <var data-var='time'>15:07</var> EDT Monitoring - We have identified and resolved the issue and and monitoring for any additional impact.Sep <var data-var='date'>30</var>, <var data-var='time'>14:55</var> EDT Identified - We are implementing a mitigation that should restore the ability to perform new tokenizations and operations on those payment methods. Some functionality, such as fingerprinting, may remain limited. Use of vaulted payment methods may remain limited. We’ll provide updates as we progress.Sep <var data-var='date'>30</var>, <var data-var='time'>14:25</var> EDT Update - Currently we are experiencing issues with services that use payment methodsSep <var data-var='date'>30</var>, <var data-var='time'>14:22</var> EDT Investigating - We are currently investigating a high number of 500 errors

Core 500s

Sep <var data-var='date'>19</var>, <var data-var='time'>13:46</var> EDT Resolved - At 1:08 PM, 3DS provider, Seglan, deployed changes to address the issue. After a period of monitoring, we’ve observed normal performance and are declaring this incident resolved.Sep <var data-var='date'>19</var>, <var data-var='time'>11:53</var> EDT Investigating - We are currently investigating elevated 3DS failures with our Global 3DS provider, Seglan.

Elevated 3DS Failures

Aug <var data-var='date'>19</var>, <var data-var='time'>09:34</var> EDT Resolved - On August 19th, 2025, from 9:34 a.m. to 12:55 p.m. EST, an unexpected interruption in 3DS execution occurred during a configuration change in one of our 3DS MPI providers' systems. Customers experienced an increased rate of SCA Authentication failures, resulting in the following error: "Gateway transaction not attempted due to failed SCA authentication." Our 3DS provider has since resolved the issue and is implementing stronger safeguards to prevent this from happening again. This issue is considered resolved, and no further customer impact is expected.

Elevated Rate of SCA Authentication Failures

Jun <var data-var='date'>30</var>, <var data-var='time'>10:05</var> EDT Resolved - Spreedly has identified an issue where non-unique payment method fingerprints were issued between 16:05 and 17:50 UTC. The issue has been resolved.

Is Spreedly down?

Spreedly status is UP

Lastest published events

Dodgeball Checkpoint Latency

Increased errors with Core Transactional API

Dodgeball maintenance

Spreedly Services, Components and Regions

Recent Spreedly events

Dodgeball Checkpoint Latency

Increased errors with Core Transactional API

Dodgeball maintenance

Dodgeball Maintenance

Dodgeball Production Instance Storage Critically Low

Dodgeball Checkpoint Latency

Get your FREE account now,
5 monitors included!

Is Spreedly down?

Spreedly status is UP

Lastest published events

Dodgeball Checkpoint Latency

Increased errors with Core Transactional API

Dodgeball maintenance

Spreedly Services, Components and Regions

Recent Spreedly events

Dodgeball Checkpoint Latency

Increased errors with Core Transactional API

Dodgeball maintenance

Dodgeball Maintenance

Dodgeball Production Instance Storage Critically Low

Dodgeball Checkpoint Latency

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!