Increased rate of call failures

What to do

• Check whether you use Vapi in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 23h 4m it lasted.

  Anything that failed between 2026-08-19 18:16 UTC and 2026-08-20 17:20 UTC may need a replay.

• Subscribe to Vapi's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=vapi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Vapi 8

1. updateAug 19, 2026, 6:16 PM UTC

   We're seeing an increased rate of call failures and the team is actively investigating

   provider

2. updateAug 19, 2026, 6:36 PM UTC

   We are confirming that calls are not connecting in the US. Our team is still investigating. Next update in 30 min or sooner.

   provider

3. updateAug 19, 2026, 7:01 PM UTC

   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.

   provider

4. updateAug 19, 2026, 7:26 PM UTC

   We have rolled out a mitigation measure and are seeing improvements in call success rate.

   provider

5. updateAug 19, 2026, 7:55 PM UTC

   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.

   provider

6. updateAug 19, 2026, 8:02 PM UTC

   We are seeing recovery on all affected services and have moved to monitoring status.

   provider

7. updateAug 19, 2026, 8:19 PM UTC

   The incident is resolved.

   provider

8. resolvedAug 20, 2026, 5:20 PM UTC

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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.