Is Spreedly down?

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.

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.

This incident has been resolved.

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

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.

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.

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

We are currently investigating this issue.

The issue has been identified and a fix is being implemented.

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.

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.

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

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.

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.

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.

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.

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.