Verify V2 Silent Auth Issue
Vonage API reports that Verify V2 Silent Authentication does not work for some customers. The Auth & Identity - Verify V2 components are affected. Vonage is investigating the issue.
State
Investigating
Started
2 h ago
2026-11-02 11:03 UTC
Ongoing for
1 h 45 min
Worst impact
Degraded
Timeline
1 updateInvestigating
1 h 45 min 100%
Updates
Times in UTCAs posted by Vonage API
We are aware of issues that may be impacting some Vonage customers' Verify V2 Silent Authentication service due to a third party interruption. We’ll provide further updates within 2 hours 30 minutes. Thank you for your patience and understanding. Incident Start Time: 11/2/2026 08:30 UTC If you have any questions, please contact api.support.vonage.com
Affected components
2Vonage API in the last 90 days
Full historyIncidents in 90 days
52
Days with an incident
40
Median duration
3 h 23 min
This incident
48% shorter than the median
Other Vonage API incidents
All incidentsVonage API·Philippines SMS - Delivery Degradation towards Globe Telecom
Vonage API reported degraded SMS delivery to Globe Telecom in the Philippines. The incident affected SMS APAC and Global Connectivity - SMS APAC. Vonage API reported that the incident is resolved after 44 minutes.
Vonage API·France Silent Authentication - Service degradation affecting the Orange France, SFR & Bouygues Telecom networks
Vonage API reports degraded Silent Authentication on the Verify SilentAuth Europe and Global Connectivity components. The degradation affects the Orange France, SFR and Bouygues Telecom networks. Vonage API resolved the incident. The incident lasted 6 hours and 47 minutes.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
SMS delivery to the Orange France network does not work correctly. The problem affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted about 17 hours.
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.
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