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