Spreedly experienced a minor incident on August 14, 2026 affecting Core Transactional API, lasting 20m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 14, 2026, 04:14 PM UTC
We are currently investigating an increase in 5xx errors on the Core Transactional API. Some transactions may be failing or returning unexpected error responses during this time. We will provide an update as soon as we have more information.
- resolved Aug 14, 2026, 04:34 PM UTC
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.
- postmortem Sep 03, 2026, 08:55 PM UTC
### 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.