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 put a fix in place and now monitors the result.
State
Monitoring
Started
Ongoing for
1 h 49 min
Worst impact
Degraded
Timeline
2 updatesInvestigating
33 min 30%
Monitoring
1 h 16 min 70%
Updates
Times in UTCAs posted by Vonage API
A fix has been implemented and we are monitoring the results.
We have been notified by our suppliers about degradation affecting traffic towards Orange France network. The carrier is aware of this issue and investigating the root cause. We 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
58
Days with an incident
42
Median duration
3 h 34 min
This incident
49% shorter than the median
Other Vonage API incidents
All incidentsVonage API·USA MMS - Delivery latency affecting MMS messages affecting multiple networks
Vonage API reports delivery latency for MMS messages in North America. This affects MMS North America and Global Connectivity - MMS North America. Vonage API is investigating the issue and will send an update when more information is available.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for AT&T network
Vonage API reported degraded MMS delivery for Long Codes and Short Codes to AT&T subscribers in the United States. The incident affected MMS North America and Global Connectivity - MMS North America. Vonage API resolved the incident. It lasted about 10 hours and 17 minutes.
Vonage API·USA SMS - Delivery degradation affecting 10DLC traffic towards AT&T operator
Vonage API reports degraded SMS delivery for 10DLC traffic to the AT&T operator in the USA. The affected components are SMS North America and Global Connectivity - SMS North America. Vonage API reports that the incident is resolved. The outage lasted about 138 minutes.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for GCI Communication network
MMS delivery is degraded for Long Codes to GCI Communication network subscribers in the United States. The incident affected MMS North America and Global Connectivity - MMS North America. Vonage reports that the incident is resolved. It lasted about 17 hours and 51 minutes.
Vonage API·Service Issues: Issues impacting WhatsApp Number Onboarding
WhatsApp number onboarding through the Embedded Sign-Up flow did not work. The issue affected Whatsapp Connectivity and Global Connectivity - Whatsapp Connectivity. Vonage reports that the incident is resolved. Vonage confirmed full resolution on 2026-11-03 at 21:30 UTC.
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