Elevated Errors Affecting Sip Domain Configuration

What to do

• Check whether you use Twilio Origination US1, SIP Interface US1, Termination US1. 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 33m it lasted.

  Anything that failed between 2026-10-10 05:08 UTC and 2026-10-10 05:40 UTC may need a replay.

• Subscribe to Twilio's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Twilio 2

1. monitoringOct 10, 2026, 5:08 AM UTC

   We are aware of intermittent errors affecting the Voice service, which may impact customer API requests for Voice. From approximately 9:32 PM - 9:47 PM PST, customers may have experienced failed requests. Our team is monitoring system performance. We will provide another update as soon as more information becomes available.

   provider

2. resolvedOct 10, 2026, 5:40 AM UTC

   Between 9:37 PM and 9:47 PM PDT, we experienced a service degradation affecting SIP services due to an outage with a critical downstream provider. During this 10-minute window, customers may have experienced issues with incoming SIP request authentication, as well as an inability to modify SIP Trunk and SIP Domain configurations. The downstream issue has been resolved, and all SIP operations and configuration management functions are now operating normally.

   provider

Corrections

None so far.

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