Skip to main content
Vapi

SIP Maintenance

Maintenance Lasted 24m · started · Vapi's page

Level
confirmed
Worst impact
Maintenance
Components
Vapi SIP, Vapi Numbers Inbound, Vapi Numbers Outbound, SIP Inbound, SIP Outbound

What to do

  • Check whether you use Vapi Vapi SIP, Vapi Numbers Inbound, Vapi Numbers Outbound, SIP Inbound and 1 more. 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-09-01 04:24 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

  1. update

    We're performing routine maintenance on our telephony infrastructure. When: Monday, August 31 9-10pm PT What to expect: There will be downtime for ~10min at 9pm in which calls made using Vapi Numbers, directly via our SIP infrastructure, or via SIP trunk will not connect and fail immediately. After, there will be a period where we monitor and validate the maintenance but calls will start connecting again. Action needed: If there are concerns around minutes of downtime, customers can configure an alternate transport (i.e. Twilio) for calls. We'll update this page as the maintenance progresses when SIP calls should be back online and when the update is completed altogether.

    provider

  2. update

    Maintenance has been completed successfully. All systems are operational, and we will continue to monitor for any regressions.

    provider

  3. 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-df7d371433

Is this Vapi maintenance still going on?

No, it ended 2026-09-01 04:24 UTC.

How long did it last?

24m, from 2026-09-01 04:00 UTC to 2026-09-01 04:24 UTC, by the times Vapi posted.

What was affected?

Vapi named Vapi SIP, Vapi Numbers Inbound, Vapi Numbers Outbound, SIP Inbound and 1 more.

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.