Russia SMS - Planned maintenance affecting MTT
Between 02 November 2026 20:55 UTC and 02 November 2026 22:00 UTC, the operator MTT will be performing maintenance on their SMS platform. During this maintenance period, there may be difficulties in delivering messages to and from the subscribers of this MTT operator. Please contact api.support.vonage.com if you have any questions.
The latest update from Vonage API.
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 Vonage API
Between 02 November 2026 20:55 UTC and 02 November 2026 22:00 UTC, the operator MTT will be performing maintenance on their SMS platform. During this maintenance period, there may be difficulties in delivering messages to and from the subscribers of this MTT operator. Please contact api.support.vonage.com if you have any questions.
Affected components
2Vonage API in the last 90 days
Full historyIncidents in 90 days
53
Days with an incident
40
Median duration
3 h 24 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Service Issues: Issues impacting WhatsApp Number Onboarding
WhatsApp number onboarding through the Embedded Sign-Up flow does not work. This affects WhatsApp Connectivity and Global Connectivity - WhatsApp Connectivity. Vonage API reports that the cause is identified and a fix is in progress. To add a new number to an existing WhatsApp Business Account, contact api.support.vonage.com for manual assistance.
Vonage API·Verify V2 Silent Auth Issue
Vonage API reported that Verify V2 Silent Authentication did not work in some regions. Some customers saw 500 errors during silent authentication requests. Vonage API reported that the issue is resolved after about 4 hours and 30 minutes.
Vonage API·Philippines SMS - Delivery Degradation towards Globe Telecom
Vonage API reported degraded SMS delivery to Globe Telecom in the Philippines. The SMS APAC and Global Connectivity - SMS APAC components were affected. Vonage API reports that the incident is resolved. The outage lasted 44 minutes.
Vonage API·France Silent Authentication - Service degradation affecting the Orange France, SFR & Bouygues Telecom networks
Silent Authentication does not work for Vonage API customers on the Orange France, SFR, and Bouygues Telecom networks. This incident affected Verify SilentAuth Europe and Global Connectivity - Verify SilentAuth Europe. Vonage API reports that the incident is resolved, and it lasted about 6 hours and 47 minutes.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
SMS delivery to the Orange France network does not work. The problem affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted about 17 hours.
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