RateQueue Host Down Did Not Recover
SendGrid SMS message delays occur on the Programmable Messaging SMS components. SendGrid identified the issue and applied a mitigation. SendGrid continues to investigate the root cause.
State
Identified
Started
2 h ago
2026-11-03 02:14 UTC
Ongoing for
1 h 36 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
37 min 39%
Identified
59 min 61%
Updates
Times in UTCAs posted by SendGrid
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available
We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available
Affected components
2SendGrid in the last 90 days
Full historyIncidents in 90 days
64
Days with an incident
39
Median duration
6 h 32 min
This incident
76% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·SMS Delivery Delays from Twilio to Lycamobile United Kingdom
SendGrid reports SMS delivery delays from Twilio to Lycamobile network subscribers in the United Kingdom. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reports a recovery in SMS delivery and monitors service stability.
SendGrid·Voice Call Audio Delays
SendGrid reports voice call audio delays and high packet loss on voice routes to Twilio phone numbers. The affected regions are North America, Latin America, APAC, Europe, and the Middle East and Africa. SendGrid reports a recovery in these calls and now monitors service stability.
SendGrid·Media Streams Audio Delays
SendGrid reports audio delays on Media Streams US1 and PROGRAMMABLE VOICE US1 - Media Streams US1. SendGrid reported the incident as investigating. The incident is now resolved and it lasted 70 minutes.
SendGrid·SMS Delivery Delays and Failures from Twilio to Claro Puerto Rico
SendGrid reports SMS delivery delays and failures to Claro network subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid has identified the cause and is working to resolve the issue.
SendGrid·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
SendGrid reports delays in SMS delivery receipts from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. The affected components are SMS, Latin America and the carrier network for SMS, Latin America. Message delivery may succeed, but delivery receipts may be delayed. SendGrid reports a recovery in delivery receipts and monitors service stability.
Follow SendGrid
Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "sendgrid" and tell me if SendGrid has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane