Spreedly Status Page

Sep 2, 2026 · resolved Sep 2

### _September 9, 2026_ — _Elevated Error Rates Affecting Transaction Processing_ ### ‌High Level Summary On September 2, 2026, between 14:35 and 15:19 UTC, Spreedly experienced a period of elevated error rates affecting a subset of transaction requests across endpoints. The issue lasted approximately 44 minutes and was caused by an infrastructure-level issue with our database platform. Our team identified and resolved the issue the same day. ### What Happened During a routine schema update, a defect in our underlying database platform caused one of our database nodes to become unavailable. This temporarily reduced the redundancy for a portion of our transaction data, which led some requests to either time out or receive a system error response \(HTTP 500\) instead of processing normally. Our team worked directly with our database vendor to identify the root cause and confirm full recovery of the affected infrastructure. ### Next Steps We've identified the underlying cause as a known issue in our database vendor's software. A vendor-supplied fix is scheduled to be applied during normal scheduled maintenance. In parallel, we are adding additional monitoring to detect this class of issue earlier, and adjusting our internal procedures around database maintenance work to further reduce the risk of a similar incident going forward. -The Spreedly Team

Aug 14, 2026 · resolved Aug 14

### Service Disruption on Transaction Endpoints ### ‌High Level Summary On August 14, 2026, Spreedly experienced a brief service disruption affecting some transaction-related API endpoints for approximately 20 minutes \(4:06 PM – 4:26 PM ET\). During this window, some requests to endpoints involving transaction lookups, captures, voids, credits, and payment method operations may have received error responses. The issue was identified and resolved quickly by our engineering team. ### What Happened A routine database schema update caused a subset of existing database connections to reference outdated schema information, resulting in intermittent errors on affected requests. Once identified, our team refreshed the affected database connections, which fully resolved 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.

Jul 27, 2026 · resolved Jul 27

### 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.

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.

Is Spreedly down right now?

No — Spreedly is up. All systems operational as of Oct 12, 5:51 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.