Malaysia SMS - Planned maintenance affecting SMS for CelcomDigi
ResolvedOfficial update
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from Vonage API.
State
Resolved
Started
10 h ago
2026-11-01 16:00 UTC
Lasted
6 h 3 min
until 2026-11-01 22:03 UTC
Worst impact
Maintenance
Timeline
2 updates16:0017:3019:0120:3222:03
MaintenanceUpdate postedTimes in UTC
In progress
6 h 3 min 100%
Updates
Times in UTCAs posted by Vonage API
Resolved2026-11-01 22:03 UTC
In progress2026-11-01 17:18 UTC
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Affected components
2SMS APACGlobal Connectivity - SMS APAC
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.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.
RSS
https://outages.cc/feed.xml?providers=vonageSlack
/feed subscribe https://outages.cc/feed.xml?providers=vonageFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane