Live

Russia SMS Carrier Maintenance - MTS

MaintenanceOfficial update

The MTS network in Russia is conducting a planned maintenance from 02 November 2026 at 19:00 PST until 02 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTS Belarus 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 SendGrid.

State

Scheduled

Starts

in 4 h

2026-11-03 03:00 UTC

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by SendGrid

Scheduled2026-11-02 21:06 UTC

The MTS network in Russia is conducting a planned maintenance from 02 November 2026 at 19:00 PST until 02 November 2026 at 20:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to MTS Belarus handsets. We are aware of the short notice and are working with our Carrier Partners to provide earlier notification where possible.

Affected components

2
SMS, EuropeCARRIER NETWORK - SMS, Europe

SendGrid in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

59

Days with an incident

38

Median duration

6 h 53 min

This incident

Not comparable

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

33 days
median 6 h 53 min
90 days agoToday

Other SendGrid incidents

All incidents

SendGrid·SMS Delivery Receipt Delays from a Subset of Twilio Short Codes to Liberty Puerto Rico

SendGrid reports SMS delivery receipt delays from a subset of Twilio Short Codes to Liberty network subscribers in Puerto Rico. This affects SMS, Latin America and the related carrier network. SendGrid has identified the cause and works to resolve the issue.

Degradedupdated 32 min ago

SendGrid·Voice Call One-Way Audio from Brazil to a Subset of Twilio Numbers

On October 31, 2026, from 5AM to 8AM PT, customers may have experienced an issue with some inbound calls to Twilio Brazil numbers having no audio, and some calls also dropping. The impact was linked to a carrier fiber cut and a fallback route that could not handle the traffic load. The issue has been resolved and Voice is operating normally.

Resolvedresolved 2 h ago

SendGrid·Some Customers May Have Incorrect Balances Reflected on Their Account

SendGrid reports incorrect balances on some customer accounts. The issue affects Billing and TWILIO PLATFORM - Billing. SendGrid is investigating the issue.

Degradedupdated 4 h ago

SendGrid·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria

SendGrid reported SMS delivery delays and failures from Twilio Alphanumeric Sender Type to T-Mobile network subscribers in Austria. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reported the incident as resolved. The incident lasted about 5 hours and 13 minutes.

Resolvedresolved 2 h ago

SendGrid·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic

SendGrid reported SMS delivery delays from a subset of Twilio Long Codes to T-Mobile and O2 subscribers in the Czech Republic. The affected components were SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid resolved the incident after 174 minutes.

Resolvedresolved 10 h ago

Follow SendGrid

Your coding agent knows when SendGrid is down, and tells you when a failure is theirs, not yours. You can also get SendGrid 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 "sendgrid" and tell me if SendGrid 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=sendgrid
Slack
/feed subscribe https://outages.live/feed.xml?providers=sendgrid

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane