Elevated 5xx Errors
major- Started
- Oct 22, 1:06 PM EDT
- Resolved
- Oct 23, 7:00 AM EDT
- Duration
- 17h 53m
Deepgram's updates (4)
- investigating · Oct 22, 12:00 PM EDT
We are currently investigating elevated 5xx errors with authentication services at one of our datacenters.
- investigating · Oct 22, 1:14 PM EDT
We are continuing to investigate this issue.
- monitoring · Oct 22, 1:29 PM EDT
We have identified the issue & are monitoring the solution.
- resolved · Oct 23, 7:00 AM EDT
Between 16:00 and 17:09 UTC on October 22, some API requests returned 5xx errors because of an issue with authentication services at one of our datacenters. This incident is resolved. All systems are operational.
What our checks recorded
We checked Deepgram 214 times from Deepgram's start time to its resolution, once every five minutes. Every one of them reached Deepgram's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 124 ms, against 122 ms over the 24 hours before. Deepgram posted the incident at Oct 22, 12:00 PM EDT.
Updates are Deepgram's own words from its status page (status: resolved); we never add an inferred cause. The vendor's incident page ↗