Russia SMS - Planned maintenance affecting Gazprombank
Between 05-November-2026 20:00 PM to 21:00 PM UTC, Operator Gazprombank will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards Gazprombank 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 UTCAs posted by Vonage API
Between 05-November-2026 20:00 PM to 21:00 PM UTC, Operator Gazprombank will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards Gazprombank Russian subscribers. If you have any questions, please contact api.support.vonage.com
Affected components
2Vonage API in the last 90 days
Full historyIncidents in 90 days
57
Days with an incident
42
Median duration
3 h 34 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
MMS delivery is degraded for MMS North America and Global Connectivity - MMS North America. Vonage API reports that delayed MMS messages can occur for US shortcodes, longcodes, and numbers. The supplier of Vonage API knows about the issue and is investigating the root cause.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for AT&T network
Vonage API reported degraded MMS delivery for AT&T network subscribers in the United States. The incident affected MMS North America and Global Connectivity - MMS North America. Vonage API reports that the incident is resolved. It lasted about 10 hours and 17 minutes.
Vonage API·USA SMS - Delivery degradation affecting 10DLC traffic towards AT&T operator
Vonage API reports degraded SMS delivery for 10DLC traffic to the AT&T operator in the USA. The incident affects SMS North America and Global Connectivity - SMS North America. Vonage API resolved the incident. The outage lasted 2 hours and 18 minutes.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for GCI Communication network
Vonage API reports MMS delivery degradation for Long Codes to GCI Communication network subscribers in the United States. The incident affected MMS North America and Global Connectivity MMS North America. Vonage API reports that the incident is resolved. It lasted about 17 hours and 51 minutes.
Vonage API·Service Issues: Issues impacting WhatsApp Number Onboarding
WhatsApp number onboarding through the Embedded Sign-Up flow did not work. The issue affected WhatsApp Connectivity and Global Connectivity - WhatsApp Connectivity. Vonage reports that the issue is resolved. The outage lasted from 2026-11-02 10:30 UTC to 2026-11-03 21:30 UTC.
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.
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 "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.
https://outages.cc/feed.xml?providers=vonage/feed subscribe https://outages.cc/feed.xml?providers=vonageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane