Voice API - Service Degradation
Vonage services have been fully restored following today’s service interruption, which began at 2026-10-12 21:51:24 UTC. Full resolution has been confirmed effective 2026-10-13 14:28 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
The latest update from Vonage API.
State
Resolved
Started
20 d ago
2026-10-13 01:26 UTC
Lasted
14 h 17 min
until 2026-10-13 15:43 UTC
Worst impact
Degraded
Timeline
4 updatesInvestigating
35 min 4%
Identified
13 h 42 min 96%
Updates
Times in UTCAs posted by Vonage API
Vonage services have been fully restored following today’s service interruption, which began at 2026-10-12 21:51:24 UTC. Full resolution has been confirmed effective 2026-10-13 14:28 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.
We have identified the issue with no ongoing impact. We will continue to provide further updates within 24 hours and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
We have identified the issue that may be impacting your Voice API - TTS (Text-to-speech) service and is seeing early signs of recovery with no ongoing impact. We will continue to provide further updates within 2 hours and once full service is restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.
We are aware of issues that may be impacting your Voice API traffic. We are working to resolve the issue as soon as possible. We’ll provide further updates within 2 hours. Thank you for your patience and understanding. If you have any questions, please contact support@api.vonage.com.
Affected components
4Vonage API in the last 90 days
Full historyIncidents in 90 days
49
Days with an incident
39
Median duration
3 h 22 min
This incident
4.3× the median
Other Vonage API incidents
All incidentsVonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reports SMS delivery degradation in France. The problem affects SMS Europe and Global Connectivity - SMS Europe. Traffic toward the Orange France network is degraded. Vonage API is investigating.
Vonage API·Netherlands Silent Authentication - Service degradation affecting KPN network
This incident has been resolved.
Vonage API·Norway Voice - Degradation towards all network affecting Long Virtual Numbers
We have worked with our carrier partner to identify workaround measures for the degradation impacting voice calls towards all networks affecting a subset of Vonage Norway Long Virtual Numbers (LVNs). While we work toward a permanent resolution for Norway, a workaround is available right now: simply use an alternative international number when placing calls to these destinations. We encourage all impacted customers to implement this as soon as possible. If you have any questions or require further assistance, please do not hesitate to contact https://api.support.vonage.com. We apologize for any inconvenience caused and thank you for your patience and understanding throughout this incident.
Vonage API·USA SMS/MMS - Delivery degradation affecting SMS and MMS traffic towards AT&T operator
This incident has been resolved.
Vonage API·Ghana SMS - Delivery degradation towards MTN network
This incident has been 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.
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