Spreedly Outage History

A fix has been implemented and error rates have returned to normal. Some transactions may have failed or returned errors during the affected window. We're continuing to monitor and will follow up with a more detailed post-incident summary.

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.

We identified and resolved the issue causing intermittent 500 responses on certain list and retrieval endpoints. A configuration update has been deployed to prevent requests from being prematurely terminated, and we are continuing to monitor the service.

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.

This incident has been resolved.

This incident has been 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.

This incident has been 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.

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.

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.

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.

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.

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.