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 1 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 customer accounts. The problem affects Billing and TWILIO PLATFORM - Billing. SendGrid is investigating the problem.
SendGrid·SMS Delivery Delays and Failures from Twilio Alphanumeric Sender Type to T-Mobile Austria
SendGrid reports SMS delivery delays and failures from the Twilio Alphanumeric Sender Type to T-Mobile subscribers in Austria. The SMS Europe components are degraded. SendGrid sees a recovery and monitors service stability. The incident started 193 minutes ago.
SendGrid·SMS Delivery Delays from a Subset of Twilio Long Codes to T-Mobile and O2 Czech Republic
SendGrid reports SMS delivery delays from a subset of Twilio Long Codes to T-Mobile and O2 Czech Republic subscribers. The incident is resolved. It lasted about 2 hours and 54 minutes.
SendGrid·Silent Network Authentication (SNA) Missing Redirects on XL Axiata in Indonesia
SendGrid reports that Silent Network Authentication (SNA) does not work on the XL Axiata network in Indonesia. Device verification during API transactions can time out on Verify Silent Network Auth. SendGrid reports the state as monitoring.
SendGrid·Voice Call Failures From a Subset of Twilio Philippines Phone Numbers to Multiple Networks in Philippines
SendGrid reports voice call failures from a subset of Twilio Philippines phone numbers. The calls do not connect to subscribers on many networks in the Philippines. The Voice, APAC and CARRIER NETWORK - Voice, APAC components are degraded. Twilio identified the cause and works 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.cc/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.cc/feed.xml?providers=sendgrid/feed subscribe https://outages.cc/feed.xml?providers=sendgridFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane