Spreedly Status Page

Aug 14, 2026 · resolved Aug 14

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.

Jul 27, 2026 · resolved Jul 27

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.

Jul 11, 2026 · resolved Jul 11

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.

Jul 8, 2026 · resolved Jul 8

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.

Jun 17, 2026 · resolved Jun 17

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

Is Spreedly down right now?

No — Spreedly is up. All systems operational as of Aug 19, 10:43 PM UTC.

What is Spreedly's current status?

Spreedly: All Systems Operational. Alert24 checks Spreedly's status page continuously and can notify you the moment it changes.

How do I get alerted when Spreedly goes down?

Alert24 monitors Spreedly and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.