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.
The latest update from Vapi.
State
Maintenance
Starts
in 6 d
2026-11-08 05:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vapi
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.
Affected components
3Vapi in the last 90 days
Full historyIncidents in 90 days
0
Days with an incident
0
Median duration
Not enough data
This incident
Not comparable
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.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.
https://outages.cc/feed.xml?providers=vapi/feed subscribe https://outages.cc/feed.xml?providers=vapiFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane