Russia SMS Carrier Maintenance - Tinkoff Mobile
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Twilio.
State
Resolved
Started
Lasted
6 h 6 min
Worst impact
Maintenance
Timeline
3 updatesScheduled
3 min 1%
In progress
6 h 3 min 99%
Updates
Times in UTCAs posted by Twilio
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The Tinkoff Mobile network in Russia is conducting an emergency maintenance from 21 November 2026 at 12:00 PST until 21 November 2026 at 19:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tinkoff Mobile Russia handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.
Affected components
1Twilio in the last 90 days
Full historyIncidents in 90 days
175
Days with an incident
58
Median duration
5 h 34 min
This incident
Not comparable
Other Twilio incidents
All incidentsTwilio·Gateway API (Lookup API) Failure Increase in Canada
Twilio reports failures for Lookup API transactions in Canada. The affected components are Lookup SIM Swap and CARRIER NETWORK - Lookup SIM Swap. Twilio is investigating the issue.
Twilio·Twilio Help Center Chat Creation and Retrieval Failures
Twilio Help Center chat creation and retrieval failed, which affected the Customer Support Center and the Twilio Platform Customer Support Center. Twilio reports that the incident is resolved and lasted 93 minutes. Twilio said customers who could not continue an existing chat could start a new chat.
Twilio·SMS Delivery Receipt Delays from a Subset of Twilio Phone Numbers to CTBC Brazil
SMS delivery receipts from a subset of Twilio phone numbers to CTBC network subscribers in Brazil were delayed. Twilio identified the cause and later saw a recovery. The incident is resolved and lasted about 5 hours and 14 minutes.
Twilio·Subset of API Requests Blocked with 403 Response
A subset of Twilio REST API requests are blocked with a 403 response. Twilio reports that the incident is resolved and that service is fully restored. It lasted 50 minutes, from 17:06 UTC to 17:56 UTC on 20 November 2026.
Twilio·SMS Delivery Delays from Twilio to Proximus Belgium
SMS delivery delays affected Twilio messages to Proximus network subscribers in Belgium. Twilio reports that the incident is resolved and SMS delivery is operating normally. The incident lasted about 7 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