Japan Voice - Planned maintenance impacting multiple networks
Between 14:00 and 15:00 (UTC) on the 12-November-2026, a planned maintenance will be performed affecting voice calls towards multiple networks. During the maintenance window, you may experience failed calls to Japan multiple networks. We apologise in advance for any inconvenience this may cause. 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 14:00 and 15:00 (UTC) on the 12-November-2026, a planned maintenance will be performed affecting voice calls towards multiple networks. During the maintenance window, you may experience failed calls to Japan multiple networks. We apologise in advance for any inconvenience this may cause. 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
77
Days with an incident
49
Median duration
3 h 24 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Issue with Spain Movistar RCS Delivery
RCS delivery to Spain Movistar does not work. The problem affects RCS Connectivity and Global Connectivity - RCS Connectivity. Vonage API reports that it is investigating the issue.
Vonage API·Issue with WhatsApp onboarding
Vonage API reports that WhatsApp onboarding does not work for WhatsApp Connectivity and Global Connectivity - Whatsapp Connectivity. Vonage reports that a third party provider identified the issue and put a fix in place. Vonage continues to monitor the situation.
Vonage API·Service issue in Voice platform
Vonage reports a service issue that affects the Voice API and SIP Trunking, and PSTN/SIP connectivity in the APAC region. Vonage states that the issue is resolved. Vonage gives the start time as 2026-11-10 09:47 UTC and the resolution time as 2026-11-10 10:11 UTC.
Vonage API·France SMS - Delivery Degradation towards Bouygues Telecom
Vonage API reported degraded SMS delivery toward Bouygues Telecom in France. The incident affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident after 79 minutes.
Vonage API·France Silent Authentication - Service degradation affecting Bouygues Telecom networks
Vonage API reports degraded Silent Authentication on Bouygues Telecom networks in France. The affected components are Verify SilentAuth Europe and Global Connectivity - Verify SilentAuth Europe. Vonage API states that the incident is resolved, and it lasted 142 minutes.
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