Spreedly incident
Asynchronous transactions with degraded performance
Spreedly experienced a minor incident on June 17, 2026 affecting Core Transactional API, lasting 6h 46m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 17, 2026, 02:55 PM UTC
Spreedly has detected an issue potentially resulting in degrated performance with asynchronous 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. Thank you for your patience.
- monitoring Jun 17, 2026, 03:00 PM UTC
We’ve implemented a fix and stabilized the asynchronous transactions. Our team is monitoring the situation closely to ensure there are no additional impacts. Please continue to follow our StatusPage for the latest update.
- monitoring Jun 17, 2026, 04:03 PM UTC
We are monitoring closely for any further issues or additional impacts. Please continue to follow our StatusPage for the latest updates.
- resolved Jun 17, 2026, 09:42 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.
- postmortem Jun 24, 2026, 08:10 PM UTC
June 24, 2026 — Asynchronous Transaction Processing Disruption **High Level Summary** On June 17, 2026 from approximately 10:02 AM to 10:41 AM UTC, Spreedly experienced a disruption affecting asynchronous gateway transactions and 3DS authentication flows. During the 39-minute window, approximately 1,634 transactions were left in a pending state without a confirmed outcome, representing less than 1% of total transaction volume during that period. **What Happened** A code deployment introduced a compatibility issue between newly deployed and previously running application instances. During a rollback process, some requests were routed across mixed code versions, causing failures when processing asynchronous transaction status updates. Affected transaction types include asynchronous gateway transactions \(gateway specific 3DS, and other asyncronous verifications, authorizations, and purchases\) and 3DS Global authentication. Transactions that entered the affected flow during this window may reflect an indeterminate outcome, the transaction state at your gateway may differ from what Spreedly reports. **Next Steps** We recommend reviewing transactions from the 10:02–10:41 AM UTC window on June 17 that remain in a pending state: Verifications may be safely retried. Authorizations should be voided at the gateway before retrying. Purchases carry a risk of duplication, we recommend refunding before retrying. Please reach out to Spreedly support if you need assistance identifying affected transactions or determining the appropriate remediation path. We are actively working to prevent this class of issue through improved deployment safeguards and automated rollback detection. -The Spreedly Team