Twilio, which operates SendGrid's underlying messaging infrastructure, reported two separate failures on 2026-11-08: verification and lookup requests failing through EnStream in Canada for 14h 13m, and SMS delivery to MTN Nigeria failing for 6h 1m. Both were carrier-side problems on Twilio's status page, not faults in SendGrid's own systems.
Started
14:58 UTC
Duration
Lasted 14h 13m
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 logged two incidents on this day, both tied to specific carrier routes rather than to SendGrid's core platform. The first started at 14:58 UTC and affected Silent Network Authentication and Lookup API transactions routed through EnStream in Canada, with Twilio noting that affected transactions could fail over to secondary methods like SMS OTP. Twilio said it identified the cause at 16:59 UTC but gave no detail on what that cause was, and spent the next several hours working with what it called its "Service Provider" before observing recovery at 23:00 UTC. The incident was marked resolved at 05:11 UTC the following day, a total of 14h 13m. The second incident began at 23:19 UTC, initially described as SMS delivery failures to "multiple networks in multiple countries" before Twilio narrowed it, within 44 minutes, to MTN network subscribers in Nigeria specifically. That incident ran 6h 1m, with recovery observed at 03:19 UTC and resolution confirmed at 05:20 UTC. In both cases Twilio named a root cause only in the vaguest terms, pointing to an external carrier without saying what went wrong on that carrier's end. No post-mortem has been published for either incident. No user reports were filed during the window on this page, and the components_affected list is empty, meaning Twilio's own status categorisation did not tag a specific SendGrid or Twilio component for either event.
Learning
Both incidents sat outside SendGrid's own application layer: they were failures in specific carrier connections, EnStream in Canada and MTN in Nigeria, that Twilio's network relies on to complete verification and SMS delivery. UptimeRobot's own API probes, run from the EU and North America at 60 second intervals, stayed at 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was not registered against those probes. That is not a contradiction. A probe hitting the API endpoint checks whether SendGrid's API is reachable and responding, not whether a message actually gets delivered through a particular third party carrier on the other side of the world. This is the shape to recognise: your own monitoring will often stay green while a downstream carrier silently drops or delays delivery to a specific country or network. Twilio's history shows this is a recurring pattern, with 420 incidents in the last 90 days and a median duration of 6 hours 1 minute, so route-specific failures like these are routine rather than rare. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.