Is Spreedly down?
Last checked 1m agoNo incidents right now.
Spreedly is operational right now. Last checked 1m ago; the most recent incident resolved 1d ago.
Real-time Spreedly status, recent outages, and incident history — pulled directly from Spreedly's official status page at http://status.spreedly.com every 5 minutes. Pingoru tracks 20 Spreedly services and has captured 10 incidents in the last 90 days (99.75% uptime). Get email, Slack, Discord, or webhook alerts the moment Spreedly reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- Core Transactional API
Timeline · 4 updates
- 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.
Latest: 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. W…
-
- Core Transactional API
Timeline · 2 updates
- investigating · Jul 11, 2026, 02:33 PM UTC
We are investigating elevated error rates affecting certain API requests. Some list and retrieval endpoints may return intermittent 500 responses while we work to identify the root cause.
- resolved · Jul 11, 2026, 03:38 PM UTC
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.
Latest: 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 b…
-
- Core Transactional API
Timeline · 3 updates
- investigating · Jul 08, 2026, 03:22 PM UTC
Spreedly has detected an issue potentially resulting in degraded performance on Cybersource Credit transactions. While we are providing this early notification in an effort to alert you as quickly as possible, we are still investigating the actual scope and impact. We will provide an update as soon as more details are available.
- identified · Jul 08, 2026, 04:08 PM UTC
We have identified transient internal DNS resolution error that occurred between 15:00 and 15:05 UTC causing select 500 errors across Spreedly services. We continue to investigate the full impact and will provide additional information as it becomes available.
- resolved · Jul 08, 2026, 04:54 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.
Latest: 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. W…
-
- Core Transactional API
Timeline · 5 updates
- 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
Latest: 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 disruptio…
-
- Dodgeball
Timeline · 2 updates
- monitoring · May 08, 2026, 06:00 PM UTC
A fix has been implemented and we are monitoring results.
- resolved · May 08, 2026, 06:05 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Started Jul 27, 2026, 01:50 PM UTC · Resolved Jul 27, 2026, 09:41 PM UTC · 7h 51m
- Started Jul 11, 2026, 02:33 PM UTC · Resolved Jul 11, 2026, 03:38 PM UTC · 1h 4m
- Started Jul 08, 2026, 03:22 PM UTC · Resolved Jul 08, 2026, 04:54 PM UTC · 1h 32m
- Started Jun 17, 2026, 02:55 PM UTC · Resolved Jun 17, 2026, 09:42 PM UTC · 6h 46m
- Elevated Latency Dodgeball Platform ResolvedStarted May 08, 2026, 06:00 PM UTC · Resolved May 08, 2026, 06:05 PM UTC · 5m