Twilio logged three separate incidents on 10 November 2026, touching Lookup API transactions on Verizon in the US, SMS delivery receipts to Movistar Venezuela, and the email template editor used for SendGrid campaigns. The longest of the three ran 10h 29m. All three were Twilio-side faults, confirmed and resolved by Twilio itself.
Started
05:42 UTC
Duration
Lasted 10h 29m
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: SendGrid Marketing Campaigns, SMS, Latin America, Lookup SIM Swap, Legacy Identity MatchAndAttributes
What happened?
The day's first and longest incident started at 05:42 UTC: Twilio customers saw failure responses for Lookup API transactions specifically on Verizon in the United States. Twilio posted four "investigating" updates over the following seven hours, each pushing the next update further out, before reporting recovery at 14:04 and resolving the incident at 16:06, 10h 29m after it began. A second incident began at 17:57 UTC, affecting SMS delivery receipts from Twilio phone numbers to Movistar subscribers in Venezuela. Twilio was explicit that message delivery itself could still succeed even though receipts were delayed, a useful distinction if you were trying to diagnose this from your own logs. That incident was identified within seven minutes, monitored from 19:11, and resolved at 21:23, a duration of 3h 27m. The third incident started at 21:32 UTC in the email template editor used for SendGrid Marketing Campaigns. Twilio described HTML entities being replaced with plain spaces, links being rewritten after saving, and portions of template content failing to render in preview. Twilio recommended avoiding saves in the HTML code editor as a workaround while engineers worked, and resolved the issue at 23:15, 1h 44m after it began. Across all three incidents, Twilio filed fourteen updates total and no user reports were logged in this window. No post-mortem has been published for any of the three, so the underlying cause of each is not on the record beyond what the status updates state.
Learning
UptimeRobot's own probes against Twilio's API stayed at 100% uptime across 24 hours, 7 days and 30 days, and that reading is accurate: those checks hit the general API surface from EU and NA regions, not the specific paths that broke. Nothing about this day's incidents touched that surface. The Lookup API failure was scoped to one carrier, Verizon, in one country. The SMS delay was scoped to one carrier, Movistar, in one country, and affected delivery receipts rather than delivery itself. The email editor fault was a content corruption bug in a web tool, not an API availability problem at all. A synthetic check watching your own endpoint, or even a general Twilio API check, would not have caught any of these, because the failures lived inside carrier-specific routing and an editor's save path, layers your monitoring was never pointed at. This is the pattern worth recognising: narrow, carrier-specific or feature-specific breakage that a broad green uptime number will not reflect. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.