Operational Deepgram outage dossier
deepgram.com · Official status page (Statuspage-compatible JSON)
Official status now
Operational Operational
checked 0 min ago How we score status
All Systems Operational
Read just now from: Official status page (Statuspage-compatible JSON) · official page ↗
ORBIT score
Clear skies: official status: Operational
At a glance
90-day timeline (1 day tracked)
Each bar is a day. Green: our checks found no official incident. Amber/red: the provider reported one. Grey: before ORBIT started tracking this service. This is "share of our checks with no official incident", not the provider's SLA.
Official incidents per week
Impact mix, 90 d
- 16 minor
- 3 major
- 3 none
Visitor reports, last 24 h
Unverified reports from ORBIT visitors, in 15-minute buckets. Add yours.
Incident history
- → resolved · lasted 6.2 h[Deepgram US API] Intermittent connection timeoutsminor resolved · STT Batch API, STT Streaming API, TTS Batch API, TTS Streaming API · official notice ↗ · replay & discuss
- → resolved · lasted 2 h[Deepgram US API] Intermittent connection timeoutsminor resolved · STT Batch API, STT Streaming API, TTS Batch API, TTS Streaming API · official notice ↗ · replay & discuss
- → resolved · lasted 16 min[Deepgram US API] Elevated errors for Aura-2 TTSminor resolved · TTS Batch API, TTS Streaming API · official notice ↗ · replay & discuss
- → resolved · lasted 1 min[Deepgram US API] Elevated API errorsminor resolved · STT Streaming API, TTS Streaming API · official notice ↗ · replay & discuss
- → resolved · lasted 10 minFlux TTS high latency and websocket disconnectsmajor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 6.6 hElevated errors for Flux streaming STT and Voice Agent sessionsnone resolved · STT Streaming API, Voice Agent API · official notice ↗ · replay & discuss
- → resolved · lasted 55 minElevated errors from authentication services at one datacenterminor resolved · STT Batch API, STT Streaming API, TTS Batch API, Voice Agent API · official notice ↗ · replay & discuss
- → resolved · lasted 2.4 hElevated Latency and Errors for Batch STTminor resolved · STT Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 19 hElevated 5xx Errorsmajor resolved · STT Batch API, STT Streaming API, TTS Batch API, Voice Agent API · official notice ↗ · replay & discuss
- → resolved · lasted 1.5 hElevated 503 errors for bath Flux TTS requestsminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 11 minElevated 503 errors for Aura-2 TTSminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 1.5 hElevated error rates for Flux TTSminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 2 hElevated errors for Flux TTSminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 2 hElevated errors for Flux TTSminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 10 minElevated API errorsminor resolved · STT Batch API, STT Streaming API, TTS Batch API, Voice Agent API · official notice ↗ · replay & discuss
- → resolved · lasted Elevated Latency and Errors for Batch STT (US)minor resolved · STT Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 4 minElevated latency on Flux STT (US)minor resolved · STT Streaming API · official notice ↗ · replay & discuss
- → resolved · lasted 4 hElevated Flux TTS 1011 Error Rateminor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 40 minAura-2 TTS Elevated Error Rates for English Voicesmajor resolved · TTS Batch API · official notice ↗ · replay & discuss
- → resolved · lasted 3.1 hISP Backbone Degradationminor resolved · official notice ↗ · replay & discuss
- → resolved · lasted [Deepgram EU API] Flux-Multi STT Outagenone resolved · official notice ↗ · replay & discuss
- → resolved · lasted [Deepgram API] Elevated Streaming STT Error Ratesnone resolved · official notice ↗ · replay & discuss
Related services
- OperationalOpenAI (ChatGPT & API)Operational→
- OperationalAnthropic (Claude)Operational→
- no official feedGoogle Geminino official feed→
- OperationalGitHub CopilotOperational→
- OperationalMistral AIOperational→
- OperationalCohereOperational→
- OperationalPerplexityOperational→
- OperationalHugging FaceOperational→
"Runs on" links are inferred from public information and may be outdated.
How we score status
- Source. Every reading comes from the provider's own public status page or status API (Statuspage, Instatus, incident.io-style JSON, or the provider's RSS/JSON). ORBIT never pings or scans the service.
- Scope. For each open incident we count the regions or components it names against the total the provider publishes, and label it global, multi-region, 1 region or n of N components.
- Age. Incidents are new (under 1 hour), active, long-running (open more than 48 hours) or stale (no provider update for 24 hours or more).
- Headline. The headline colour comes from current incidents only. A single-region or small-scope incident caps the headline at "Degraded"; a global or widespread one keeps the provider's impact. Long-running or stale issues limited to one region or a few components get a known long-running issue badge and don't set the headline colour.
- Transparency. The provider's own page-level status is always shown next to ORBIT's headline, with a link to the official page. When they differ, the provider's page is the authority on what it says.
Where this data comes from. "Official status" is read from each provider's own public status page or status API (the same JSON or RSS their status page publishes), cached for a minute or more. ORBIT never pings, scans or probes the provider's systems. "Our checks" and history are ORBIT's own record of those readings, kept in our database. Visitor reports are unverified. Headlines are matched by name and shown for context: coincidence, not causation. Cloudy_Day is independent and not an official source for any company listed.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.