outages.live
Live
V

Vapi

Vapi is operational

Checked 55 s ago Operational

History

90 days agoToday

Incidents in 90 days

0

Days with an incident

0

Median duration

No data

Longest incident

No data

Components

30
Vapi API Operational
90 days agoNo incidentsToday
Vapi API [Weekly] Operational
90 days agoNo incidentsToday
Vapi Dashboard Operational
90 days agoNo incidentsToday
Vapi Website Operational
90 days agoNo incidentsToday
Vapi Docs Operational
90 days agoNo incidentsToday
Vapi Auth Operational
90 days agoNo incidentsToday
Vapi Chat Operational
90 days agoNo incidentsToday
Vapi SIP Operational
90 days agoNo incidentsToday
Vapi Numbers Inbound Operational
90 days agoNo incidentsToday
Vapi Numbers Outbound Operational
90 days agoNo incidentsToday
SIP Inbound Operational
90 days agoNo incidentsToday
SIP Outbound Operational
90 days agoNo incidentsToday
Twilio Inbound Operational
90 days agoNo incidentsToday
Twilio Outbound Operational
90 days agoNo incidentsToday
Telnyx Inbound Operational
90 days agoNo incidentsToday
Telnyx Outbound Operational
90 days agoNo incidentsToday
Vonage Inbound Operational
90 days agoNo incidentsToday
Vonage Outbound Operational
90 days agoNo incidentsToday
Vapi Call Logs Operational
90 days agoNo incidentsToday
Vapi EU API Operational
90 days agoNo incidentsToday
Vapi EU SIP Operational
90 days agoNo incidentsToday

Providers

OpenAI Operational
90 days agoNo incidentsToday
Anthropic Unknown
90 days agoNo incidentsToday
Google Gemini Unknown
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

No incident in the last 90 days.

Maintenance

SIP Infrastructure Scheduled Maintenance

We will be performing scheduled maintenance on the SIP infrastructure to ensure performance and reliability. Connected calls may be interrupted for 5-10 minutes. However, the platform will be able to take new calls throughout the maintenance period.

Maintenancestarts in 6 d

Affected components

3
  • AnthropicProvidersUnknown
  • Google GeminiProvidersUnknown
  • GladiaProvidersUnknown

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=vapi
Slack
/feed subscribe https://outages.cc/feed.xml?providers=vapi

Go from tracking outages to fixing production issues with Polylane.

Try Polylane