- Level
- confirmed
- Worst impact
- Degraded
- Components
- Vapi Docs
- Down Index
- 14of 100
What to do
Check whether you use Vapi Vapi Docs. 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 9m it lasted.
Anything that failed between 2026-10-12 17:54 UTC and 2026-10-12 18: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 2
- downtime
Our documentation is unavailable due to an upstream outage, we're tracking status closely ([Fern](https://status.buildwithfern.com/) -> [Vercel](https://www.vercel-status.com/) -> [GitHub](https://www.githubstatus.com/)) and will notify once service is restored
provider
- resolved
The issue has been resolved upstream and documentation is available once again, we'll 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-08fef45a00
Is Vapi still down?
No, this incident was resolved 2026-10-12 18:03 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
9m, from 2026-10-12 17:54 UTC to 2026-10-12 18:03 UTC, by the times Vapi posted.
What was affected?
Vapi named Vapi Docs.
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.