Russia SMS Carrier Maintenance - Tele2
The Tele2 network in Russia is conducting a series of planned maintenances from 02 November 2026 at 12:00 PST until 30 November 2026 at 16:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tele2 Belgium handsets. Note, the maintenance will be carried out on each of the following dates and times: 02 November 2026 at 12:00 PST until 02 November 2026 at 16:00 PST 09 November 2026 at 12:00 PST until 09 November 2026 at 16:00 PST 11 November 2026 at 12:00 PST until 11 November 2026 at 16:00 PST 16 November 2026 at 12:00 PST until 16 November 2026 at 16:00 PST 18 November 2026 at 12:00 PST until 18 November 2026 at 16:00 PST 23 November 2026 at 12:00 PST until 23 November 2026 at 16:00 PST 25 November 2026 at 12:00 PST until 25 November 2026 at 16:00 PST 30 November 2026 at 12:00 PST until 30 November 2026 at 16:00 PST 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 6 h
2026-11-02 20:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by SendGrid
The Tele2 network in Russia is conducting a series of planned maintenances from 02 November 2026 at 12:00 PST until 30 November 2026 at 16:00 PST. During the maintenance window, there could be intermittent delays delivering SMS to Tele2 Belgium handsets. Note, the maintenance will be carried out on each of the following dates and times: 02 November 2026 at 12:00 PST until 02 November 2026 at 16:00 PST 09 November 2026 at 12:00 PST until 09 November 2026 at 16:00 PST 11 November 2026 at 12:00 PST until 11 November 2026 at 16:00 PST 16 November 2026 at 12:00 PST until 16 November 2026 at 16:00 PST 18 November 2026 at 12:00 PST until 18 November 2026 at 16:00 PST 23 November 2026 at 12:00 PST until 23 November 2026 at 16:00 PST 25 November 2026 at 12:00 PST until 25 November 2026 at 16:00 PST 30 November 2026 at 12:00 PST until 30 November 2026 at 16:00 PST 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
55
Days with an incident
38
Median duration
7 h 14 min
This incident
Not comparable
Other SendGrid incidents
All incidentsSendGrid·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 in Indonesia
SendGrid reports a problem with Silent Network Auth and the carrier network for Silent Network Auth in Indonesia. Device verification can time out during API transactions. SendGrid has identified the issue, and API transactions can use SMS OTP as a fallback.
SendGrid·Voice Call Failures from a Subset of Twilio Phone Numbers to Multiple Networks in Philippines
Voice calls fail from a subset of Twilio Philippines Phone Numbers to subscribers on multiple networks in the Philippines. The APAC Voice components are degraded. Twilio has identified the cause and works to resolve the issue.
SendGrid·SMS Delivery Delays from a Subset of Twilio Short Codes to Google Voice United States
SendGrid reports SMS delivery delays from a subset of short codes to Google Voice subscribers in the United States. The affected components are SMS Short Code and CARRIER NETWORK - SMS Short Code in North America. SendGrid resolved the incident after 6 hours and 32 minutes.
SendGrid·SMS Delivery Failures from Twilio to KDDI Japan
SendGrid reports SMS delivery failures from Twilio to KDDI network subscribers in Japan. The affected components are SMS, APAC and CARRIER NETWORK - SMS, APAC. Twilio identified the cause and monitored a recovery. The incident is resolved and lasted 4 hours and 8 minutes.
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