Russia SMS - Planned maintenance affecting Motive Network
Between 05 Nov 2026 at 18:00 and 06 Nov 2026 at 00:00 (UTC), the supplier will be performing maintenance on their platform affecting SMS towards Motive network in Russia. During the maintenance window, you may experience SMS Inbound and Outbound degradation and delays to subscribers of this operator. Please contact api.support.vonage.com if you have any questions.
The latest update from Vonage API.
State
Scheduled
Starts
in 3 d
2026-11-05 18:00 UTC
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vonage API
Between 05 Nov 2026 at 18:00 and 06 Nov 2026 at 00:00 (UTC), the supplier will be performing maintenance on their platform affecting SMS towards Motive network in Russia. During the maintenance window, you may experience SMS Inbound and Outbound degradation and delays to subscribers of this 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
52
Days with an incident
40
Median duration
3 h 22 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Verify V2 Silent Auth Issue
Vonage API reports that Verify V2 Silent Authentication does not work for some customers. The Auth & Identity - Verify V2 components are affected. Vonage is investigating the issue.
Vonage API·Philippines SMS - Delivery Degradation towards Globe Telecom
Vonage API reported degraded SMS delivery to Globe Telecom in the Philippines. The incident affected SMS APAC and Global Connectivity - SMS APAC. Vonage API reported that the incident is resolved after 44 minutes.
Vonage API·France Silent Authentication - Service degradation affecting the Orange France, SFR & Bouygues Telecom networks
Vonage reports degraded Silent Authentication on the Orange France, SFR, and Bouygues Telecom networks. This affects Verify SilentAuth Europe and Global Connectivity - Verify SilentAuth Europe. Vonage put a fix in place and now monitors the result.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
SMS delivery to the Orange France network does not work correctly. The problem affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted about 17 hours.
Vonage API·Netherlands Silent Authentication - Service degradation affecting KPN network
This incident has been 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.
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.
https://outages.live/feed.xml?providers=vonage/feed subscribe https://outages.live/feed.xml?providers=vonageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane