USA/Canada SMS and MMS - Planned Maintenance affecting SMS & MMS messages
Between 2026-12-17 04:00 UTC and 08:00 UTC, supplier will be performing maintenance towards United States and Canada. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of short and long codes. 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
Between 2026-12-17 04:00 UTC and 08:00 UTC, supplier will be performing maintenance towards United States and Canada. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to United States and Canada handsets when sending via subset of short and long codes. If you have any questions, please contact api.support.vonage.com
Affected components
4Vonage API in the last 90 days
Full historyIncidents in 90 days
65
Days with an incident
44
Median duration
3 h 24 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·Dominican Republic SMS - Delivery Degradation towards Claro network
Vonage API reports SMS delivery degradation for the Claro network in the Dominican Republic. The affected components are SMS Latin America and Global Connectivity - SMS Latin America. Vonage API resolved the incident after 114 minutes.
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 states that the incident is resolved. The outage lasted 2 hours and 6 minutes.
Vonage API·Czech Republic SMS - Delivery Degradation towards T-Mobile Network
Vonage API reported degraded SMS delivery to the T-Mobile network in the Czech Republic. The affected components were SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident. The degradation lasted about 4 hours and 3 minutes.
Vonage 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·UK SMS - Delivery degradation of SMS traffic towards O2 UK Network
SMS delivery towards the O2 UK network does not work correctly. The issue affects SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The incident lasted about 6 hours.
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