Twilio favicon

Twilio outage on 2026-11-03

twilio.com
November 2026 3 Minor incident

On 3 November 2026, Twilio ran ten separate incidents across messaging and voice, touching 11 components in total. The longest, a message queue host that failed to recover, ran for 39h 57m. Twilio's own status page confirms these were faults on their side.

Started

01:29 UTC

Duration

Lasted 1h 9m

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: MMS Long Code, North America, MMS Short Code, North America, SMS, Latin America, SMS, Europe, Voice, North America, Voice, APAC, Voice, Latin America, Voice, Europe, Voice, Middle East & Africa, SMS, Media Streams US1

What happened?

Twilio logged ten distinct incidents on this day, starting at 01:29 UTC with media streams audio delays and continuing through the day with overlapping problems in SMS, voice, and MMS. The worst of them, titled "RateQueue Host Down Did Not Recover", started at 02:14 UTC and ran for 39h 57m before Twilio marked it resolved at 18:09. Twilio's updates on that incident repeat the same line across several hours: messages were delayed but not lost, the cause was mitigated but not yet fully identified. A separate voice incident starting at 02:17 UTC, affecting audio delays and high packet loss on calls using Media Streams, took 16h 54m to resolve. Several of the day's incidents were narrow by carrier: SMS delays to Lycamobile in the United Kingdom, to Entel in Bolivia, and to Brisanet in Brazil each got their own incident page and resolution notice. MMS problems recurred through the day across different carrier combinations in the United States, including T-Mobile, Verizon, and AT&T, with delivery receipts delayed even when the messages themselves reportedly still succeeded. Across the ten incidents, Twilio published 65 status updates in total. No user reports were filed during the window on this page. No post-mortem has been published for any of these incidents, and Twilio's updates do not explain what caused the RateQueue host to fail to recover for nearly 40 hours.

Learning

Twilio's own probes watch api in the eu and na regions, and over this same stretch they show 100% uptime at 24 hours, 7 days and 30 days, with no registration against this incident. That is not a contradiction. The outage sat in SMS, MMS and voice delivery paths, carrier by carrier, not in the API endpoint that a generic health check calls. A request to Twilio's API can succeed every time while the message behind it sits delayed at a carrier gateway, or a voice call carries audio only after packet loss nobody flagged at the API layer. If your own monitoring only pings your endpoints and Twilio's API, this kind of delay or carrier-specific drop can run for hours without tripping anything you control. Over 90 days Twilio has logged 534 incidents with a median duration of 5 hours 57 minutes, so a day like this one, with ten incidents and one running close to 40 hours, is on the longer end but not an outlier for this provider. 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.