Russia SMS Carrier Maintenance - MTT
The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
The latest update from Twilio.
State
Scheduled
Starts
in 2 h
2026-11-02 20:55 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Twilio
The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
The MTT network in Russia is conducting a planned maintenance from 02 November 2026 at 12:55 PST until 02 November 2026 at 14:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTT Russia handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
Affected components
2Twilio in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
38
Median duration
7 h 14 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Some Customers May Have Incorrect Balances Reflected on Their Account
Twilio reports that some customer accounts show incorrect balances. The Billing component and the Twilio Platform Billing component are affected. Twilio is investigating the issue and states that work to deploy a fix is in progress.
Twilio·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
Twilio SMS delivery delays and failures affect Alphanumeric Sender Type messages to T-Mobile subscribers in Austria, in the SMS Europe and carrier network components. Twilio identified the cause and now reports a recovery in delivery. Twilio monitors service stability.
Twilio·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
Twilio SMS delivery delays affected a subset of Twilio Long Codes to T-Mobile and O2 network subscribers in the Czech Republic. Twilio reports the incident resolved. It lasted about 2 hours and 54 minutes.
Twilio·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
Silent Network Authentication (SNA) on XL Axiata in Indonesia does not complete device verification. API transactions can fail over to SMS OTP. Twilio reports the state as monitoring after a recovery in API transactions.
Twilio·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
Twilio reports voice call failures from a subset of Twilio Philippines phone numbers to network subscribers on multiple networks in the Philippines. The affected components are Voice, APAC and CARRIER NETWORK - Voice, APAC. Twilio identified the cause and is working to resolve the issue.
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