Elevated Rate of Transaction Failures

Incident Report for Spreedly

Postmortem

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.

Posted Apr 28, 2025 - 19:38 EDT

Resolved

This incident has been resolved.

Posted Apr 14, 2025 - 16:33 EDT

Monitoring

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

Posted Apr 14, 2025 - 16:18 EDT

Identified

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

Posted Apr 14, 2025 - 16:13 EDT

Update

We are continuing to investigate this issue.

Posted Apr 14, 2025 - 16:08 EDT

Investigating

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.

Posted Apr 14, 2025 - 15:55 EDT

This incident affected: Core Transactional API.