Live

Russian SMS - Planned maintenance affecting Sber operator

MaintenanceOfficial update

Between 21-Nov-2026 20:00 to 23:00 UTC, Operator Sber will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards Sber Russian subscribers. If you have any questions, please contact api.support.vonage.com

The latest update from Vonage API.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Vonage API

Scheduled

Between 21-Nov-2026 20:00 to 23:00 UTC, Operator Sber will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards Sber Russian subscribers. If you have any questions, please contact api.support.vonage.com

Affected components

2
SMS EuropeGlobal Connectivity - SMS Europe

Vonage API in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

94

Days with an incident

58

Median duration

3 h 26 min

This incident

Not comparable

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

35 days
median 3 h 26 min
90 days agoToday

Other Vonage API incidents

All incidents

Vonage API·Belgium SMS - Delivery degradation towards Proximus network

SMS delivery to the Proximus network in Belgium is degraded. This affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that a fix is in place and the result is under monitoring.

Degraded

Vonage API·Belgium SMS - Delivery degradation towards Proximus network

SMS delivery is degraded for outbound messages to the Proximus network in Belgium. The issue affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. It lasted 2 hours and 25 minutes.

Resolved

Vonage API·Japan SMS - Delivery degradation affecting NTT DoCoMo Network

SMS delivery to the NTT DoCoMo network in Japan is degraded and affects SMS APAC and Global Connectivity - SMS APAC. Vonage API reports that the incident is resolved. The incident lasted 122 minutes.

Resolved

Vonage API·China SMS - Delivery degradation affecting multiple networks

SMS delivery to China is degraded on multiple networks and affects SMS APAC and Global Connectivity - SMS APAC. Vonage API reports that the incident is resolved. It lasted 4 hours and 30 minutes.

Resolved

Vonage API·Germany Silent Authentication - Service degradation affecting Vodafone GmbH

Vonage API reports degraded Silent Authentication service for Vodafone GmbH in Germany, affecting Verify SilentAuth APAC and Global Connectivity - Verify SilentAuth APAC. The incident is resolved and lasted about 7 hours.

Resolved

Follow Vonage API

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane