- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 27of 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 47m it lasted.
Anything that failed between 2026-06-24 20:12 UTC and 2026-06-24 20:59 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 investigating reports of elevated failure rates affecting our API on weekly channel. Our team is actively working to confirm these reports and will provide an update within the next 30 minutes.
provider
- update
We have observed recovery of this issue starting around 1:20PM PT. We identified the root cause of the issue and are working to implement a fix.
provider
- resolved
We have deployed a fix for this issue and will continue to monitor. We have not seen any elevated error rate since 1:20PM PT.
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-b78343492b
Is Vapi still down?
No, this incident was resolved 2026-06-24 20:59 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
47m, from 2026-06-24 20:12 UTC to 2026-06-24 20:59 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.