Skip to main content
Vapi

Emergency maintenance on SIP monitoring server, US region

Maintenance Lasted 25m · started · Vapi's page

Level
confirmed
Worst impact
Maintenance
Components
Vapi SIP
Regions
us

What to do

  • Check whether you use Vapi Vapi SIP 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-13 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

  1. update

    We are doing an emergency upgrade to add capacity for the SIP monitoring server. During the period PCAP files will not be saved.

    provider

  2. update

    Maintenance ended

    provider

  3. update

    The monitoring server was successfully upgraded. We will continue to monitor. PCAP files are available for registered calls.

    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-935dc049ca

Is this Vapi maintenance still going on?

No, it ended 2026-10-13 04:25 UTC.

How long did it last?

25m, from 2026-10-13 04:00 UTC to 2026-10-13 04:25 UTC, by the times Vapi posted.

What was affected?

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