Notification Delivery Logs Unavailable in Console
Twilio notification delivery logs were unavailable in Console for Conversations and Programmable Messaging Conversations. Twilio reports that the issue is resolved. The outage lasted about 7 minutes.
State
Resolved
Started
Lasted
7 min
Worst impact
Notice
Timeline
2 updatesMonitoring
7 min 100%
Updates
Times in UTCAs posted by Twilio
Our engineers have mitigated the issue and are monitoring system performance. Notification delivery logs in Console are returning to normal, and new records are appearing again for affected services. We will provide another update in 2 hours or as soon as more information becomes available.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
83
Days with an incident
42
Median duration
6 h 53 min
This incident
98% shorter than the median
Other Twilio incidents
All incidentsTwilio·Notification Logs Unavailable in Console
Twilio Notify notification delivery logs do not populate new data in the Console. Twilio reports that engineers mitigated the issue and now monitor system performance. Logs are returning to normal and new records appear again for affected services.
Twilio·SMS Delivery Delays Between Twilio and T-Mobile in Czech Republic
Twilio reports SMS delivery delays between Twilio and T-Mobile subscribers in the Czech Republic. The affected components are SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio identified the cause and now monitors service stability after a recovery.
Twilio·Voice Call Silent and One-Way Audio Between a Subset of Twilio Phone Numbers and Colombia
Twilio reports silent and one-way audio on voice calls between a subset of Twilio Phone Numbers and network subscribers in Colombia. The issue affects Voice in Latin America and the carrier network for Voice in Latin America. Twilio has identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico
Twilio reports SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. The affected components are SMS, Latin America and CARRIER NETWORK - SMS, Latin America. Twilio identified the cause and is working to resolve the issue.
Twilio·SMS Delivery Failures from Twilio to Lycamobile France
Twilio SMS delivery failures affected messages to Lycamobile network subscribers in France. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. Twilio reports that the incident is resolved. It lasted about 4 hours and 52 minutes.
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.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 "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.cc/feed.xml?providers=twilio/feed subscribe https://outages.cc/feed.xml?providers=twilioFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane