Twilio logged four separate incidents on 15 November 2026, touching email provisioning, the Lookup API, inbound MMS and long code SMS delivery to Canada. The longest, the Canadian SMS delivery failures, ran 4h 13m. All four were faults on Twilio's side, not yours.
Started
13:16 UTC
Duration
Lasted 2h 36m
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 Long Code, North America, MMS, Lookup SIM Swap, Other
What happened?
Twilio's status page recorded four distinct incidents across the day, each against a different component: Other, Lookup SIM Swap, MMS, and SMS Long Code in North America. The first, starting at 13:16, affected new accounts trying to provision Twilio Email, with Twilio saying some newly created accounts could not use the email product immediately. That one ran 2h 36m before Twilio marked it resolved. At 14:18 a second incident hit the Lookup API, with Twilio customers in the United States seeing failure responses on Lookup transactions. Twilio said it had identified the cause fairly quickly, at 14:27, but kept the incident open through three more updates before confirming recovery at 17:35 and resolution at 18:05, a total of 3h 49m. Later that night, two incidents started within six minutes of each other: inbound MMS errors at 23:02, where Twilio described users hitting error 12300 on inbound MMS, resolved in 1h 35m, and SMS delivery failures from a subset of Twilio long codes to multiple networks in Canada at 23:08, which took the longest to clear at 4h 13m. None of Twilio's updates across any of the four incidents gave a root cause beyond "identified the cause" without naming it. No post-mortem has been published for any of the four. No user reports were filed during the window on this page, so the only account of impact is Twilio's own status updates.
Learning
UptimeRobot's own probes, which check Twilio's API from EU and NA regions every 60 seconds, read 100% uptime over 24 hours, 7 days and 30 days, with no registration against any of these four incidents. That is not a contradiction. The probes watch whether the API endpoint answers, and none of the four incidents here were a flat API outage: they were provisioning delays, Lookup failures scoped to the US, MMS error codes, and SMS delivery failures to specific Canadian networks. A simple reachability check can stay green while a feature-specific or region-specific failure path inside the provider is broken for everyone using it. This is the general shape of a provider-side partial outage: the front door opens fine, but a slice of what happens once you're in is failing. Watching your own endpoints would only tell you your product is passing requests through, not whether Twilio is processing them correctly on the other end. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.