Degraded performance: SIP BYO trunk creation

What to do

• Check whether you use Vapi Vapi SIP. 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 20h 20m it lasted.

  Anything that failed between 2026-10-08 18:27 UTC and 2026-10-09 14:47 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 4

1. degradedOct 8, 2026, 6:27 PM UTC

   We're seeing failures when creating BYO SIP trunks. Existing trunks and calls on them aren't affected. Our team is actively investigating and we'll post an update as soon as we have more information.

   provider

2. degradedOct 8, 2026, 6:57 PM UTC

   We're continuing to investigate failures when creating BYO SIP trunks. Next update within 30 minutes, or sooner if the status changes.

   provider

3. degradedOct 8, 2026, 8:08 PM UTC

   Cause Identified: applying a vendor software update to re-enable the functionality. The patch will be deployed during the dedicated maintenance window 21:00–21:15 PT on October 8 (04:00–04:15 UTC on October 9).

   provider

4. resolvedOct 9, 2026, 2:47 PM UTC

   BYO SIP registration has been re-enabled during scheduled maintenanc and we were able to successfully place outbound calls

   provider

Corrections

None so far.

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