- Level
- confirmed
- Worst impact
- Degraded
- Components
- Vapi SIP, SIP Outbound
- Down Index
- 16of 100
What to do
Check whether you use Vapi Vapi SIP, SIP Outbound. 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 21m it lasted.
Anything that failed between 2026-10-02 12:12 UTC and 2026-10-02 12:33 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
- downtime
Calls currently failing for SIP and Vapi member outbound. We are investigating root cause and will update shortly.
provider
- degraded
We have identified the root cause of the issue and the services are recovering. We are monitoring and will update shortly.
provider
- resolved
The issue has been resolved and calls are completing as expected.
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-3b0d60ac0a
Is Vapi still down?
No, this incident was resolved 2026-10-02 12:33 UTC. For Vapi's live state, see https://down.guide/vapi.
How long did it last?
21m, from 2026-10-02 12:12 UTC to 2026-10-02 12:33 UTC, by the times Vapi posted.
What was affected?
Vapi named Vapi SIP, SIP Outbound.
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.