Spreedly experienced a minor incident on September 2, 2026 affecting Core Transactional API, lasting 6h 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Sep 02, 2026, 03:11 PM UTC
Spreedly has detected an issue potentially resulting in degraded performance on transactional APIs. 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 Sep 02, 2026, 03:57 PM UTC
We’re working to resolve a performance lag affecting some payment processing (specifically purchase, capture, and payment method creation) related to recent database maintenance. A fix is underway, and our team is actively monitoring the system. Please check back here for real-time updates.
- resolved Sep 02, 2026, 09:32 PM UTC
This incident has been resolved.
- postmortem Sep 09, 2026, 09:50 PM UTC
### _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