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.
State
Resolved
Started
1 h ago
2026-11-03 01:29 UTC
Lasted
1 h 10 min
until 2026-11-03 02:39 UTC
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 10 min 100%
Updates
Times in UTCAs posted by SendGrid
We are investigating media streams audio delays. 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
63
Days with an incident
39
Median duration
6 h 32 min
This incident
82% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·Voice Call Audio Delays
SendGrid reports audio delays on voice calls in North America. The affected components are Voice, North America and CARRIER NETWORK - Voice, North America. SendGrid is investigating the incident.
SendGrid·RateQueue Host Down Did Not Recover
SendGrid reports degraded SMS service and the Programmable Messaging SMS component. SendGrid is investigating delays in message delivery. SendGrid states that no messages are lost.
SendGrid·SMS Delivery Delays and Failures from Twilio to Claro Puerto Rico
SendGrid reports SMS delivery delays and failures from Twilio to Claro network subscribers in Puerto Rico. The affected components are SMS, Latin America and the carrier network for SMS, Latin America. SendGrid 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 SMS delivery receipt delays from a subset of short codes to Liberty network subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. SendGrid identified the cause and works to resolve the issue.
SendGrid·Voice Call One-Way Audio from Brazil to a Subset of Twilio Numbers
On October 31, 2026, from 5AM to 8AM PT, customers may have experienced an issue with some inbound calls to Twilio Brazil numbers having no audio, and some calls also dropping. The impact was linked to a carrier fiber cut and a fallback route that could not handle the traffic load. The issue has been resolved and Voice is operating normally.
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