Elevated Rate of Transaction Failures

Update timeline

1. investigating Apr 14, 2025, 07:55 PM UTC

   Spreedly has detected an issue that may impact customers, including potentially resulting in failed 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.

2. investigating Apr 14, 2025, 08:08 PM UTC

   We are continuing to investigate this issue.

3. identified Apr 14, 2025, 08:13 PM UTC

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

4. monitoring Apr 14, 2025, 08:18 PM UTC

   A fix has been implemented and we are monitoring the results.

5. resolved Apr 14, 2025, 08:33 PM UTC

   This incident has been resolved.

6. postmortem Apr 28, 2025, 11:37 PM UTC

   # **April 14, 2025 — Certificate Issue Impacts Core Requests** ‌ On April 14 at 3:47 PM ET, a platform-wide incident occurred that caused all core Spreedly requests to fail. The issue was identified and declared at 3:49 PM, mitigated by 4:13 PM, and fully resolved by 4:32 PM. Total impact duration was 26 minutes. During this window, merchants were unable to complete any transactions through the Spreedly platform due to system-wide connectivity failures. ## What Happened An intermediate certificate on our core service hosts expired April 14th at 3:47pm EST, which broke the certificate chain, preventing HTTP requests between Spreedly internal services and subsequently led to responses of HTTP 500 errors for all requests. ## Next Steps * Spreedly is completing an audit of all certificate chains to identify potential risks and update our catalog of expiration dates. * Spreedly has a plan in place to migrate the management of all certificate chains to our cloud provider.