Live

Malaysia SMS - Planned maintenance affecting SMS for XOX

MaintenanceOfficial update

On 24-Nov-2026 between 05:00 UTC and 07:00 UTC, the operator XOX will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards XOX Malaysia subscribers. 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 UTC

As posted by Vonage API

Scheduled

On 24-Nov-2026 between 05:00 UTC and 07:00 UTC, the operator XOX will be performing maintenance on their SMS platform. During this maintenance period, there may be potential delay in SMS delivery from and towards XOX Malaysia subscribers. 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

89

Days with an incident

57

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·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

Vonage API·France SMS - Delivery Degradation towards Lebara France

SMS delivery to Lebara France is degraded. This affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved and that it lasted 150 minutes.

Resolved

Vonage API·Canada SMS - Delivery Degradation towards Bell Canada

SMS delivery to Bell Canada is degraded for SMS North America and Global Connectivity - SMS North America. Vonage reports that the incident is resolved. It lasted 55 minutes.

Resolved

Vonage API·Japan SMS - Delivery degradation affecting KDDI Network

Vonage API reported degraded SMS delivery on the KDDI network in Japan, which affected SMS APAC and Global Connectivity - SMS APAC. Vonage API later reported that the incident was resolved. The degradation lasted 99 minutes.

Resolved

Vonage API·Nigeria SMS - Delivery Degradation towards MTN network

Vonage API reported degraded SMS delivery to the MTN network in Nigeria. The affected components were SMS Middle East & Africa and Global Connectivity - SMS Middle East & Africa. Vonage API resolved the incident after about 139 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