Delayed Email Validation History
SendGrid Email Validation history and statistics in the SendGrid UI do not show recent results or updated totals. The affected components are Logs and TWILIO EMAIL - Logs. SendGrid has identified the issue and is working on a fix. Mail send is not affected.
State
Identified
Started
Ongoing for
1 h 13 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
1 h 3 min 86%
Identified
10 min 14%
Updates
Times in UTCAs posted by SendGrid
Our engineers have identified the issue and are working toward a fix for the delayed Email Validation history issue. We will provide another update in 1 hour or as soon as more information becomes available.
Starting around 11:30 on 11/04/2026, our engineers began investigating an issue with the Email validation history and statistics shown in the SendGrid UI. Users may not see recent email validation results or updated totals in their validation history. Results validated before the issue began are still visible. This does not impact mail send. We will 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
71
Days with an incident
40
Median duration
9 h 36 min
This incident
87% shorter than the median
Other SendGrid incidents
All incidentsSendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Carriers in United States
SendGrid reports MMS delivery delays from a subset of Twilio Long Codes to multiple small carriers in the United States. The affected components are MMS Long Code, North America, CARRIER NETWORK - MMS Long Code, North America, and ZIPWHIP MESSAGING - MMS Long Code, North America. SendGrid resolved the incident after 54 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes and Short Codes to AT&T United States
SendGrid reported MMS delivery delays and delivery receipt delays for MMS Long Code and MMS Short Code in North America, including CARRIER NETWORK and ZIPWHIP MESSAGING components. The affected messages go to AT&T subscribers in the United States. The incident is resolved, and it lasted about 8 hours.
SendGrid·MMS Delivery Delays and Failures from a Subset of Twilio Short Codes to T-Mobile and Verizon United States
SendGrid reports MMS delivery delays and failures from a subset of Twilio Short Codes to T-Mobile and Verizon subscribers in the United States. The affected components are MMS Short Code and CARRIER NETWORK MMS Short Code in North America. SendGrid reports that the incident is resolved. It lasted about 6 hours and 18 minutes.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes and Long Codes to Brisanet Brazil
SendGrid reported SMS delivery delays from a subset of Twilio Short Codes and Long Codes to Brisanet network subscribers in Brazil. The incident affected SMS in Latin America and the carrier network for SMS in Latin America. SendGrid reports that the incident is resolved. The outage lasted about 14 hours and 47 minutes.
SendGrid·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks United States
SendGrid reports MMS delivery delays and failures from a subset of Twilio Long Codes to subscribers on multiple small networks in the United States. The affected components are MMS Long Code, North America and CARRIER NETWORK - MMS Long Code, North America. SendGrid reports that the incident is resolved after 16 hours and 15 minutes.
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