Twilio, which operates SendGrid's underlying infrastructure, logged three separate incidents on 10 November 2026, the longest running 10h 29m. If your product sends email campaigns, SMS, or does phone number lookups through Twilio, you may have seen failures or delays that had nothing to do with your own code.
Started
05:42 UTC
Duration
Lasted 10h 29m
Source
IsDown
Next time
SendGrid 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.
What happened?
The day's first incident started at 05:42 UTC and was the longest, lasting 10h 29m. It affected Gateway API Lookup transactions specifically for Verizon numbers in the United States, meaning customers using Twilio's Lookup API saw failure responses when checking Verizon numbers, while other carriers were unaffected. Twilio posted five updates during that incident, each pushing the next check back further, from one hour out to eventually eight hours, before confirming recovery at 14:04 UTC and resolving at 16:06 UTC. A second incident began at 17:57 UTC and ran 3h 27m, this time hitting SMS delivery receipts from Twilio phone numbers to Movistar subscribers in Venezuela. Twilio was explicit that message delivery itself may have succeeded even though receipts were delayed, a distinction that matters if your product relies on receipts to confirm sends. The third incident started at 21:32 UTC and lasted 1h 44m, affecting the email template editor used to build campaigns, with HTML entities being replaced by spaces, links rewritten, and template content not rendering correctly after saving or previewing. Twilio identified the cause within 14 minutes and offered a workaround, avoiding the HTML code editor, before mitigating at 22:17 UTC and resolving at 23:15 UTC. None of the three incidents named a root cause beyond identifying the affected feature. No components are listed as formally affected in Twilio's status breakdown for this day, and no user reports were filed during the window on this page.
Learning
UptimeRobot's own probes against SendGrid's API, run from the EU and North America every 60 seconds, stayed at 100% uptime across the 24 hour, 7 day and 30 day windows, and that reading is accurate for the API surface it checks. What it would not have caught is any of these three incidents, because each one was narrow: Lookup API failures limited to one US carrier, SMS receipt delays limited to one Venezuelan carrier, and a template editor bug that only shows up when you save or preview HTML. A generic uptime check hitting the main API endpoint has no reason to touch a Verizon-specific lookup, a Movistar-Venezuela delivery path, or the email campaign editor's rendering logic. This is the common shape of Twilio-side outages: the core service answers fine, but a specific carrier route or a specific feature breaks underneath it. Your own monitoring of your integration covers your half, confirming your requests go out correctly, but it cannot see into Twilio's carrier routing or editor backend. UptimeRobot now watches the provider's half too, so next time something breaks you know which side it was without guessing.