Live

Japan SMS - Planned Maintenance affecting NTT Japan

MaintenanceOfficial update

We will be undergoing scheduled maintenance during this time.

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

We will be undergoing scheduled maintenance during this time.

Scheduled

On 02nd Dec 2026 between 14:00 UTC and 15:00 UTC, the operator NTT Japan will be performing a maintenance on their SMS platform. During this time, SMS delivery to and from NTT Docomo subscribers may occasionally experience a delay. If you have any questions, please contact api.support.vonage.com

Affected components

2
SMS APACGlobal Connectivity - SMS APAC

Vonage API in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

93

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 and affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that a fix is in place and the state is monitoring.

Degraded

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

SMS delivery is degraded on the NTT DoCoMo network in Japan and affects SMS APAC and Global Connectivity - SMS APAC. Vonage API implemented a fix and is monitoring the results.

Degraded

Vonage API·China SMS - Delivery degradation affecting multiple networks

Vonage API reports degraded SMS delivery to China across China Mobile, China Unicom and China Telecom. The affected components are SMS APAC and Global Connectivity - SMS APAC. Vonage reports the status as investigating and is working with carrier partners.

Degraded

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

Vonage API·Denmark SMS - Delivery receipt degradation affecting Hi3G Denmark

Delivery receipts do not work correctly for SMS messages to Hi3G Denmark on the SMS Europe and Global Connectivity - SMS Europe components. Vonage API reports that the incident is resolved. It lasted about 2 hours and 14 minutes.

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