Live

Russia SMS Carrier Maintenance - MegaFon

MaintenanceOfficial update

The MegaFon network in Russia is conducting a planned maintenance from 26 November 2026 at 11:00 PST until 26 November 2026 at 17:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MegaFon Russia handsets.

The latest update from Twilio.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Twilio

Scheduled

The MegaFon network in Russia is conducting a planned maintenance from 26 November 2026 at 11:00 PST until 26 November 2026 at 17:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MegaFon Russia handsets.

Affected components

2
SMS, EuropeCARRIER NETWORK - SMS, Europe

Twilio in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

172

Days with an incident

56

Median duration

5 h 34 min

This incident

Not comparable

How long each incident lasted, on the day it started. The outlined bar is this incident.

33 days
median 5 h 34 min
90 days agoToday

Other Twilio incidents

All incidents

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.

Resolved

Twilio·SMS Delivery Delays from Twilio to Proximus Belgium

SMS delivery delays affect Twilio messages to Proximus network subscribers in Belgium, in the SMS and carrier network components for Europe. Twilio reports a recovery in SMS delivery and monitors service stability. The incident is not resolved.

Degraded

Twilio·On Call Engineers are Investigating

Twilio reported a problem with User Account Roles on the Twilio Platform in the Other component. Twilio investigated the issue and then reported it resolved. The incident lasted about 18 minutes.

Resolved

Twilio·Voice Call Failures from a Subset of Twilio Phone Numbers to Argentina

Voice calls from a subset of Twilio Phone Numbers to network subscribers in Argentina failed. The Voice, Latin America and CARRIER NETWORK - Voice, Latin America components had degraded service. Twilio reports that the incident is resolved. The incident lasted about 7 hours and 38 minutes.

Resolved

Twilio·SMS Delivery Delays from Twilio to ISP Telecom United States

SMS delivery delays affected Twilio messages to ISP Telecom network subscribers in the United States. The affected components were SMS Long Code, SMS Short Code, and SMS Toll-Free in North America, including the carrier network. Twilio reports that the incident is resolved and that SMS delivery operates normally. The incident lasted about 9 hours and 37 minutes.

Resolved

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.

Prompt
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.

RSS
https://outages.live/feed.xml?providers=twilio
Slack
/feed subscribe https://outages.live/feed.xml?providers=twilio

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane