Vonage API
Vonage API is reporting degraded
Partially Degraded Service
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.
France SMS - Delivery degradation affecting a subset of LVNs towards France networks
SMS delivery to France is degraded for a subset of LVNs. This affects the SMS Europe and Global Connectivity SMS Europe components. Vonage API identified the root cause and works with suppliers and carriers to resolve the problem.
USA MMS - Delivery degradation affecting MMS traffic towards C-Spire operator
Vonage API reports a delivery degradation for MMS traffic to the C-Spire operator in the USA. This affects MMS North America and Global Connectivity MMS North America. Vonage API put a fix in place and now monitors the result.
History
Incidents in 90 days
49
Days with an incident
39
Median duration
3 h 22 min
Longest incident
35 days
Components
120Video
Oct 29, 2026
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.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 27, 2026
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 25, 2026
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 22, 2026
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 21, 2026
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
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 Sweden Long Virtual Numbers (LVNs). While we work toward a permanent resolution for Sweden, 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.vonageapi.statuspage.io
Vonage services have been fully restored following today's service interruption on Outbound SMS in the APAC region, which began at [2026-10-21 10:15:00] UTC. Full resolution has been confirmed effective at [2026-10-21 10:34:00] 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 https://www.vonage.com/support/vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 20, 2026
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
This incident has been resolved.vonageapi.statuspage.io
Oct 19, 2026
This incident has been resolved.vonageapi.statuspage.io
Vonage services have been fully restored following today’s service interruption in Voice traffic, which began at 2026-10-19 15:11 UTC. Full resolution has been confirmed effective 2026-10-19 16:11 UTC. Impacted customers will receive a formal RFO. 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.vonageapi.statuspage.io
Vonage services have been fully restored following today's Verify V2 service interruption reported by our third party, which began at 2026-10-19 09:00 UTC. Full resolution of the incident has been confirmed effective 2026-10-19 09:20 UTC. Impacted customers will receive a formal RFO. 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.vonageapi.statuspage.io
Oct 16, 2026
This incident has been resolved.vonageapi.statuspage.io
Vonage services have been fully restored following a service degradation affecting your ability to create payments via the Vonage Customer Dashboard, which occurred between 2026-10-16 12:28:00 AM UTC and 2026-10-16 6:03:05 AM UTC. This issue is no longer active and full service has been confirmed restored. Thank you for your patience and understanding. If you have any questions, please contact api.support.vonage.com.vonageapi.statuspage.io
Maintenance
Philippines SMS - Planned maintenance affecting Globe Telecom
We have been notified by our partners that between 19:00 (UTC) and 21:00 (UTC) on 29-November-2026, a planned maintenance will be performed affecting Philippines Globe Telecom network. During the maintenance window, you may experience delivery degradation towards the Globe subscribers. If you have any questions, please contact api.support.vonage.com
USA/Canada SMS and MMS - Planned Maintenance affecting SMS & MMS messages
Between 2026-11-24 04:00 UTC and 08:00 UTC, supplier will be performing maintenance towards United States and Canada. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of long codes. If you have any questions, please contact api.support.vonage.com
Philippines SMS - Planned maintenance affecting Globe Telecom
We have been notified by our partners that between 19:00 (UTC) and 21:00 (UTC) on 22-November-2026, a planned maintenance will be performed affecting Philippines Globe Telecom network. During the maintenance window, you may experience delivery degradation towards the Globe subscribers. If you have any questions, please contact api.support.vonage.com
USA & Canada SMS and MMS - Planned Maintenance affecting 10DLC traffic
Between 19th November 2026, 05:00 UTC and 11:00 UTC, Operator will be performing maintenance towards the United States and Canada. During the maintenance window, Clients may experience delayed or failed 10DLC MT/MO traffic towards the United States and Canada. If you have any questions, please contact api.support.vonage.com
USA/Canada SMS and MMS - Planned Maintenance affecting SMS & MMS messages
Between 2026-11-19 04:00 UTC and 08:00 UTC, supplier will be performing maintenance towards United States and Canada. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of long codes. If you have any questions, please contact api.support.vonage.com
Affected components
2- SMS EuropeGlobal ConnectivityDegraded
- SMS APACGlobal ConnectivityMaintenance
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=vonageGo from tracking outages to fixing production issues with Polylane.
Try Polylane