Skip to main content
Vapi

Upgrade to SIP infrastructure

Maintenance Lasted 1h · started · Vapi's page

Level
confirmed
Worst impact
Maintenance
Components
SIP Inbound, SIP Outbound

What to do

  • Check whether you use Vapi SIP Inbound, 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.
  • Check that everything you run on Vapi came back after the window closed 2026-10-19 05:00 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 2

  1. update

    We will be updating servers to increase resiliency. During this maintenance period, some in-progress calls may be disrupted. However new calls will still be answered.

    provider

  2. 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-b9b0ed9c23

Is this Vapi maintenance still going on?

No, it ended 2026-10-19 05:00 UTC.

How long did it last?

1h, from 2026-10-19 04:00 UTC to 2026-10-19 05:00 UTC, by the times Vapi posted.

What was affected?

Vapi named SIP Inbound, 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.