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.
Spreedly Outage History
Spreedly is up right nowSpreedly had 34 outages in the last 2 years totaling 56h 28m of downtime — averaging 1.4 incidents per month.
There were 34 Spreedly outages since May 30, 2024 totaling 56h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.
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
Timeline · 2 updates
Intermittent 500 Errors
Affected: Core Transactional API
Timeline · 1 update
- resolved Jun 04, 2025, 05:15 PM UTC
This morning, from 11:43 AM EDT to 11:45 AM EDT, for about two minutes, we experienced a minor issue that caused intermittent 500 errors. Our team has fixed the problem, and we do not anticipate any further impact on customers.
Issues with Google Pay transactions
Affected: Alternative Payment Methods (APMs)
Timeline · 4 updates
Elevated Rate of Transaction Failures
Affected: Core Transactional API
Timeline · 6 updates
- investigating Apr 14, 2025, 07:55 PM UTC
Spreedly has detected an issue that may impact customers, including potentially resulting in failed 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.
- investigating Apr 14, 2025, 08:08 PM UTC
We are continuing to investigate this issue.
- identified Apr 14, 2025, 08:13 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 14, 2025, 08:18 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 14, 2025, 08:33 PM UTC
This incident has been resolved.
- postmortem Apr 28, 2025, 11:37 PM UTC
# **April 14, 2025 — Certificate Issue Impacts Core Requests** On April 14 at 3:47 PM ET, a platform-wide incident occurred that caused all core Spreedly requests to fail. The issue was identified and declared at 3:49 PM, mitigated by 4:13 PM, and fully resolved by 4:32 PM. Total impact duration was 26 minutes. During this window, merchants were unable to complete any transactions through the Spreedly platform due to system-wide connectivity failures. ## What Happened An intermediate certificate on our core service hosts expired April 14th at 3:47pm EST, which broke the certificate chain, preventing HTTP requests between Spreedly internal services and subsequently led to responses of HTTP 500 errors for all requests. ## Next Steps * Spreedly is completing an audit of all certificate chains to identify potential risks and update our catalog of expiration dates. * Spreedly has a plan in place to migrate the management of all certificate chains to our cloud provider.
Missing Stylesheet - 404 Error on express-3.min.js
Affected: iFrame
Timeline · 3 updates
- investigating Apr 02, 2025, 08:54 AM UTC
We are currently investigating an issue where the stylesheet express-mobile-3.1.0.min.css is returning a 404 Not Found error, causing the user interface to break in the Spreedly Express integration.
- monitoring Apr 02, 2025, 10:24 AM UTC
The issue with the missing stylesheet express-mobile-3.1.0.min.css causing the user interface to break in the Spreedly Express integration has been resolved. We are now actively monitoring the system to ensure the issue does not recur.
- resolved Apr 02, 2025, 10:49 AM UTC
The issue has been fully resolved, and the system is functioning as expected. No further incidents have been observed.
Early Alert: Potential Customer-Impacting Issue Detected
Affected: Core Transactional API
Timeline · 5 updates
- investigating Mar 15, 2025, 06:50 AM UTC
We are investigating an elevated rate of 5xx errors affecting Spreedly core services starting at 01:36AM EST. 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. Our team is actively working to identify the root cause and mitigate the impact. We will provide further updates as soon as we have more information. Thank you for your patience.
- monitoring Mar 15, 2025, 07:32 AM UTC
As of 3:10 AM EST, our system availability has been fully restored and we are seeing stability return. We have implemented a fix and stabilized Spreedly Core Services. Our team is closely monitoring the situation to ensure no further impact.
- monitoring Mar 15, 2025, 11:35 AM UTC
As of 3:10 AM EST, our system availability has been fully restored and we are seeing stability return. We have implemented a fix and stabilized Spreedly Core Services. Our team is closely monitoring the situation to ensure no further impact.
- resolved Mar 15, 2025, 01:40 PM UTC
IMPACT STARTED AT: 2:12 AM EST IMPACT ENDED AT: 2:40 AM EST After closely monitoring Spreedly Core Services 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. A post-mortem will be published. We apologize for any inconvenience or disruption.
- postmortem Mar 21, 2025, 02:07 AM UTC
# March 15th, 2025 — Payment Method Storage Errors _On March 15th, 2025 at 06:12 UTC Spreedly systems encountered a system resource constraint which led to intermittent API call failures resulting in_ `404` _and_ `500` errors being returned to customers. _The unresponsive application containers were restarted allowing the system to return to normal at 06:47 UTC_ ## What Happened On 2025-03-15 between 06:12 and 06:47 UTC, calls to Spreedly’s payment method tokenization endpoints intermittently failed resulting in `HTTP 500` errors. Intermittent elevated rates of `HTTP 404` errors when attempting to use a payment method to transact were also encountered. These failures were the result of internal system resource limitations. ## Next Steps * Spreedly has implemented additional resource monitoring in our automated alerting system to prevent future overruns. * System resources have been adjusted to prevent similar situations in the future.
Core 5xx Errors Impacting Spreedly Core Services
Affected: Core Transactional API
Timeline · 4 updates
- investigating Feb 16, 2025, 09:43 AM UTC
We are investigating an elevated rate of 5xx errors affecting Spreedly core services. This issue began at 3:56 AM EST. Our team is actively working to identify the root cause and mitigate the impact. We will provide further updates as soon as we have more information. If you have any questions or concerns, please reach out and our support team will be happy to assist.
- monitoring Feb 16, 2025, 10:16 AM UTC
As of 4:44 AM EST, our systems have been resourcing this issue, and we are seeing stability return. We have implemented a fix and stabilized Spreedly Core Services. Our team is closely monitoring the situation to ensure no further impact.
- resolved Feb 16, 2025, 10:39 AM UTC
After closely monitoring Spreedly Core Services 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 root cause of the incident and any residual impact. A post-mortem will be published. We apologize for any inconvenience or disruption.
- postmortem Feb 20, 2025, 10:16 PM UTC
# February 16, 2025 — Intermittent API Failures Resulting in 404 and 500 errors _On February 16, 2025 at 08:55 UTC Spreedly systems encountered a system resource constraint which led to intermittent API call failures resulting in_ `404` _and_ `500` errors being returned to customers. _The unresponsive application containers were restarted allowing the system to return to normal at 09:55 UTC._ ### What Happened On 2025-02-16 between 08:55 and 09:55 UTC calls to Spreedly’s payment method tokenization endpoints intermittently failed resulting in `HTTP 500` errors. Intermittent elevated rates of `HTTP 404` errors when attempting to use a payment method to transact were also encountered. These failures were the result of internal system resource limitations. ### Next Steps * Spreedly has implemented additional resource monitoring in our automated alerting system to prevent future overruns. * System resources have been adjusted to slow similar situations in the future.
Core Transactional API Errors
Affected: Core Transactional API
Timeline · 4 updates
- investigating Dec 12, 2024, 06:04 PM UTC
Spreedly has discovered an issue that could potentially impact new payment method creation. We are taking all necessary measures to investigate the matter and determine the extent of the situation. We will provide an update as soon as more details are available.
- monitoring Dec 12, 2024, 06:32 PM UTC
From 12:47 to 12:58 PM EST, we encountered an issue that affected customers attempting to tokenize a payment method and transacting with a payment method, resulting in a 500 error. We have identified the problem and implemented a fix. Our team is closely monitoring the situation to ensure there are no further impacts. If you need additional assistance, please reach out to our Support team.
- resolved Dec 12, 2024, 07:25 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.
- postmortem Dec 17, 2024, 10:59 PM UTC
# December 12th, 2024 — Payment Method Tokenization Errors Server maintenance to reduce log volume caused an internal service to become unavailable, causing payment method tokenization requests to fail. ## What Happened At approximately 17:45 UTC on December 12th, 2024, a logging configuration change made to reduce log volume resulted in an internal service becoming unavailable. Traffic was shifted to an alternate service during the outage window to reduce impact. At approximately 18:01 the internal service resumed normal operation and service was restored. Payment transactions were negatively impacted during this time. ## Next Steps Spreedly Engineering is investigating the coupling of the configuration change to the internal service and will be taking steps to prevent the issue from occuring in the future.
Global Collect Gateway 404 Errors
Affected: Core Transactional API
Timeline · 3 updates
- investigating Dec 12, 2024, 12:42 AM UTC
Spreedly is investigating an issue that could potentially impact our services, leading to 404 errors on the Global Collect gateway. We are taking all necessary measures to investigate the matter and determine the extent of the situation. We will provide an update as soon as more details are available. Thank you for your patience.
- resolved Dec 12, 2024, 02:05 AM UTC
We have identified an issue with a code change that was deployed around 3:35 pm EST that affected the Global Collect gateway. We have rolled back this code change and are now seeing successful transactions. After a period of monitoring, we have not seen any recurrence of this issue. The incident is being considered resolved. We will publish a postmortem on our status page as soon as possible. We apologize for any inconvenience this has caused.
- postmortem Dec 16, 2024, 07:04 PM UTC
# December 11th, 2024 — Global Collect Gateway Transaction Failures A change to the Global Collect gateway integration resulted in transaction failures for a subset of customers. ## What Happened At 20:50 UTC, an update was made to the Global Collect gateway integration. Initial monitoring and observability did not surface issues. At 23:53 UTC, Spreedly Engineering began researching an elevated number of transaction failures on the Global Collect gateway. After investigation, it was determined that the prior update to the Global Collect gateway was causing the increase in transaction failures. At 01:02 UTC on December 12th, 2024, the change was reverted and service to the Global Collect gateway was restored. ## Next Steps Spreedly Engineering is reviewing and improving internal observability to better surface gateway-specific transaction failure rate anomalies.