Increased rate of call failures
resolved- Started
- Aug 19, 2:16 PM EDT
- Resolved
- Aug 19, 4:19 PM EDT
- Duration
- 2h 3m
Vapi's updates (8)
- update · Aug 19, 2:16 PM EDT
We're seeing an increased rate of call failures and the team is actively investigating
- update · Aug 19, 2:36 PM EDT
We are confirming that calls are not connecting in the US. Our team is still investigating. Next update in 30 min or sooner.
- update · Aug 19, 3:01 PM EDT
Calls are still failing to connect. Our team has a working hypothesis and we will post as soon as we can confirm the root cause. Next update will be in 30 min or earlier.
- update · Aug 19, 3:26 PM EDT
We have rolled out a mitigation measure and are seeing improvements in call success rate.
- update · Aug 19, 3:55 PM EDT
Some customers are reporting concurrency limits issues. We are resetting all limits to zero for all subscriptions. This change will propagate over the next few minutes.
- update · Aug 19, 4:02 PM EDT
We are seeing recovery on all affected services and have moved to monitoring status.
- resolved · Aug 19, 4:19 PM EDT
The incident is resolved.
- resolved · Aug 20, 1:20 PM EDT
Incident Report available at https://drive.google.com/file/d/1ORxSZb8NYgVlmPoqnUEdTmlIua3NSl_k/view
What our checks recorded
We checked Vapi 24 times from Vapi's start time to its resolution, once every five minutes. Every one of them reached Vapi's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 183 ms, against 165 ms over the 24 hours before. Vapi posted the incident at Aug 19, 2:16 PM EDT.
Updates are Vapi's own words from its status page (status: resolved); we never add an inferred cause.