Is Vapi Down Right Now? Live Vapi Status & Outages | IsDown had 55 outages in the last 2 years totaling 25h 22m of downtime — averaging 2.3 incidents per month.
There were 55 Is Vapi Down Right Now? Live Vapi Status & Outages | IsDown outages since February 12, 2026 totaling 25h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
Our dashboard login provider's service is degraded. Our API remains functional.
Our login provider has recovered and the Vapi dashboard is fully operational again.
On Sunday, September 13, 2026, from 8:24 a.m. to 10:55 a.m. Pacific Time, Vapi Chat experienced a service disruption on both daily and weekly channels. During this period, requests to /session and /session/{id} timed out or returned HTTP 504 (Gateway Timeout) and 500 (Internal Server Error) responses, affecting chat session creation, retrieval, and management. Service was restored at 10:55 a.m. Pacific Time. All other services, including voice calls, were unaffected on both channels.
We're seeing an increased rate of call failures and the team is actively investigating
The incident is resolved.
Incident Report available at https://drive.google.com/file/d/1ORxSZb8NYgVlmPoqnUEdTmlIua3NSl_k/view
OpenAI recovered
We are investigating an issue affecting webhook behavior for a subset of web calls. Calls using private credentials and dashboard call flows are unaffected. We are deploying a fix and will provide another update once validation is complete.
Our documentation hosting provider is currently experiencing an issue which is impacting the availability of Vapi documentation and MCP server. In the meantime you may directly view our documentation repo here: https://github.com/VapiAI/docs At this time there is no evidence of impact to the Vapi dashboard, API, or other services.
Our documentation vendor has resolved their issue and Vapi documentation is now fully available.
Vonage Outbound went down
Telnyx Inbound went down
Telnyx Outbound went down
Vapi Numbers Outbound recovered
Vapi API went down
We are experiencing API Degradation on the daily channel. The team is actively investigating.
We have identified the root cause of this issue and implemented a fix. We've seen a full recovery across our systems and are continuing to monitor for any regressions.
Cartesia went down
Between 10:55 and 11:10 UTC, some API requests and calls failed due to a network performance issue at our upstream network provider affecting US west. EU and Australia regions were not impacted. Service recovered at 11:10 UTC. No action is required. We're continuing to monitor.
SIP Inbound went down
Vapi Numbers Inbound recovered
SIP Outbound went down
Vonage Inbound went down
Twilio Inbound went down
Vapi Call Logs went down
Twilio Outbound went down
Vapi SIP went down
We observed an increase in Dashboard Access degradation due to an outage with our downstream authentication provider. We are investigating the root cause and actively monitoring.
We have engaged our fallback authentication provider restoring access back to the Vapi Dashboard. We will continue to monitor but at this time, we are observing no further issues.
We observed an increase in API error rates between 12:30 and 12:35 am PT, and 12:44 and 12:47. Service levels recovered after 12:47 m PT. We are investigating the root cause and actively monitoring API health.
We observed an increase in API error rates between 12:30 and 1PM PT. Service recovered after 1PM PT. We are investigating the root cause and actively monitoring API health.
We have identified the root cause of this issue and successfully implemented a fix. We will continue to monitor but at this time are observing no further issue.
We noticed a degradation in API success rate only on the daily channel from 11 A.M to 11:04 A.M. Success rate has since recovered and we are not seeing any further degradation - the team will continue to monitor the issue.