SendGrid favicon

SendGrid outage on 2026-11-16

sendgrid.com
November 2026 16 Minor incident

Twilio, which SendGrid runs on, logged eight separate incidents on 16 November 2026, touching SMS delivery, voice audio, device verification and console features in different countries. Two of the eight were still open as the status page was last updated. None of this was a SendGrid-specific fault, but if your product depends on Twilio's messaging or voice stack, you felt it.

Started

02:16 UTC

Duration

Lasted 16h 7m

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 distinct incidents on this day, starting at 02:16 UTC with device verification timeouts for Silent Network Authentication in the Philippines, which ran for 16h 7m before resolving at 18:19 UTC. A second incident, SMS delivery receipt delays from a subset of Twilio Short Codes to multiple networks in New Zealand, started at 06:35 UTC and was still open as of the last update shown, with Twilio saying as late as 13:56 UTC that it had identified the cause but had not resolved it. SMS delivery delays from Twilio to MTN/Libertis subscribers in Congo ran for 7h 57m, identified quickly but not resolved until 19:06 UTC. A separate SMS delay affecting Telenor subscribers in Pakistan started at 13:21 UTC and moved to monitoring by 14:58 UTC, with no resolved update visible. Voice call audio quality degraded between Twilio and multiple networks in the United Kingdom for 4h 28m, identified at 16:44 UTC and resolved by 20:08 UTC. Three further incidents affected Conversation Intelligence V3 results, Marketplace plugin loading in Console, and SMS delivery to T-Mobile in the United States, each running between roughly two and two and a half hours before resolution. None of Twilio's updates across any of these eight incidents names a root cause beyond identifying which component or route was affected. Across the day, Twilio logged 38 status updates in total. No user reports were filed during this window on UptimeRobot's side.

Learning

UptimeRobot's own probes against the SendGrid API from EU and NA regions showed 100% uptime across the 24 hour, 7 day and 30 day windows, and this incident was never registered against those checks. That is not a contradiction. Every one of the eight incidents Twilio logged this day was scoped to specific SMS routes, specific countries, a specific voice path, or specific console and intelligence features, none of which an external uptime check against the core API endpoint would touch. A probe that sends a request and gets a healthy response back cannot see that delivery receipts to New Zealand are delayed, or that calls in the UK sound degraded, because those failures happen downstream in carrier and network routing that your own monitoring never reaches either. This is the general shape of the failure: the API answers, so your dashboard is green, while a narrow slice of real traffic quietly fails or lags behind. Your own monitoring covers your half, checking that your product calls out and gets a response. UptimeRobot now watches the provider's half too, so next time something like this happens 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.