United Kingdom Silent Authentication - Planned maintenance affecting Vodafone UK
To ensure platform stability, our upstream partner will conduct maintenance on 10-11-2026 starting at 23:15 UTC until 12-11-2026 at 03:45 UTC. During this window, users may experience intermittent latency for Silent Authentication requests on the Vodafone network. If you have any questions, please contact api.support.vonage.com
The latest update from Vonage API.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vonage API
To ensure platform stability, our upstream partner will conduct maintenance on 10-11-2026 starting at 23:15 UTC until 12-11-2026 at 03:45 UTC. During this window, users may experience intermittent latency for Silent Authentication requests on the Vodafone network. 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
75
Days with an incident
48
Median duration
3 h 23 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Service issue in Voice platform
Vonage Voice API and SIP Trunking have degraded service in the APAC region. PSTN and SIP connectivity may be affected. Vonage reports that services show signs of recovery and that monitoring continues. The issue started 64 minutes ago and is not resolved.
Vonage API·France SMS - Delivery Degradation towards Bouygues Telecom
Vonage API reported degraded SMS delivery toward Bouygues Telecom in France. The incident affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident after 79 minutes.
Vonage API·France Silent Authentication - Service degradation affecting Bouygues Telecom networks
Vonage API reports degraded Silent Authentication on Bouygues Telecom networks in France. The affected components are Verify SilentAuth Europe and Global Connectivity - Verify SilentAuth Europe. Vonage API states that the incident is resolved, and it lasted 142 minutes.
Vonage API·Israel SMS - Delivery degradation affecting domestic traffic for Partner, Cellcom & Pelephone networks
Vonage API reported degraded SMS delivery for domestic traffic to the Partner, Cellcom and Pelephone networks in Israel, which affected SMS Middle East & Africa and Global Connectivity - SMS Middle East & Africa. Vonage API implemented a fix and monitored the results. The incident is resolved and lasted 108 minutes.
Vonage API·Indonesia SMS - Delivery degradation affecting XLSmart
Vonage API reported degraded SMS delivery to XLSmart in Indonesia. The problem affected SMS APAC and Global Connectivity - SMS APAC. Vonage API reports that the issue is resolved after 12 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