Delayed Email Validation History
Twilio reports delayed Email validation history and statistics in the SendGrid UI. This affects the Logs and TWILIO EMAIL - Logs components. Twilio has identified the issue and is working on a fix. Mail send is not affected.
State
Identified
Started
Ongoing for
1 h 48 min
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 3 min 58%
Identified
45 min 42%
Updates
Times in UTCAs posted by Twilio
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.
Our monitoring systems have detected a potential issue with Email history displaying in UI. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
75
Days with an incident
40
Median duration
7 h 52 min
This incident
77% shorter than the median
Other Twilio incidents
All incidentsTwilio·Search Delays on Enterprise Knowledge
Twilio reports elevated latency for search and content ingestion on Enterprise Knowledge. The issue also affects Enterprise Knowledge used with Conversation Intelligence. Twilio is investigating the issue and continues to work on it.
Twilio·SMS Delivery Delays from Twilio to Claro Brazil
Twilio reports SMS delivery delays to Claro network subscribers in Brazil. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio identified the cause and continues to work on the fix. The incident started at 17:15 UTC and continues.
Twilio·SMS Delivery Delays from Twilio to Algar Telecom Brazil
Twilio SMS delivery delays affect messages to Algar Telecom subscribers in Brazil and the SMS Latin America components. Twilio reports a recovery and now monitors service stability. The incident is not resolved.
Twilio·MMS Delivery Failures from a Subset of Twilio Long Codes to GCI United States
MMS delivery failures affected a subset of Twilio Long Codes that send to GCI network subscribers in the United States. Twilio reports that the incident is resolved. The outage lasted about 32 minutes.
Twilio·MMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States
MMS delivery receipts were delayed from a subset of Twilio Long Codes to subscribers on multiple small networks in the United States. Twilio identified the cause and worked on a fix. The incident is resolved and lasted about 8 hours.
Follow Twilio
Your coding agent knows when Twilio is down, and tells you when a failure is theirs, not yours. You can also get Twilio 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.live/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 "twilio" and tell me if Twilio 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.live/feed.xml?providers=twilio/feed subscribe https://outages.live/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane