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 SendGrid.
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 SendGrid
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
2SendGrid 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 SendGrid incidents
All incidentsSendGrid·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.
SendGrid·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
SendGrid reports SMS delivery delays and failures for messages from Twilio Alphanumeric Sender Type to T-Mobile subscribers in Austria. The components are SMS, Europe and CARRIER NETWORK - SMS, Europe. SendGrid reports monitoring after a recovery in delivery.
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.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
SendGrid reports that device verification timeouts occur during API transactions for Silent Network Authentication on the XL Axiata network in Indonesia. The affected components are Verify Silent Network Auth and CARRIER NETWORK - Verify Silent Network Auth. SendGrid reports recovery of the API transactions and monitors service stability.
SendGrid·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
Voice calls fail from some SendGrid Philippines phone numbers to subscribers on many networks in the Philippines. The Voice, APAC and carrier network components are degraded. SendGrid identified the cause and continues work to resolve the issue.
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.
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.
https://outages.live/feed.xml?providers=sendgrid/feed subscribe https://outages.live/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane