Twilio's status page, which also covers SendGrid, logged five separate incidents on 28 September 2026, the longest running 40h 23m. Each one was a carrier-level messaging fault on Twilio's side, not a problem with your own integration.
Started
08:26 UTC
Duration
Lasted 5h 12m
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 five incidents through the day. The first, starting at 08:26, was SMS delivery failures from Twilio to multiple networks in Spain, resolved after 5h 12m once Twilio observed recovery and monitored stability before closing it out. A second incident starting at 10:45 covered voice call failures from a subset of Twilio mobile numbers to Vodafone subscribers in the United Kingdom, open for 16h 57m with updates stretching from 10:45 through to resolution at 03:38 the next day. The longest incident, starting at 13:25, was SMS delivery receipt delays from Twilio to CTBC network subscribers in Brazil. Twilio said message delivery itself could succeed even while receipts lagged, and kept the incident in "identified" status across seven updates spanning 08:26 to the following morning before resolving it at 05:45, a total of 40h 23m. A fourth, brief incident at 19:50 was flagged by Twilio's own automated monitoring against Flex, and closed 1h 55m later with Twilio stating there was no noticeable customer impact. A fifth item logged at 21:12 was a retrospective note: a Bulk Messaging API issue that had actually run from 12:00pm to 12:30pm PDT on 16 September, causing elevated HTTP 503 errors and timeouts, filed on this date as resolved. None of these updates mention SendGrid by name or list SendGrid components as affected, since Twilio's status page groups its products together. One user report during the window, filed from Brazil at 21:48, said "Sendgrid website not loading", which does not map directly to any of the five logged incidents. No post-mortem has been published for any of the five, and none of the updates explain a root cause beyond naming the affected carrier or network.
Learning
UptimeRobot's own probes against SendGrid's API, run from both EU and NA regions every 60 seconds, showed 100% uptime across the last 24 hours, 7 days and 30 days, with no registration against any of these incidents. That is consistent with what Twilio reported: these were carrier-to-carrier delivery and receipt problems for SMS and voice traffic routed through specific networks in Spain, the UK and Brazil, not failures of SendGrid's API endpoint itself. A probe hitting an API endpoint checks that the endpoint answers, it cannot see whether a message you sent then failed to reach a Vodafone subscriber in the UK or a CTBC subscriber in Brazil three steps downstream. That is the shape of this kind of outage: your calls succeed, your emails or messages get accepted, and the failure shows up later, in delivery to specific networks, where your own monitoring never looks. The one user report, a loading complaint from Brazil, does not match any of the five carrier-specific incidents on record, which is a reminder that status pages and user complaints do not always line up neatly. Your monitoring covers your half, checking that your own integration and endpoints respond, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
