On 14 November, SendGrid's underlying Twilio infrastructure logged four separate SMS delivery delay incidents, each tied to a different carrier route: Telenor Pakistan, MTN Nigeria, Orange Mali and Altan Redes Mexico. The longest, affecting MTN Nigeria, ran for 17 hours 2 minutes. All four were filed and resolved by Twilio, not SendGrid itself.
Started
03:52 UTC
Duration
Lasted 9h 6m
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 on this day, all describing SMS delivery delays rather than outright failures, each scoped to a single phone carrier in a single country. The first began at 03:52 UTC, affecting a subset of Twilio phone numbers sending to Telenor subscribers in Pakistan, and ran for 9 hours 6 minutes before Twilio marked it resolved at 12:57 UTC. A second began at 12:02 UTC, affecting delivery to MTN subscribers in Nigeria, and this was the longest of the four at 17 hours 2 minutes, not resolved until 05:01 UTC the next day. A third, affecting Orange subscribers in Mali, started at 15:05 UTC and lasted 4 hours 26 minutes. A fourth, affecting Altan Redes subscribers in Mexico, started at 17:37 UTC and ran 11 hours 27 minutes. Each incident followed the same pattern on Twilio's log: investigating, then identified, then monitoring once a recovery was observed, then resolved. None of the update text names a root cause beyond identifying which carrier route was affected, so what actually broke on the carrier or routing side is not on the record. Twilio filed 24 updates across the four incidents in total. No components are listed as affected on SendGrid's own status breakdown for this day. No user reports were filed during the window for any of the four incidents. These were narrow, carrier-specific SMS delays, not a platform-wide fault, and each was contained to one country's mobile network.
Learning
UptimeRobot's own probes against SendGrid's API, run from the EU and North America every 60 seconds, showed 100% uptime over 24 hours, 7 days and 30 days, and nothing was registered against this incident. That is not a contradiction. These four incidents were about SMS messages failing to reach specific carriers in Pakistan, Nigeria, Mali and Mexico, a routing and carrier-interconnect problem downstream of the API call itself. An API uptime check from outside those networks has no way to see a delay that only shows up once a message hits a particular mobile carrier's network in a particular country. This is the shape to watch for with any SMS or messaging platform: your own API calls can succeed cleanly while delivery to a specific destination network still lags or fails. Over the last 90 days this provider logged 462 such incidents with a median duration of 6 hours 1 minute, so carrier-specific delays like these are routine rather than exceptional. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.