outages.live
Live
VapiIncident ·

New Vapi Phone Number creation degraded

ResolvedOfficial update

New number provisioning has been restored as of 3:00 AM PT today. Creating Vapi phone numbers is working normally again. Thank you for your patience.

The latest update from Vapi.

State

Resolved

Started

Lasted

22 h 45 min

Worst impact

Degraded

Timeline

5 updates
17:1622:5704:3810:1916:01
DegradedUpdate postedTimes in UTC

Degraded

22 h 45 min 100%

Updates

Times in UTC

As posted by Vapi

Resolved

New number provisioning has been restored as of 3:00 AM PT today. Creating Vapi phone numbers is working normally again. Thank you for your patience.

Degraded

No change - we are still awaiting confirmation from our upstream provider to restore new number provisioning. Creating new Vapi phone numbers remains unavailable; existing numbers and imported numbers are unaffected. We will post another update as soon as we have news.

Degraded

We are currently working with our upstream provider to restore new number provisioning. Creating new Vapi phone numbers remains unavailable; existing numbers and imported numbers are unaffected. Next update within the hour or as soon as provisioning is restored.

Degraded

The team has identified the cause and are actively working on a fix. Creating new Vapi phone numbers remains unavailable; while existing numbers and imported numbers are unaffected.

Degraded

We're aware of an issue provisioning new Vapi phone numbers - the team is actively looking into it. Calls to existing numbers and importing numbers from other providers are NOT impacted.

Affected components

2
Vapi Numbers InboundVapi Numbers Outbound

Vapi in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

11

Median duration

23 min

This incident

59× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

22 h 45 min
median 23 min
90 days agoToday

Other Vapi incidents

All incidents

Vapi·Degraded Service: Insights API and Boards Inaccessible

Vapi reports degraded service on the Insights API and the boards in the Vapi Dashboard. Vapi identified the cause and developed a fix. Vapi disabled creating, editing, and running reporting insights while it rolls out the fix, and expects full insights functionality to return tomorrow afternoon (PT).

Degraded

Vapi·Dashboard is unavailable

The issue is resolved and all services have returned to normal.

Resolved

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.

Resolved

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

Resolved

Vapi·SIP Server downtime

There will be reactive maintenance on SIP outbound dialing infrastructure, US region Status: Scheduled What is affected: Our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing, as part of remediating the root cause of today's incident. Inbound calls are not affected. When: Tuesday, October 6, 21:00–21:15 PT (04:00–04:15 UTC, Oct 7) What to expect: This work is not expected to be customer-impacting or noticeable. Outbound calls may briefly stall during the window; any impact should last less than 10 minutes. Action needed: None

Resolved

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.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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane