Twilio favicon

Twilio outage on 2026-11-16

twilio.com
November 2026 16 Minor incident

Twilio filed eight separate incidents on 16 November 2026, touching SMS delivery, voice audio quality, Console and Conversation Intelligence across markets from the Philippines to the UK and the US. Several were still open at the last update Twilio published. The faults sat on Twilio's side, inside specific carrier routes and services, not in anything you control.

Started

02:16 UTC

Duration

Lasted 16h 7m

Source

IsDown

Next time

Twilio is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

Affected components: SMS Short Code, North America, Console, Conversation Intelligence, Voice, Europe, SMS, APAC, SMS, Middle East & Africa, Verify Silent Network Auth

What happened?

Twilio logged eight incidents through the day, starting at 02:16 UTC with device verification timeouts for Silent Network Authentication in the Philippines and running through to a Short Code delivery delay to T-Mobile in the United States at 17:36 UTC. The SNA incident ran 16 hours 7 minutes before Twilio marked it resolved at 18:19 UTC, with API transactions failing over to secondary methods like SMS OTP in the meantime. A separate SMS delivery receipt delay affecting a subset of Short Codes to multiple networks in New Zealand started at 06:35 UTC and was still open as of the 13:56 UTC update, the last one on record, with Twilio saying it had identified the cause but not resolved it. SMS delivery to MTN/Libertis subscribers in Congo was delayed for 7 hours 57 minutes before resolving at 19:06 UTC. A Telenor Pakistan SMS delay, a UK voice audio quality degradation affecting multiple networks, and a second Short Code delay to T-Mobile in the US each reached a "monitoring" update but no confirmed resolution in what Twilio has published so far. Two incidents closed faster: Conversation Intelligence V3 results being unavailable from the intelligence.twilio.com endpoints, fixed and resolved within 2 hours 17 minutes, and a Console fault stopping customers loading Marketplace plugins, resolved in 2 hours 3 minutes. Across the day Twilio posted 36 status updates on these eight incidents. No user reports were filed during the window on this page, and Twilio's updates are the only record of what happened. Twilio's postings describe failover behaviour and partial symptoms, for example saying message delivery may succeed while receipts lag, but they do not explain root cause for any of these eight.

Learning

UptimeRobot's own checks against Twilio's API stayed green throughout, with 100% uptime over 24 hours, 7 days and 30 days from probes run in the EU and North America at 60 second intervals. That is consistent with what Twilio reported: these were narrow failures inside specific routes, such as SMS to one carrier in one country, or one Console feature, or audio quality on calls through particular UK networks, not a general outage of the Twilio API surface that an external endpoint check would catch. A synthetic probe hitting a healthy API endpoint has no way to see that Short Code delivery receipts to New Zealand are delayed, or that SNA verification in the Philippines is timing out and falling back to SMS OTP. This is the normal split between your monitoring, which watches whether your product's calls to Twilio succeed, and Twilio's own internal state across its hundreds of carrier interconnects and country-specific routes. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.