Asynchronous transactions with degraded performance
Affected: Core Transactional API
Spreedly Outage History
Spreedly is up right nowSpreedly had 18 outages in the last 2 years totaling 49h 57m of downtime — averaging 0.7 incidents per month.
There were 18 Spreedly outages since June 30, 2025 totaling 49h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
Elevated Latency Dodgeball Platform
Affected: Dodgeball
Timeline · 2 updates
- monitoring May 08, 2026, 06:00 PM UTC
A fix has been implemented and we are monitoring results.
- resolved May 08, 2026, 06:05 PM UTC
This incident has been resolved.
Dodgeball Checkpoint Latency
Affected: Dodgeball
Timeline · 5 updates
- identified Mar 19, 2026, 03:13 PM UTC
We are currently investigating performance of the Dodgeball service.
- identified Mar 19, 2026, 03:30 PM UTC
We are working to resolve an issue with delayed processing of requests to the Dodgeball services.
- monitoring Mar 19, 2026, 03:55 PM UTC
We’ve implemented a fix and stabilized the Dodgeball component that was experiencing a partial outage. We are continuing to monitor
- monitoring Mar 19, 2026, 04:07 PM UTC
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.
- resolved Mar 19, 2026, 04:09 PM UTC
This incident has been resolved.
Increased errors with Core Transactional API
Affected: Core Transactional API
Timeline · 4 updates
Dodgeball Production Instance Storage Critically Low
Affected: Dodgeball
Timeline · 3 updates
- investigating Feb 26, 2026, 04:45 PM UTC
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.
- monitoring Feb 26, 2026, 04:59 PM UTC
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.
- resolved Feb 26, 2026, 06:44 PM UTC
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.
Credits Referencing Capture Transactions Failing
Affected: Core Transactional API
Timeline · 4 updates
Multiple merchants using Payflow Pro with experiencing intermittent payment failures
Affected: Core Transactional API
Timeline · 3 updates
- investigating Feb 04, 2026, 06:15 PM UTC
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.
- monitoring Feb 04, 2026, 07:52 PM UTC
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.
- resolved Feb 04, 2026, 07:56 PM UTC
This incident has been resolved.
Dodgeball: Elevated levels of latency for Checkpoints
Affected: Dodgeball
Timeline · 2 updates
- investigating Jan 27, 2026, 07:59 PM UTC
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.
- resolved Jan 27, 2026, 08:12 PM UTC
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.
3DS2 Global Transactions Pending
Affected: 3DS Global
Timeline · 4 updates
Higher error rates on when using Dodgeball runtime
Affected: Dodgeball
Timeline · 4 updates
- investigating Jan 09, 2026, 06:46 PM UTC
We are currently investigating this issue.
- investigating Jan 09, 2026, 06:52 PM UTC
We are continuing to investigate this issue.
- monitoring Jan 09, 2026, 07:07 PM UTC
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.
- resolved Jan 09, 2026, 07:10 PM UTC
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.
Increased Latency
Timeline · 1 update
- resolved Dec 29, 2025, 04:50 PM UTC
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.
Delayed Processing of Some 3DS Global Transactions
Timeline · 2 updates
Transaction Reporting Degraded
Affected: app.spreedly.com
Timeline · 5 updates
AWS Outage Impact
Affected: Core Secondary API
Timeline · 3 updates
- identified Oct 20, 2025, 03:41 PM UTC
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 here
- resolved Oct 20, 2025, 08:22 PM UTC
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.
- postmortem Oct 23, 2025, 06:27 PM UTC
### Postmortem: October 24, 2025 — _AWS outage_ Monday's AWS outage had downstream impact on some 3rd-party systems utilized by Spreedly's platform. Namely, our indexing endpoints and callbacks lagged behind due to the outage and recovery steps. ### What Happened Spreedly's 3DS global service and legacy smart routing product both faced a period of failures due to 3rd-party systems relying on AWS. ### Next Steps Spreedly will improve its response to our alerts platform, and are actively working on multi-region support slated for 2026, which should mitigate the impact of similar events going forward. -The Spreedly Team
Core 500s
Affected: Core Transactional API
Timeline · 6 updates
Elevated 3DS Failures
Affected: 3DS Global
Timeline · 2 updates
- investigating Sep 19, 2025, 03:53 PM UTC
We are currently investigating elevated 3DS failures with our Global 3DS provider, Seglan.
- resolved Sep 19, 2025, 05:46 PM UTC
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.
Elevated Rate of SCA Authentication Failures
Timeline · 1 update
- resolved Aug 20, 2025, 10:31 PM UTC
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.
Duplicate Payment Method Fingerprints Issued
Affected: Fingerprinting