USA SMS and MMS - Planned Maintenance affecting T-Mobile operator
Between 2026-11-16 04:30 UTC to 2026-11-16 08:30 UTC, supplier will be performing maintenance towards T-Mobile. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS towards T-Mobile operator for Short Codes and 10dlc. 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-11-16 04:30 UTC to 2026-11-16 08:30 UTC, supplier will be performing maintenance towards T-Mobile. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS towards T-Mobile operator for Short Codes and 10dlc. 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
84
Days with an incident
52
Median duration
3 h 43 min
This incident
Not comparable
Other Vonage API incidents
All incidentsVonage API·France SMS - Delivery Degradation towards Lebara France
On 2026-11-13, Vonage API reported degraded SMS delivery to the Lebara France network. This affected SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved. The degradation lasted about 5 hours and 44 minutes.
Vonage API·Issues Impacting WhatsApp API
Vonage Messages API had problems with the WhatsApp channel. Inbound WhatsApp messages and webhooks did not work. Delivery callbacks for the WhatsApp channel did not arrive. Outbound messaging was not affected. The incident is resolved. Vonage reported full recovery at 2026-11-13 22:00:00 UTC. The incident began at 2026-11-13 18:31:00 UTC and lasted about 3 hours and 29 minutes.
Vonage API·Vonage API Help Center - Ticket Email Degradation
Email support for the Vonage API Help Center did not work. The affected components were Email Support and Vonage API Support Platforms. Vonage reported the incident as resolved. The outage lasted about 11 hours and 47 minutes.
Vonage API·France SMS - Delivery Degradation towards Lebara France
Vonage API reports degraded SMS delivery to the Lebara France network. The problem affects SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident. The outage lasted about 9 hours and 40 minutes.
Vonage API·France SMS - Delivery Degradation towards Lebara France
Vonage API reported degraded SMS delivery to the Lebara France network. The incident affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident after 2 hours and 35 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