Summary
On 9/20/23, a third-party CDN provider had internal issues connecting to AWS data centers in Columbus, OH. This caused increased timeouts for transactions originating from these locations.
What Happened
Based on Fastly’s Statuspage resolution on this incident:
“During this incident, customers would have experienced increased latency and elevated 5xx errors in our Columbus (CMH) POP, as well as, elevated errors when attempting to access configuration management and API services through our Control Plane from 18:40 to 21:30 UTC.”
Next Steps
No additional steps are required at this time
Conclusion
This is an unfortunate third-party service provider outage, and Spreedly has been in communication with the provider to determine the reason for the delay in notification.