PulseWatch manages 5 data types including abuse signals. Helps you organize, track, and share your work in 1 place for teams and solo users.

How does PulseWatch know if Deepgram is down?

PulseWatch evaluates user reports and replay-approved automated evidence for Deepgram. Canonical source identity prevents duplicate pipelines from being counted as independent corroboration.

How many people have reported Deepgram issues today?

As of Sep 27, 2026 16:52 UTC, 0 users had reported issues with Deepgram in the previous 24 hours.

How can I report a Deepgram outage?

Click the "Report an issue" button on this page to submit an outage report. Reports are evaluated with moderation, baseline, and corroboration controls before they can support an incident.

Productivity

Is Deepgram down right now?

NormalOfficial status last polled Sep 27, 2026 16:50 UTCdeepgram.com Official status page

Deepgram speech AI API, transcription, streaming, and platform availability.

Are you on the Deepgram team and see something inaccurate? Report it to us. We respond within one business day.

Is Deepgram down right now?

No. Deepgram has a current operational conclusion. Fresh official operational result confirmed by a healthy reachability check from the PulseWatch runtime (single region, HTTP reachability only).

Status as of Sep 27, 2026 16:52 UTC

Normal

Deepgram is operating normally

As of Sep 27, 2026 16:52 UTC

No elevated reports in the last 15 minutes. Baseline 5 reports/hour.

Reports 24h

Last incident

May 5, 2026 07:02 UTC

Trend

0/15m

Baseline

5/hr

Observed health

Unknown

No samples qualify for a combined success and latency score.

Evidence strength

No current issue evidence

No current corroborated or observed finding.

Evidence describes support for an issue, not its outage probability.

How this score works

100 × successful samples within the latency target ÷ assessed samples. Targets use a historical operation-latency baseline and are heuristic. Server failures count as failed samples; successful responses without a qualified target are shown separately. Only named operations are measured. Vendor statements, report volume, forecasts and incident records do not add score points.

A component issue stays visible even when other operations pass. Forecasts are separate from current health.

30 days incident history

Daily incident severity and duration for Deepgram.

Incident days

No recorded incident

0 min

Recorded duration

No recorded incident — health unknownLow or mediumHigh or critical

Recorded incidents remain visible regardless of current monitoring status. Days without records do not establish historical coverage or healthy service.

Showing available records within the selected range.

30-day outage frequency

Recorded incidents per day and recorded incident duration for Deepgram. Hover a day for detail.

Green baseline markers mean no recorded incident. These records do not establish historical monitoring coverage or verified uptime.

Days with incidents

0 incidents

Busiest day

0 min

Recorded duration

Report volume

0 reports in last 24H

Issue types

No data

Top cities

No location data

Top providers

No provider data

Auto-drafted postmortem

Deepgram outage on May 5 19-minute disruption

May 5, 06:42 AM → May 5, 07:02 AM · 19 minutes · high

Deepgram experienced a service disruption on May 5, 2026, which was detected by user reports and third-party monitoring. The incident lasted approximately 19 minutes and was fully resolved by 07:02 UTC.

Peak reports

in 15 min

Total reports

during outage

Duration

19 minutes

until recovery

Impact

The disruption to Deepgram services was observed by users and reported through various channels. While specific details regarding affected features or regions were not broadly recorded, the incident was categorized as high severity. We acknowledge the inconvenience this may have caused to our users during the 19-minute period.

Outage timeline

May 5, 06:42 AM
PulseWatch detected elevated report volume (high severity)
May 5, 06:45 AM
Peak of 0 reports in 15 minutes (baseline 1.3)
May 5, 07:02 AM
Report volume returned to baseline — incident resolved

Official updates

May 5, 06:42 AM
Deepgram status page acknowledged the incident.
View official source

Reliability

Detected by PulseWatch

30-day uptime

99.99%

90-day uptime

99.99%

Calculated from Deepgram's detected incidents. Lower than the vendor's own reported SLA? That's the whole point — we measure what users actually experience.

Other productivity services we monitor

Browse all

Community reports

0 comments

Confirm what you're seeing — your report helps others know if it's just them.

Be the first to post a report.