Twilio logged five separate incidents on 4 November 2026, touching MMS delivery to a US carrier, SMS delivery to two Brazilian carriers, email validation history and Enterprise Knowledge search. The longest ran 5h 21m, and all five were faults on Twilio's side rather than anything in your own setup.
Started
00:27 UTC
Duration
Lasted 33m
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: Enterprise Knowledge, Logs, SMS, Latin America, MMS Long Code, North America
What happened?
The first incident started at 00:27 UTC, when Twilio reported MMS delivery failures from a subset of its Long Codes to GCI subscribers in the United States. That one ran 33 minutes and only has the single investigating update on record, so there's no confirmation of what caused it or how it was fixed. The bulk of the day's trouble sat in the afternoon and evening UTC hours. At 16:02 Twilio opened an SMS delivery delay affecting Algar Telecom subscribers in Brazil, identifying a cause within four minutes but not confirming recovery until 19:12 and resolving at 21:21, a total of 5h 21m. A near-identical pattern hit Claro subscribers in Brazil starting at 17:15, also identified quickly, recovering around 19:53 and resolved at 21:59, for 4h 44m. Separately, Twilio's SendGrid component reported delayed Email Validation history starting around 11:30 local engineering time and logged at 17:54 UTC, affecting the validation history and statistics shown in the UI. Twilio was explicit that mail send itself was not affected and that previously validated results stayed visible, resolving at 20:42 after 2h 49m. The fifth incident, starting at 18:20, involved elevated latency when searching and ingesting content in Enterprise Knowledge, also affecting Conversation Intelligence users, running 4h 35m before resolution at 22:53. Across all five incidents Twilio filed 22 updates in total. No user reports were filed during the window on any of these. Twilio's own history shows 534 incidents in the last 90 days with a median duration of 5 hours 54 minutes, so a day with five distinct faults clustered in the afternoon is within the pattern this provider has been running.
Learning
UptimeRobot's own probes against Twilio's API, run from the EU and North America every 60 seconds, held 100% uptime across the 24 hour, 7 day and 30 day windows, and none of these five incidents registered against that monitoring. Both readings are accurate at once. External API checks confirm that the core request path answers, but they can't see delivery delays to a specific carrier's network, delayed statistics inside a UI panel, or search latency inside a feature like Enterprise Knowledge. Those are failures inside Twilio's delivery and processing pipelines, downstream of the API call that succeeded. Over the last 30 days UptimeRobot recorded 100 incidents against Twilio with a median duration of 7h 15m, so this kind of carrier-specific or feature-specific delay is routine rather than a one-off. If your product sends SMS through Twilio to Brazilian carriers, validates emails, or queries Enterprise Knowledge, a green uptime check tells you nothing about any of these. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.