- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 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 4h 53m it lasted.
Anything that failed between 2026-06-26 19:55 UTC and 2026-06-27 00:48 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 are investigating reports of high latency when viewing logs within the dashboard. At this time we do not see any impact to call success rate, this issue appears isolated to accessing logs of calls once completed.
provider
- update
We have identified the root cause of this issue and are working to deploy a fix.
provider
- update
We are continuing our work to deploy this fix across our services. Our next update will be once the fix is successfully deployed everywhere.
provider
- resolved
We have deployed a fix for this issue and are observing full resolution. All systems are fully operational. Our team will continue to monitor.
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-c4b95c050c
Is Vapi still down?
No, this incident was resolved 2026-06-27 00:48 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
4h 53m, from 2026-06-26 19:55 UTC to 2026-06-27 00:48 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.