Vendor record
Deepgram
Checked
Front door check counts and Deepgram’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented Deepgram endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,871 of 2,871 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
8 more checks gave no clear answer and are not counted.
- Endpoint checked
- api.deepgram.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every Deepgram product, region or your app worked.
How we count front door checksDeepgram says
Incident posts from Deepgram’s status page, with its titles, impact levels and times. They say what Deepgram chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
22
incidents Deepgram posted, last 1 year
Median recorded duration: 3h 39m. From 22 incidents with vendor-supplied starts and recorded closure times.
Most recent records · all dates
Elevated errors for Flux TTS
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(27m)
Elevated errors for Flux TTS
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(2h 7m)
Elevated API errors
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(18h 1m)
Elevated Latency and Errors for Batch STT (US)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(4h 19m)
Elevated latency on Flux STT (US)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(3m)
15 older records
ISP Backbone Degradation
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(3h 7m)
Elevated 5XX Error Rate for v1/auth/grant
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(1h 38m)
[Deepgram API] Elevated Batch and Streaming STT Error Rates
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(3h 39m)
[Deepgram API] Elevated Batch Error Rates: 400 error code responses
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(21h 14m)
Intermittent Connectivity Issues Due to AWS US-WEST-2 Infrastructure Event
Not specifiedDeepgram’s postStarted, per Deepgram
Closed in our record(12m)
Elevated 5XX Errors for Flux STT Requests
Not specifiedDeepgram’s postStarted, per Deepgram
Closed in our record(10m)
Voice Agent third-party provider Instability (Anthropic LLMs)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(2h 23m)
Elevated errors when using Google Gemini models with Voice Agent
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(5d 19h)
Degraded performance — Flux streaming Speech-to-Text
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(18m)
Degraded API Performance
Not specifiedDeepgram’s postStarted, per Deepgram
Closed in our record(10m)
Voice Agent third-party provider instability (ChatGPT 4o)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(1d)
Voice Agent third-party provider instability (Claude Sonnet 4.5)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(7d 12h)
Voice Agent third-party provider instability (Google Gemini LLMs)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(10d 2h)
Issues with downstream LLM provider in Voice Agent API
Not specifiedDeepgram’s postStarted, per Deepgram
Closed in our record(6h 53m)
Outbound networking issues affecting STT PreRecorded API requests with callbacks, TTS Batch (HTTP) requests with callbacks, and Voice Agent API BYO 3rd party providers (LLM and TTS)
MinorDeepgram’s postStarted, per Deepgram
Closed in our record(3d 2h)
Your code, your dependencies
See which of your code paths call Deepgram
Connect GitHub or GitLab to find where your public or private repository uses Deepgram. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add Deepgram status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is Deepgram currently down?
Deepgram's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did Deepgram last have an outage?
The most recent closed incident record began 11 days ago and spans 27 minutes. The vendor reported degraded performance. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for Deepgram?
No. CheckUpstream checks Deepgram’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor Deepgram in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track Deepgram?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.