Russia SMS Carrier Maintenance - Tele2
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Twilio.
State
In progress
Started
Ongoing for
1 h 43 min
Worst impact
Maintenance
Timeline
1 updateIn progress
1 h 43 min 100%
Updates
Times in UTCAs posted by Twilio
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
167
Days with an incident
54
Median duration
5 h 27 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·SMS Delivery Failures from a Subset of Twilio Phone Numbers to Zong Pakistan
SMS delivery failures affect a subset of Twilio phone numbers that send to Zong network subscribers in Pakistan. The APAC SMS components are degraded. Twilio reports a recovery and is monitoring service stability.
Twilio·Text to Speech Timeouts
Twilio reports timeouts when users generate speech from text through ElevenLabs Text to Speech in the US1 region, including Speech Recognition (Gather Speech) US1. Twilio later identified the issue, monitored recovery, and marked the incident resolved. The outage lasted about 4 hours and 34 minutes.
Twilio·Voice Call Silent and One-Way Audio from Colombia to a Subset of Twilio Phone Numbers
Voice calls from network subscribers in Colombia to a subset of Twilio Phone Numbers have silent or one-way audio. The issue affects Voice in Latin America and the carrier network in Latin America. Twilio has identified the cause and is working to resolve the issue.
Twilio·Transactional Email Delays in AP
Twilio reported degraded sending of transactional email in the AP region through the v3 Mail Send API. SMTP and v2 mail send continued to operate normally. Twilio reports that the incident is resolved and that it lasted 57 minutes.
Twilio·Voice Call Failures from a Subset of Twilio phone numbers in Brasil
Voice calls fail from a subset of Twilio phone numbers in Brasil, which affects SIP Interface US1 and Programmable Voice US1. Twilio reports that the incident is resolved and that it lasted about 47 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