SendGrid favicon

SendGrid outage on 2026-11-03

sendgrid.com
November 2026 3 Minor incident

Twilio, which underpins SendGrid's delivery infrastructure, filed ten separate incidents on 3 November 2026 covering voice, SMS and MMS delivery delays across multiple carriers and countries. The longest ran 39 hours 57 minutes. These were faults on Twilio's side of the network, not yours.

Started

01:29 UTC

Duration

Lasted 1h 8m

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 opened its first incident at 01:29 UTC for media streams audio delays, and from there the day filled up with overlapping reports: voice call audio delays, SMS delays to Lycamobile in the United Kingdom, SMS delays to Entel in Bolivia, MMS delays to small networks and GCI in the United States, SMS delays to Brisanet in Brazil, and further MMS delivery problems touching T-Mobile, Verizon and AT&T subscribers. Ten incidents in total were logged, against total of 65 status updates across them. The worst of the ten, a rate queue host issue first reported at 02:14 UTC, stayed open for 39 hours 57 minutes and went through five "identified" updates before Twilio called it resolved at 18:09 UTC. Several updates on that incident repeat that messages were delayed but none were lost, which is Twilio's own characterisation rather than an independent check. No update explains what actually caused the rate queue host to fail. Twilio's status page gives no root cause for most of these ten incidents either, only that a fix was identified and later confirmed working. No user reports were filed during the window on our side. Historically Twilio logs about 10.9 incidents a month on this status page, and the median incident over the last 90 days runs 6 hours 4 minutes, so this day's volume and duration both sit above what is typical even for a provider that files frequently.

Learning

UptimeRobot's own probes watched SendGrid's API from both EU and NA regions through this entire day and recorded 100% uptime at 24 hours, 7 days and 30 days, with this incident never registering against those checks. That is not a contradiction. The faults Twilio reported sat in specific delivery paths, things like SMS routing to one mobile network in one country, or MMS delivery receipts on a subset of long codes, which a generic API reachability check from outside has no way to see. Your own monitoring of your integration would show the same gap: your endpoint can be healthy while messages to a particular carrier are stuck behind a queue you don't control and can't inspect. This is the general shape of a delivery provider outage, narrow enough to miss on a top level check but wide enough to delay real messages to real recipients. 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.