Twilio, which operates the messaging infrastructure behind SendGrid, logged eight separate incidents on 9 November, running from SMS delivery failures in Laos to a WhatsApp Business API send failure that was still open at the last update. These were network and carrier level faults on Twilio's side, not something your own code could trigger or fix.
Started
06:57 UTC
Duration
Lasted 16h 8m
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 eight incidents starting at 06:57 UTC on 9 November, affecting SMS delivery and voice calls across several countries plus the WhatsApp Business API. The first began as SMS delivery failures from Twilio to Megacom subscribers in Kyrgyzstan, then was updated to describe the same pattern hitting ETL subscribers in Laos, and ran 16 hours 8 minutes before resolving. A separate incident covered SMS failures from Germany to a subset of Twilio long codes, lasting 8 hours 43 minutes. Bouygues Telecom subscribers in France saw delivery receipt delays, where Twilio noted message delivery could succeed even while receipts lagged, and that incident ran 13 hours 35 minutes. Shorter incidents hit Spusu subscribers in the United Kingdom and multiple networks in Italy, each resolved in a little over three hours. A voice incident covering silent and one-way audio between Twilio and UK networks ran 5 hours 20 minutes, and a separate voice failure to Chile ran 19 hours 21 minutes before resolving at 12:14 UTC. The eighth incident, WhatsApp Business API message send failures starting at 20:32 UTC, reached a monitoring update at 01:01 UTC saying the issue had been mitigated, but no resolved update appears on the record, so it is still open. Across all eight, Twilio's updates describe identified causes and recoveries but do not publish what caused any of the underlying faults. No user reports were filed during this window on our side.
Learning
Our own probes checked SendGrid's API from the EU and North America through the day and recorded 100% uptime over 24 hours, 7 days and 30 days, with this incident not registered against our monitoring at all. That is not a contradiction. Our checks confirm the API endpoint answered when asked, while Twilio's incidents sat further down the stack, in specific carrier routes, long code pools and the WhatsApp Business API backend, none of which a simple reachability check exercises. This is the shape to recognise: your product can call the API successfully and still have messages silently failing to reach subscribers on a particular network in France or Chile, because the fault lives in a hop your monitoring never touches. Twilio's own history here is not rare, with 429 incidents logged across its status page in the last 90 days alone and a median duration of 6 hours 3 minutes, so carrier-specific failures of this kind are a routine part of running on this provider. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.