- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 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 1h 45m it lasted.
Anything that failed between 2026-05-12 15:18 UTC and 2026-05-12 17:03 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 4
- update
We're seeing an increased rate in call failures and are actively looking into it.
provider
- update
The team is still actively looking into the issue and working on a fix.
provider
- update
The team has identified the issue, scaled the offending service accordingly, and we're starting to see a recovery. We will continue monitoring the situation as it improves.
provider
- resolved
This incident has been resolved. All systems are operating normally
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-d8c22b03f7
Is Vapi still down?
No, this incident was resolved 2026-05-12 17:03 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
1h 45m, from 2026-05-12 15:18 UTC to 2026-05-12 17:03 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.