On 7 November, Twilio's status page (SendGrid's parent) logged four separate SMS delivery problems spanning New Zealand, India, the United States and the Philippines. The longest, affecting New Zealand short codes, ran 51 hours 30 minutes. All four were delivery receipt or delivery delays on Twilio's SMS network, not a SendGrid email fault.
Started
02:57 UTC
Duration
Lasted 2d 3h
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 incidents through the day, all tied to SMS rather than email sending. The first started at 02:57 and ran 51 hours 30 minutes: delivery receipts from a subset of Twilio short codes to multiple New Zealand networks were delayed, though Twilio noted message delivery itself might still succeed. A second incident began at 13:00 and lasted 3 hours 41 minutes, covering SMS delivery delays from Twilio to multiple networks in India. A third, starting at 19:37 and running 21 hours 38 minutes, hit SMS delivery receipts from a subset of Twilio long codes and short codes to multiple US networks. The fourth, from 21:22 and lasting 13 hours 20 minutes, affected SMS delivery receipts from Twilio to Globe network subscribers in the Philippines. Across all four, Twilio repeatedly stated the cause had been identified but never named it publicly in any update shown. Each incident followed the same pattern: investigating, identified, monitoring, resolved, with updates spaced hours apart as Twilio pushed back its own promised check-in times repeatedly. No components list was published alongside these incidents. No user reports were filed during the window on this page, so the only record of impact is Twilio's own updates. Twilio's wording throughout distinguishes between message delivery and delivery receipts, meaning actual message sending may have worked even while confirmation data lagged.
Learning
All four incidents here affected SMS delivery receipts or delivery timing on Twilio's network, a layer that sits entirely outside anything an API uptime check on your own product would see. UptimeRobot's probes against the API component held 100% uptime across 24 hours, 7 days and 30 days, which is consistent with Twilio's own wording: message delivery could succeed while only the receipt confirmation was delayed. That is the general shape of this kind of fault, the thing that breaks is a secondary signal, not the primary function, so a simple up or down check on your own endpoint stays green throughout. Your own monitoring will tell you your application is up and calling out correctly. It will not tell you that a carrier-side receipt pipeline in New Zealand, India, the US or the Philippines is running hours behind. Twilio's history over 90 days shows 420 incidents with a median duration of 6 hours 2 minutes, so delays of this kind are a known recurring pattern rather than a one-off. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.