- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 23of 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 7m it lasted.
Anything that failed between 2026-05-29 03:51 UTC and 2026-05-29 03:58 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 2
- update
We are investigating reports of degraded performance affecting the Vapi Dashboard. Calls do not appear to be impacted. Our team is actively working to determine the root cause and will provide the next update within 30 minutes.
provider
- resolved
We have identified the cause of the issue and reverted the change. The issue has been resolved, and all systems are operating normally. We will continue monitoring to ensure stability.
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-f5834a5bd4
Is Vapi still down?
No, this incident was resolved 2026-05-29 03:58 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
7m, from 2026-05-29 03:51 UTC to 2026-05-29 03:58 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.