rewindex

ChangesDeepgramElevated 5xx Errors

Deepgram: Incident updated: Elevated 5xx Errors

Incident updateNormal progress (rule, 100%)Changed status.deepgram.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Deepgram removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-23 11:00 UTC
AddedUpdateresolved#3
Before: not present
After: 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.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Friday, October 23

1 incident change

Thursday, October 22

3 incident changes

Cite this

Incident updated: Elevated 5xx Errors on Deepgram’s status page, changed 2026-10-23 11:03 UTC (change 4 of 4).

Title
Incident updated: Elevated 5xx Errors
Vendor
Deepgram
Date
URL
https://rewindex.com/change/rd0d309933cb882

All Deepgram changesDeepgram profileMarkdownJSON