On February 24th, 2022 at 16:25 UTC, an upstream service provider declared an incident that caused Spreedly’s transactional API to return elevated
502 error responses. A total of 7% of overall API requests were affected for a duration of approximately 61 minutes. Normal operations resumed after the upstream provider resolved their incident.
An upstream service provider disruption prevented core Spreedly APIs from performing functions required to process a subset of transactions nominally. The disruption first presented as access issues to the Spreedly Dashboard service, and at the same time Spreedly identified failed transactions (around 16:41 UTC). The Spreedly team began investigation and noted that the upstream providers disruption’s timing coincided with the timing of failed transactions on Spreedly’s systems. Once the upstream disruption subsided at 17:26 UTC, Spreedly’s systems returned to a normal functioning state.
Spreedly has updated their internal roadmap with specific items intended to lessen the reliance on upstream service providers for the transactional API and improve resiliency when disruptions to 3rd party services occur.