- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 17of 100
What to do
Check whether your product depends on Vapi. 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 51m it lasted.
Anything that failed between 2026-06-03 12:40 UTC and 2026-06-03 13:31 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 3
- update
We are seeing a high rate of call creation failures. We are investigating and will share updates here.
provider
- update
We implemented a fix and are seeing recovery as of 5:47am PDT. We will continue to monitor and update here.
provider
- resolved
The incident has been resolved, and service restored as of 5:47am PDT.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-177a0ec8b2
Is Vapi still down?
No, this incident was resolved 2026-06-03 13:31 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
51m, from 2026-06-03 12:40 UTC to 2026-06-03 13:31 UTC, by the times Vapi posted.
What caused it?
Vapi hasn't published a root cause. If it does, it shows here.
Where does this come from?
Vapi's official status page, https://status.vapi.ai, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.