SendGrid favicon

SendGrid outage on 2026-11-11

sendgrid.com
November 2026 11 Minor incident

Twilio's status page (which also covers SendGrid's parent infrastructure) logged seven separate incidents through the day on 11 November 2026, all tied to SMS, MMS and voice delivery to specific carriers and regions rather than to SendGrid's email sending itself. The longest ran 16 hours 30 minutes, affecting MMS delivery from a subset of Twilio long codes to multiple US networks. Each incident traces to carrier-side or edge-routing delivery paths, not to a broad platform failure.

Started

12:55 UTC

Duration

Lasted 3h 58m

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 12:55 UTC and running into the following day, with 38 status updates posted across them. The first affected SMS delivery from Twilio to Turkcell subscribers in Turkey, lasting 3 hours 58 minutes, with the cause identified within three minutes of the initial report but recovery not confirmed until 16:49. A short, separate 17 minute incident flagged JS client connectivity issues to the Tokyo edge with no further update filed on the record. Voice call failures in the JP1 region followed, lasting 3 hours 51 minutes, specifically affecting calls made or received using the Voice JavaScript SDK. Three further SMS and MMS incidents ran overnight: delivery failures to K-Cell in Kazakhstan for 7 hours 27 minutes, MMS delivery delays to multiple US networks for 16 hours 30 minutes, and SMS failures to Tcell in Tajikistan for 11 hours 21 minutes. A final incident, SMS delivery delays from Twilio to MTS in Kazakhstan, ran 14 hours 9 minutes and needed eight separate updates before resolution. None of the filings named a root cause beyond "identified," and none link the incidents to each other. No user reports were filed during the window on the record you have. Every incident here is scoped to specific carriers, countries or SDK features rather than to SendGrid or Twilio's platform as a whole.

Learning

UptimeRobot's own probes, which check the API from the EU and North America, stayed at 100% uptime across the last 24 hours, 7 days and 30 days, and that is not a contradiction with the incidents above. These outages were carrier-routing problems, SMS and MMS delivery failing or delaying to specific networks in Turkey, Kazakhstan, Tajikistan and the United States, and voice call failures tied to one SDK in one region. A synthetic check hitting the API endpoint from Europe or North America has no way to see a delivery failure to Turkcell subscribers in Turkey, because the API itself answered normally throughout. This is the shape to watch for in your own product: the thing you can monitor, your own endpoint, stays green, while the thing that actually breaks, delivery to a specific downstream carrier, sits entirely with the provider and its network partners. If your product sends SMS, MMS or voice traffic through Twilio or SendGrid, your dashboard will not tell you a carrier route failed. 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.