UK SMS - Delivery degradation of SMS traffic towards O2 UK Network
SMS delivery to the O2 UK network is degraded. The affected components are SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted 6 hours and 3 minutes.
State
Resolved
Started
Lasted
6 h 3 min
Worst impact
Degraded
Timeline
4 updatesInvestigating
5 h 30 min 91%
Monitoring
33 min 9%
Updates
Times in UTCAs posted by Vonage API
A fix has been implemented and we are monitoring the results.
We are continuing to work with our carrier partners to resolve the issue. Please note that delivery is unaffected. Missing delivery reports.
Please be advised that we are observing SMS delivery degradation towards O2 UK Network. We are working with our carrier partners to resolve the issue and will issue an update as soon as more information becomes available. 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
62
Days with an incident
44
Median duration
3 h 26 min
This incident
1.8× the median
Other Vonage API incidents
All incidentsVonage API·Vonage Video Degradation
Vonage services have been fully restored following a service interruption to the Vonage Video API (US East), which began at 2026-11-02 17:09 UTC. Full resolution has been confirmed effective at 2026-11-02 17:50 UTC. If you have any questions, please contact api.support.vonage.com.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reported degraded SMS delivery to the Orange France network. The problem affected SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted 1 hour and 43 minutes.
Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France
Vonage API reports degraded SMS delivery to the Orange France network. The affected components are SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident on 4 November 2026, about 154 minutes after it started.
Vonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
Vonage reports delayed MMS message delivery in the USA on multiple networks. The affected components are MMS North America and Global Connectivity - MMS North America. Vonage resolved the incident on 5 November 2026, and it lasted about 34 hours and 37 minutes.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for AT&T network
Vonage API reported degraded MMS delivery for AT&T network subscribers in the United States. The incident affected MMS North America and Global Connectivity - MMS North America. Vonage API reports that the incident is resolved. It lasted about 10 hours and 17 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.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