Japan SMS - Planned Maintenance affecting SoftBank
Between 05-Nov-2026 15:00 UTC and 05-Nov-2026 17:00 UTC, the operator SoftBank will perform maintenance on its SMS platform. During this maintenance period, there may be Inbound and Outbound SMS delays to subscribers of this operator. 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-Nov-2026 15:00 UTC and 05-Nov-2026 17:00 UTC, the operator SoftBank will perform maintenance on its SMS platform. During this maintenance period, there may be Inbound and Outbound SMS delays to subscribers of this operator. 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
59
Days with an incident
43
Median duration
3 h 43 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reports a delivery degradation for SMS towards the Orange France network. This affects SMS Europe and Global Connectivity - SMS Europe. Vonage API is investigating the problem.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reports degraded SMS delivery to the Orange France network. The affected components are SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident on 4 November 2026, about 154 minutes after it started.
Vonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
Vonage reports delayed MMS message delivery in the USA on multiple networks. The affected components are MMS North America and Global Connectivity - MMS North America. Vonage resolved the incident on 5 November 2026, and it lasted about 34 hours and 37 minutes.
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.
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