SendGrid favicon

SendGrid outage on 2026-11-13

sendgrid.com
November 2026 13 Minor incident

On 13 November, Twilio's status page (which also covers SendGrid's messaging infrastructure) logged seven separate incidents spanning voice calls, SMS delivery and verification services across several countries. The longest of these, affecting SMS delivery to Brisanet network subscribers in Brazil, was still open as the day closed. Each of these was a fault on Twilio's side of the network, not yours.

Started

02:33 UTC

Duration

Lasted 28m

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 seven incidents starting at 02:33 UTC and running through the day, with a total of 55 status updates posted across them, 33 of which are reflected here. The first was a 28 minute issue with Elastic SIP Trunking voice calls, resolved by 03:02. Two separate incidents hit SMS delivery and delivery receipts to networks in India within the same few hours, one lasting 3h 14m and the other 50m, both resolved by mid morning. A later incident affected Silent Network Authentication and Lookup API transactions in the United Kingdom for 5h 13m, with Twilio noting that affected transactions could fail over to secondary methods like SMS OTP. A second India SMS delay incident, started at 15:37, ran for 56h 4m before resolution, far longer than the first. Voice calls from Twilio numbers to subscribers in Colombia, Mexico, Chile and Costa Rica failed for 21h 39m starting at 21:56. The longest running incident of the day, SMS delivery delays from Twilio to Brisanet network subscribers in Brazil, began at 22:36 and was still open with no resolution update visible in the record, cycling repeatedly through "identified" and "monitoring" states over many hours. Twilio's updates describe a cause as identified for the Brisanet incident but do not state what that cause was. No user reports were filed during the window for any of these incidents. Twilio's own components list shown in the record is empty, so this page relies entirely on the incident log itself.

Learning

UptimeRobot's own probes against SendGrid's API, checked every 60 seconds from both EU and North American regions, stayed at 100% uptime over 24 hours, 7 days and 30 days, and none of them registered against this incident. That is consistent with what Twilio described: these were routing and delivery problems affecting specific countries, carriers and call paths, such as SMS to one network in Brazil or voice calls to four countries in Latin America, not a failure of the core API endpoint that a synthetic check would reach. A check that hits an API and gets a clean response has no way to see that messages sent through it are stalling somewhere downstream on a specific carrier's network. This is the shape to recognise in your own product: your API calls succeed, your dashboard looks green, but a subset of your end users on a particular network or in a particular country stop receiving messages or calls. Twilio's 90 day history shows 474 incidents with a median duration of 5 hours 57 minutes, so incidents of this kind are routine rather than exceptional for 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.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.