This incident was resolved at 11:40 UTC on Sunday 22nd August, approximately 3 hours and 45 minutes after it began. The issue related to a cache failover event, leading to certain parts of our API infrastructure becoming overburdened. While our service remained available during this time, up to approximately 50% of API requests may have received 500 errors.
(NB: An earlier update to this incident report may have continued to show the API status as "partially degraded," however the service has been fully operational since the fix was implemented.)
Please accept our apologies for any inconvenience caused by this incident. If you have any further comments or questions, please don't hesitate to contact us at firstname.lastname@example.org.
Posted Aug 24, 2021 - 09:47 UTC
A fix has been implemented and we are monitoring the results.
Posted Aug 22, 2021 - 11:50 UTC
We have identified the cause of the incident occurring today, and we are working on a solution. Thank you for your patience.
Posted Aug 22, 2021 - 11:12 UTC
We are investigating a technical issue with our infrastructure that is causing API 500 errors. Please stand by for updates.