Cartesia recovered
Timeline · 1 update
- investigating Aug 01, 2026, 01:29 AM UTC
Cartesia went down
Is Vapi Down Right Now? Live Vapi Status & Outages | IsDown had 50 outages in the last 2 years totaling 8h 19m of downtime — averaging 2.1 incidents per month.
There were 50 Is Vapi Down Right Now? Live Vapi Status & Outages | IsDown outages since February 12, 2026 totaling 8h 19m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 Outbound went down
Vonage Inbound went down
Twilio Inbound went down
Vapi Call Logs went down
Vapi API went down
Telnyx Outbound went down
Telnyx Inbound 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.
We are aware of and are investigating degradation in API success rate in the daily channel.
We observed an increase in API error rates between 11:00 and 11:04 am PT, affecting only the daily channel. Service levels recovered after 11:04 m PT. We are investigating the root cause and actively monitoring API health.
We are investigating reports of high latency when viewing logs within the dashboard. At this time we do not see any impact to call success rate, this issue appears isolated to accessing logs of calls once completed.
We have deployed a fix for this issue and are observing full resolution. All systems are fully operational. Our team will continue to monitor.
We are investigating reports of elevated failure rates affecting our API on weekly channel. Our team is actively working to confirm these reports and will provide an update within the next 30 minutes.
We have deployed a fix for this issue and will continue to monitor. We have not seen any elevated error rate since 1:20PM PT.
Vapi API [Weekly] recovered
We are observing elevated error rates across API endpoints in the daily channel. The team is actively investigating.
We are observing elevated error rates across API endpoints in the daily and weekly channels. The team is actively investigating.
We have implemented a fix and observed full recovery. Failures were observed beginning 5:45pm and resolved as of 6:05pm.
We observed an increase in API error rates between 12:05-12:10pm PT affecting both daily and weekly channels. Service levels recovered after 12:10pm PT. We are investigating the root cause and actively monitoring API health.
OpenAI went down
We are seeing a high rate of call creation failures. We are investigating and will share updates here.
The incident has been resolved, and service restored as of 5:47am PDT.