Vendor reports: operationalResolved · vendor status “resolved”Official status API
Outbound networking issues affecting STT fetch requests and callbacks, Dashboard API requests, and Voice Agent 3rd party providers
Reported by Deepgram · AI & ML · source last read just now
- Vendor start
- Apr 27, 2026, 14:14 UTC
- Vendor's clock
- Resolved
- Apr 27, 2026, 14:14 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- Not available
- Needs both vendor times
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
Affected products and regions
- Components: Batch API, Streaming API, Voice Agent API.[E6]
What is unknown
- Which regions are affected: the vendor did not say.[E5]
- Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.
Last update in these facts: 2026-04-27 14:14 UTC · summary s1, evidence b1ccda8a283cc5d1
Evidence (7)
- E1Deepgram reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Outbound networking issues affecting STT fetch requests and callbacks, Dashboard API requests, and Voice Agent 3rd party providers". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2026-04-27 14:14 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Batch API, Streaming API, Voice Agent API. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2026-04-27 14:14 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Batch API, Streaming API, Voice Agent API
No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.
Potential relevance
Deepgram is not in your stack. Follow it to see whether reports like this fall inside the regions you use.
Timeline
Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.
- Apr 27, 2026, 14:14 UTCVendor-reported startVendor time
- Apr 27, 2026, 14:14 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.