●Incident
Deepgram outage.
ResolvedDEGRADATION · HIGHNov 1, 2026, 03:01 PM · 2 days ago · Duration: 36min
Incident Summary
Incident Summary
API Deepgram is currently DOWN in us-east.
Diagnostic Details
Error Type: http HTTP Status: 503 Error Message: API returned HTTP 503 Retry Attempts: 1 (all failed)
Validation Results
Validation Reason: DOWN in multiple regions: asia, europe, us-west + us-east Consecutive DOWN Checks: 2 Time Between Checks: 270s
Cross-Region Impact
Also DOWN in: asia, europe, us-west Total Affected Regions: 4
Severity Assessment
Level: HIGH Multiple regions affected or critical error type detected.
Detected by Probecast Health Monitor - 2026-11-01T15:01:15.527Z
Timeline
●Started
Nov 1, 2026, 03:01 PM
2 days ago
●Resolved
Nov 1, 2026, 03:37 PM
2 days ago
●Duration
36min
Total downtime
Evidence Logs5 checks
| Time | Region | Status | Latency | Code |
|---|---|---|---|---|
| Nov 1, 03:01 PM | us-east | down | 13ms | 503 |
| Nov 1, 03:00 PM | europe | down | 142ms | 503 |
| Nov 1, 02:59 PM | asia | down | 223ms | 503 |
How many of your clients depend on Deepgram?
When Deepgram slows down, every project that depends on it feels it at once — and the first call goes to whoever shipped it. Probecast watches the sites you ship and the providers underneath them, shows which clients an outage touches and turns each month into a report your client can trust.
One provider breaks. See every client it touches.
Ordered by how many clients it hits, so you message the right people first.
Each client's site and store, checked from up to four regions.
US West & East, Europe and Asia — a regional outage never hides.
A monthly report under your brand, reviewed by your team before it goes out.
Uptime, incidents, traffic, revenue and support — signed off by a person.
Your team scoped per client. Every change on the record.
Freelancers see only their clients; every change lands in an append-only audit log.
Alerts land on email, Slack, push or webhooks — with the client's name on them.