Skip to content

Outage tracker / Deepgram / In the US

Is Deepgram down in the US?

Vendor reports no incidentWhat Deepgram reports

Deepgram reports no incident on its status page.

As of the last successful poll, 2026-11-06 17:08 UTC.

Deepgram's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingin the US, measured from Ashburn and San Jose

All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Deepgram at Nov 6, 2026, 5:12 PM UTC.

Over the last 24 hours we completed 255 checks from Ashburn and San Jose and 255 answered cleanly, 100.00% availability.

Of the 2 other regions we check Deepgram from, all 2 read checks passing right now.

Email me when Deepgram reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is Deepgram's own statement from its status page, with our regional reading beside it.

What our Ashburn and San Jose probes measured

AshburnChecks passing143 checks in 24h, 100.00%
San JoseChecks passing112 checks in 24h, 100.00%

Last checked Nov 6, 2026, 5:12 PM UTC.

Deepgram from Ashburn and San Jose over the last 30 days

Over the last 30 days, Deepgram answered our San Jose probe in 1,091 ms on average, and 1 check in 20 took longer than 1,794 ms.

Over the last 30 days, Deepgram answered our Ashburn probe in 1,191 ms on average, and 1 check in 20 took longer than 1,605 ms.

Ranked by average response time across the 4 cities we check Deepgram from, San Jose 2nd, Ashburn 3rd; Frankfurt was fastest at 895 ms and Tokyo slowest at 1,898 ms.

From Ashburn and San Jose we ran 1,038 checks of Deepgram in 5 days, and 1,037 answered cleanly: 99.90% availability.

1 of the 5 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 248 checks.

In Ashburn local time (EST), Deepgram was slowest around 12 AM, at 1,417 ms on average over the last 14 days, and quickest around 7 AM, at 903 ms.

Day (UTC)ChecksAvailabilityAverage response
Fri, Nov 6177100.00%1,226 ms
Thu, Nov 5253100.00%1,157 ms
Wed, Nov 4254100.00%1,068 ms
Tue, Nov 324899.59%1,141 ms
Mon, Nov 2106100.00%1,201 ms

Deepgram outages measured from the US

Our Ashburn and San Jose probes measured no confirmed Deepgram outage in the last 90 days.

How the other regions read right now

Of the 2 other regions we check Deepgram from, all 2 read checks passing right now.

Probe cityRight nowLast 24h
FrankfurtChecks passing100.00% of 98 checks
TokyoChecks passing100.00% of 59 checks

Other countries we check Deepgram from

How we measured this

The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Deepgram's public endpoints. They are not user reports, and they are not Deepgram's own status page.

See Deepgram's full check readings, the 90-day history by region, or the outage tracker methodology.

The US readings here are taken from that country and show the time of the last one, but Deepgram has not yet accumulated enough continuous history for us to publish this page to search engines.

Check your own site from Ashburn

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter