Twilio, which runs SendGrid's underlying platform, logged four separate incidents on 15 November 2026, starting at 13:16 UTC and running into the next day. The longest, a Canadian SMS delivery failure, lasted 4h 13m. All four were Twilio-side faults, not anything you could have fixed on your end.
Started
13:16 UTC
Duration
Lasted 2h 36m
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?
Twilio's status page recorded four distinct incidents across the day, none of them overlapping in cause as far as the updates show. The first began at 13:16 UTC: new Twilio accounts were hitting provisioning delays getting their email product set up, meaning some freshly created accounts couldn't use Twilio Email right away. That one ran 2h 36m, with Twilio reporting "signs of recovery" at 14:22 before resolving at 15:52. While that was still open, a second incident started at 14:18 UTC affecting the Gateway API's Lookup API, with failure responses for Lookup transactions in the United States. Twilio said it had identified the cause within nine minutes, but the fix dragged, with status updates still being pushed at 15:27 and 17:33 before recovery was observed at 17:35 and resolution landed at 18:05, a total of 3h 49m. Later that night, two more incidents opened almost together: inbound MMS errors (error 12300 on receipt) starting at 23:02 UTC and resolved by 00:37, and SMS delivery failures from a subset of Twilio long codes to multiple Canadian networks starting at 23:08 UTC, which ran the longest of the day at 4h 13m before resolving at 03:18. Across all four, Twilio's own updates describe the symptoms but none explain root cause beyond "identified" labels with no detail attached. No user reports were filed during the window on this page. Components affected aren't broken out individually in Twilio's listing for this day, so the scope is described only through the incident titles themselves.
Learning
UptimeRobot's own probes against SendGrid's API, checked every 60 seconds from both EU and North American regions, showed 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident isn't registered against those probes. That's not a contradiction. The four incidents that day hit account provisioning, phone number lookups, inbound MMS and regional SMS delivery, none of which are the plain API availability check that an external monitor samples. A simple reachability probe can stay green while a specific downstream pipeline, like SMS routing to a subset of Canadian carriers, is failing for real users on that exact path. This is the general shape of provider-side outages: the front door answers fine while a narrower corridor behind it is blocked. Watching your own endpoints wouldn't surface this either, because your systems would just see Twilio's API respond normally while individual messages silently failed or delayed downstream. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.