Deepgram STT service degraded
Deepgram speech-to-text service is degraded for Vapi customers. Vapi reports that the root cause is identified and a fix is in progress. The issue started 26 minutes ago.
State
Degraded
Started
Ongoing for
35 min
Worst impact
Degraded
Timeline
2 updatesDegraded
35 min 100%
Updates
Times in UTCAs posted by Vapi
We have identified the root cause and are implementing a fix.
Customers are still seeing degraded service with Deepgram Flux models. We have escalated to Deepgram and are investigating the issue.
Affected components
1Vapi in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
13
Median duration
37 min
This incident
About the median
Other Vapi incidents
All incidentsVapi·Model provider failures ongoing across Cartesia, Deepgram and Elevenlabs
Model provider failures affected the Deepgram, Cartesia and ElevenLabs components in Vapi. Vapi reports that this incident is resolved, and it lasted about 3 hours and 20 minutes.
Vapi·Degraded Service: Insights API and Boards Inaccessible
Vapi reports that the Insights API and Dashboard boards did not work. Calls and structured outputs were not affected. Vapi resolved the issue on 11 November 2026, about 43 hours after it started.
Vapi·Dashboard is unavailable
The issue is resolved and all services have returned to normal.
Vapi·docs.vapi.ai is unavailable
The issue has been resolved upstream and documentation is available once again, we'll continue monitoring to ensure stability.
Vapi·Degraded performance: SIP BYO trunk creation
BYO SIP registration has been re-enabled during scheduled maintenanc and we were able to successfully place outbound calls
Follow Vapi
Your coding agent knows when Vapi is down, and tells you when a failure is theirs, not yours. You can also get Vapi incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "vapi" and tell me if Vapi has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=vapi/feed subscribe https://outages.live/feed.xml?providers=vapiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane