Indonesia Voice - Degradation towards Indosat network
Please be informed that there was service degradation for calls towards Indosat numbers in Indonesia between October 28 01:34 UTC and 02:30 UTC The carrier has confirmed the full resolution of the issue and calls should be resumed as normal. If you have any questions, please contact api.support.vonage.com
The latest update from Vonage API.
State
Resolved
Started
Lasted
1 min
Worst impact
Notice
Timeline
1 updateResolved
1 min 100%
Updates
Times in UTCAs posted by Vonage API
Please be informed that there was service degradation for calls towards Indosat numbers in Indonesia between October 28 01:34 UTC and 02:30 UTC The carrier has confirmed the full resolution of the issue and calls should be resumed as normal. If you have any questions, please contact api.support.vonage.com
Vonage API in the last 90 days
Full historyIncidents in 90 days
60
Days with an incident
43
Median duration
3 h 26 min
This incident
100% shorter than the median
Other Vonage API incidents
All incidentsVonage API·France SMS - Delivery degradation affecting SMS towards Orange France
SMS delivery to the Orange France network does not work correctly. The affected components are SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved after 103 minutes.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reported degraded SMS delivery to the Orange France network. The issue affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident. It lasted about 2 hours and 34 minutes.
Vonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
Vonage API reports that MMS message delivery was delayed in North America for MMS North America and Global Connectivity - MMS North America. MMS messages to US shortcodes, longcodes, and numbers had delays on multiple networks. Vonage API resolved the incident on 5 November 2026, about 34 hours and 37 minutes after it started.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for AT&T network
Vonage API reported degraded MMS delivery for Long Codes and Short Codes to AT&T subscribers in the United States. The incident affected MMS North America and Global Connectivity - MMS North America. Vonage API resolved the incident. 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 affected components are SMS North America and Global Connectivity - SMS North America. Vonage API reports that the incident is resolved. The outage lasted about 138 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