Twilio, which operates SendGrid's delivery infrastructure, logged 13 separate incidents on 12 November 2026, touching SMS routes, voice calls and email delivery to Microsoft inboxes. These were carrier and routing problems on Twilio's side, not faults in your own setup.
Started
01:17 UTC
Duration
Lasted 1h 20m
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 13 incidents starting from 01:17 UTC, affecting SMS delivery to carriers in the US, Sierra Leone, Pakistan, Colombia, France, Brazil and Costa Rica, voice call audio and dial delay issues, and a prolonged email delivery delay to Microsoft-hosted inboxes. Most SMS incidents followed the same pattern: Twilio opened an investigation, then identified a carrier-specific cause, then resolved within a few hours. The AT&T long code SMS failure lasted 1h 20m, while the Orange Sierra Leone SMS failure ran for 36h 32m before Twilio called it resolved. The email delay to Microsoft inboxes ran for 34h 11m, with Twilio repeatedly stating that a third-party provider dependency was causing messages to queue longer than usual, and that no mail was being lost. Twilio issued seven separate updates on that one email incident alone, consistently saying mail was deferred rather than dropped. Two incidents were still open as of the last updates Twilio had posted: the Colombia voice call silent and one-way audio issue, last updated when Twilio said it had identified the cause, and the SMS delivery receipt failure to Claro in Costa Rica, last updated when Twilio reported a recovery and said it would keep monitoring. No user reports were filed during this window. Across all 13 incidents, Twilio's own updates are the only record of what happened, and none of them explain why any of these carrier or provider dependencies failed in the first place.
Learning
UptimeRobot's own probes against SendGrid's API showed 100% uptime over 24 hours, 7 days and 30 days, and that is not a contradiction. The probes check whether the API answers, and it did, the whole time. What broke instead sat downstream: SMS routing to specific carriers, voice audio paths through specific networks, and email queuing to one inbox provider. None of that shows up as a failed API call, because the request was accepted and only the delivery leg further down the chain was delayed or dropped. This is the shape to watch for in your own product: a send that succeeds at the API but never lands, or lands late, because of a carrier or provider relationship you have no visibility into. Watching your own endpoints only tells you your side is up, it says nothing about whether SendGrid's delivery partners on the other end are behaving. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.