Planned Maintenance — API Platform
We will be performing two scheduled maintenance windows as part of planned infrastructure maintenance. During these windows, the following services may be temporarily affected: Fraud Defender (traffic rules, burst protection, account takedown, custom fraud alerts, alert manager, DNO checker) SMS / Messages API (messaging settings, messaging opt-out, adaptive traffic control, MT routing, email channel) Notification Service (notification subscriptions) Vonage Network APIs / VNA (routing configuration, Identity Insights allowlists, feature flags) Window 1 - Mon 16 Nov 2026, 05:00-05:30 UTC A brief disruption of approximately 15 seconds is expected. Any attempts to update settings for the above services during this window may fail. Window 2 - Mon 23 Nov 2026, 05:00-05:30 UTC A disruption of approximately 1 minute is expected. Any attempts to update settings for the above services during this window may fail. You may also experience brief errors when reading your current settings. Normal se
The latest update from Vonage API.
State
Resolved
Starts
Lasted
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vonage API
We will be performing two scheduled maintenance windows as part of planned infrastructure maintenance. During these windows, the following services may be temporarily affected: Fraud Defender (traffic rules, burst protection, account takedown, custom fraud alerts, alert manager, DNO checker) SMS / Messages API (messaging settings, messaging opt-out, adaptive traffic control, MT routing, email channel) Notification Service (notification subscriptions) Vonage Network APIs / VNA (routing configuration, Identity Insights allowlists, feature flags) Window 1 - Mon 16 Nov 2026, 05:00-05:30 UTC A brief disruption of approximately 15 seconds is expected. Any attempts to update settings for the above services during this window may fail. Window 2 - Mon 23 Nov 2026, 05:00-05:30 UTC A disruption of approximately 1 minute is expected. Any attempts to update settings for the above services during this window may fail. You may also experience brief errors when reading your current settings. Normal se
Affected components
18Vonage API in the last 90 days
Full historyIncidents in 90 days
70
Days with an incident
48
Median duration
3 h 53 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Indonesia SMS - Delivery Degradation of Domestic Brands towards network PT XL Axiata Tbk and Smartfren
Vonage API reports SMS delivery problems for domestic brands to the Indonesia networks PT XL Axiata Tbk and Smartfren. The affected components are SMS APAC and Global Connectivity - SMS APAC. Vonage API is investigating the issue with its carrier partners.
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.
Vonage API·DE and CR SMS - Delivery degradation affecting a subset of LVNs towards Germany and Costa Rica networks
SMS delivery is degraded for some LVNs to Germany and Costa Rica networks. This affects SMS Europe, SMS Latin America, and their Global Connectivity components. Vonage reports that the incident is resolved. It lasted about 23 hours.
Vonage API·USA SMS- Delivery degradation affecting SMS 10DLC/SC traffic towards multiple operators
Vonage API reports delivery degradation for SMS 10DLC and Short Code traffic from and towards USA networks. This affects SMS North America and Global Connectivity - SMS North America. Vonage API resolved the incident after 25 hours and 30 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