- Level
- confirmed
- Worst impact
- Maintenance
- Components
- SIP Outbound
- Regions
- us
What to do
Check whether you use Vapi SIP Outbound in us. 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.Check that everything you run on Vapi came back after the window closed 2026-10-07 04:32 UTC.
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
This maintenance period is a reactive patch, as our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing to remediate the root cause of today's incident. Inbound calls are not affected. When: Tuesday, October 6, 21:00–21:15 PT (04:00–04:00 UTC, Oct 7) What to expect: This work is not expected to be customer-impacting or noticeable. Outbound calls may briefly stall during the window; any impact should last less than 15 minutes. Action needed: None
provider
- update
Maintenance was successfully complete. We verified that all servers are operating normally.
provider
- update
Maintenance ended
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-6686a6802c
Is this Vapi maintenance still going on?
No, it ended 2026-10-07 04:32 UTC.
How long did it last?
32m, from 2026-10-07 04:00 UTC to 2026-10-07 04:32 UTC, by the times Vapi posted.
What was affected?
Vapi named SIP Outbound in us.
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.