Previous incidents

Incident Report available at https://drive.google.com/file/d/1ORxSZb8NYgVlmPoqnUEdTmlIua3NSl_k/view

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 vendor has resolved their issue and Vapi documentation is now fully available.

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.

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.

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 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 performed critical maintenance on our analytics service, during which the Analytics charts and Insights (Boards) in the Vapi Dashboard were temporarily unavailable or returned errors. Voice calls, call handling, and all APIs operated normally throughout, with no impact to your account settings or call data. The affected features are now fully restored and we're actively monitoring. We apologize for the disruption.

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