- Level
- confirmed
- Worst impact
- Maintenance
- Components
- Vapi SIP, Vapi Numbers Outbound, SIP Outbound
- Regions
- us
What to do
Check whether you use Vapi Vapi SIP, Vapi Numbers Outbound, 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-12 04:25 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
We will be upgrading the API server related to outbound calling. Outbound calling will be unavailable for approximately 30 minutes for new outbound call requests. We will validate for the remainder of the window to confirm calls are connecting normally, and update this page when connectivity returns and maintenance is complete.
provider
- update
Outbound API server upgrade was successful. Outbound call is operational. We will continue to monitor for the next 2 hours.
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-d01aa20d29
Is this Vapi maintenance still going on?
No, it ended 2026-10-12 04:25 UTC.
How long did it last?
26m, from 2026-10-12 04:00 UTC to 2026-10-12 04:25 UTC, by the times Vapi posted.
What was affected?
Vapi named Vapi SIP, Vapi Numbers Outbound, 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.