AWS Outage Impact
Incident
Report for Spreedly
Postmortem
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
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.
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 here
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
This incident affected: Core Secondary API.