SendGrid favicon

SendGrid outage on 2026-11-02

sendgrid.com
November 2026 2 Minor incident

Twilio, SendGrid's parent, logged eight separate incidents on 2 November 2026, ranging from SMS delivery delays on specific carrier routes to incorrect account balances shown to customers. Several ran for hours and one voice call failure in the Philippines was still open going into the next day. These were carrier and billing faults on Twilio's side, not something you could have fixed from your own setup.

Started

00:51 UTC

Duration

Lasted 6h 35m

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 00:51 UTC and continuing through the day, with 59 status updates logged in total. Most were narrow SMS routing problems tied to specific carrier and country combinations: Short Codes to Google Voice in the United States, Long Codes to T-Mobile and O2 in the Czech Republic, Alphanumeric Sender IDs to T-Mobile in Austria, Short Codes to Liberty in Puerto Rico, and SMS from Twilio to Claro in Puerto Rico. Each of these resolved within hours, with durations ranging from 2h 54m to 7h 44m. A separate incident affected Silent Network Authentication redirects on XL Axiata in Indonesia, lasting 13h 27m, during which Twilio said API transactions could fail over to SMS OTP as a backup method. The longest incident of the day was not a delivery problem at all: some customers saw incorrect balances reflected on their accounts, an issue that started at 16:37 UTC and ran for 32h 51m before Twilio marked it resolved. The voice call failure affecting a subset of Twilio Philippines phone numbers to multiple networks in the Philippines started at 05:41 UTC and was still open as of the last update shown, with Twilio repeatedly reporting the cause as identified and recovery observed, then extending its update window multiple times without a final resolution filed. No user reports were logged in this window. Twilio's updates place the faults with specific carrier routes and an internal billing calculation, not with any single platform-wide failure.

Learning

Our own probes watched SendGrid's API from EU and North America regions through this entire day and recorded 100% uptime at the 24 hour, 7 day and 30 day marks, with this incident not registered against those checks. That is consistent with what actually broke: carrier-specific SMS routing, a silent authentication redirect, voice calls into one country's networks, and a billing display error. None of these touch the API endpoint an uptime check calls, so a green monitor and a real, hours-long outage for affected customers are both accurate readings of two different layers. If your product relies on SMS reaching Google Voice users in the US, or voice calls connecting in the Philippines, or your customers' account balances displaying correctly, your own endpoint monitoring would have shown nothing wrong while those specific paths failed. The pattern across 423 incidents in the last 90 days, with a median duration of 6 hours 2 minutes, suggests this kind of narrow, carrier-specific disruption is a routine feature of running on Twilio's network rather than an anomaly. 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.