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 for Verify SilentAuth Europe. Vonage is investigating with its carrier partners.
State
Investigating
Started
Ongoing for
50 min
Worst impact
Degraded
Timeline
1 updateInvestigating
50 min 100%
Updates
Times in UTCAs posted by Vonage API
We are currently experiencing degradation of the Silent Authentication service, which is affecting Bouygues Telecom Networks. 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
73
Days with an incident
48
Median duration
3 h 26 min
This incident
76% shorter than the median
Other Vonage API incidents
All incidentsVonage 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.
Vonage API·Indonesia SMS - Delivery Degradation of Domestic Brands towards network PT XL Axiata Tbk and Smartfren
Vonage API reports SMS delivery degradation for Indonesia domestic brands to the PT XL Axiata Tbk and Smartfren networks. The affected components are SMS APAC and Global Connectivity - SMS APAC. Vonage API states that the incident is resolved and that it lasted 158 minutes.
Vonage API·France SMS - Delivery Degradation towards Bouygues Telecom
SMS delivery to France Bouygues Telecom does not work. The problem affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted 11 hours and 52 minutes.
Vonage API·Philippines SMS - Delivery Degradation towards Globe Telecom
Vonage API reports degraded SMS delivery to Globe Telecom in the Philippines. The SMS APAC and Global Connectivity - SMS APAC components are affected. Vonage API resolved the incident, which lasted about 14 hours and 41 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