- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 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 9d 6h it lasted.
Anything that failed between 2026-03-10 12:46 UTC and 2026-03-19 18:51 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're noticing a small percentage of calls using GPT 5.2 fail with an internal error during inference from OpenAI's side. We've reached out to the team and are closely monitoring the situation. In the meantime, we recommend switching to another model as we're seeing the degradation only on 5.2 currently.
provider
- resolved
The issue has been resolved we're not seeing any further degradation
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-95e835a34d
Is Vapi still down?
No, this incident was resolved 2026-03-19 18:51 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
9d 6h, from 2026-03-10 12:46 UTC to 2026-03-19 18:51 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.