SIP Server downtime

What to do

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

• Confirm your retries, queues and scheduled jobs caught up after the 3h 5m it lasted.

  Anything that failed between 2026-10-06 21:04 UTC and 2026-10-07 00:09 UTC may need a replay.

• 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. degradedOct 6, 2026, 9:04 PM UTC

   Outbound SIP Server downtime from 1:55 to 2:07, impacting outbound calls and call transfers. Currently seeing recovery, and the team is monitoring closely.

   provider

2. resolvedOct 6, 2026, 9:29 PM UTC

   The root cause has been identified, and the issue has been resolved, with downtime experienced between 1:55 and ending at 2:07

   provider

3. resolvedOct 7, 2026, 12:09 AM UTC

   There will be reactive maintenance on SIP outbound dialing infrastructure, US region Status: Scheduled What is affected: Our SIP infrastructure provider will upgrade the web server/API that controls outbound dialing, as part of remediating the root cause of today's incident. Inbound calls are not affected. When: Tuesday, October 6, 21:00–21:15 PT (04:00–04:15 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 10 minutes. Action needed: None

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.