Notification Delivery Logs Unavailable in Console
Twilio notification delivery logs were unavailable in Console for Conversations and Programmable Messaging Conversations. Twilio mitigated the issue and monitored system performance. The incident is resolved and lasted 8 minutes.
State
Resolved
Started
Lasted
8 min
Worst impact
Notice
Timeline
2 updatesMonitoring
8 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 show new data in Console. The affected components are Notify and PROGRAMMABLE MESSAGING - Notify. Twilio reports that engineers mitigated the issue and now monitor system performance. New records are appearing again for affected services.
Twilio·SMS Delivery Delays Between Twilio and T-Mobile in Czech Republic
SMS delivery delays affect Twilio messages to T-Mobile subscribers in the Czech Republic. The affected components are SMS, Europe and the carrier network for SMS, Europe. Twilio reports a recovery in delivery and monitors service stability.
Twilio·Voice Call Silent and One-Way Audio Between a Subset of Twilio Phone Numbers and Colombia
Twilio Voice in Latin America has silent and one-way audio on calls between some Twilio phone numbers and subscribers on multiple networks in Colombia. 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
SMS delivery receipts are delayed from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS in Latin America and the related carrier network. Twilio has identified the cause and is working to resolve the issue. Message delivery may still succeed.
Twilio·SMS Delivery Failures from Twilio to Lycamobile France
Twilio SMS delivery to Lycamobile network subscribers in France failed. The Twilio SMS and carrier network components in Europe were degraded. Twilio resolved the incident. The outage lasted 4 hours and 51 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.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