Spreedly experienced a major incident on July 27, 2026 affecting Core Transactional API, lasting 7h 51m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 27, 2026, 01:50 PM UTC
We are currently investigating this issue.
- identified Jul 27, 2026, 02:00 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Jul 27, 2026, 03:00 PM UTC
Spreedly detected an issue that may have impacted core transaction performance. While the issue now appears to be resolved, our team is actively monitoring systems to ensure continued stability. We will provide a final update once our investigation into the full scope and impact is complete. Please continue to follow our StatusPage for the latest update.
- resolved Jul 27, 2026, 09:41 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 are completing our investigation concerning the causes of the incident and any residual impact. We apologize for any inconvenience or disruption.
- postmortem Sep 03, 2026, 08:57 PM UTC
### High Level Summary On July 27, 2026, Spreedly experienced intermittent errors on a subset of transaction requests, including purchases, authorizations, and webhooks. ### What Happened A database migration updated the schema of an internal service that manages stored payment methods. This caused errors on existing connections referencing a stale cache. We rolled back the change and cycled those connections, fully resolving the issue. ### Next Steps We are reviewing our schema migration process to add additional safeguards that will prevent this class of issue from recurring, and are improving automated testing coverage for this scenario. We have added auto-retry and recovery mechanisms so that if a connection does reference an outdated schema it will not affect transactions going forward.