USA MMS - Planned Maintenance affecting T-Mobile operator
We will be undergoing scheduled maintenance during this time.
The latest update from Vonage API.
State
Scheduled
Starts
Ongoing for
Not started
Worst impact
Maintenance
Updates
Times in UTCAs posted by Vonage API
We will be undergoing scheduled maintenance during this time.
Affected components
2Vonage API in the last 90 days
Full historyIncidents in 90 days
55
Days with an incident
41
Median duration
3 h 23 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage 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 incident affects SMS North America and Global Connectivity - SMS North America. Vonage API resolved the incident. The outage lasted 2 hours and 18 minutes.
Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for GCI Communication network
Vonage reports degraded MMS delivery for Long Codes to GCI Communication network subscribers in the United States. The affected components are MMS North America and Global Connectivity - MMS North America. Vonage is investigating, and the carrier is also investigating the root cause.
Vonage API·Service Issues: Issues impacting WhatsApp Number Onboarding
Vonage API reports that WhatsApp number onboarding through the Embedded Sign-Up flow does not work. This issue affects WhatsApp Connectivity and Global Connectivity in all regions. Vonage has identified the problem and continues to work on a fix. To add a new number to an existing WhatsApp Business Account, contact Vonage support at api.support.vonage.com for manual assistance.
Vonage API·Verify V2 Silent Auth Issue
Vonage API reported that Verify V2 Silent Authentication did not work in some regions. Some customers saw 500 errors during silent authentication requests. Vonage API reported that the issue is resolved after about 4 hours and 30 minutes.
Vonage API·Philippines SMS - Delivery Degradation towards Globe Telecom
Vonage API reported degraded SMS delivery to Globe Telecom in the Philippines. The SMS APAC and Global Connectivity - SMS APAC components were affected. Vonage API reports that the incident is resolved. The outage lasted 44 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