Live

USA MMS - Delivery latency affecting MMS messages affecting multiple networks

0

MMS delivery is degraded for MMS North America and Global Connectivity - MMS North America. Vonage API reports that delayed MMS messages can occur for US shortcodes, longcodes, and numbers. The supplier of Vonage API knows about the issue and is investigating the root cause.

State

Investigating

Started

Ongoing for

1 h 11 min

Worst impact

Degraded

Timeline

1 update
17:2417:4117:5918:1718:35
DegradedUpdate postedTimes in UTC

Investigating

1 h 11 min 100%

Updates

Times in UTC

As posted by Vonage API

Investigating

We have been notified by our US supplier about an issue impacting delivery for MMS messages towards multiple network operators. You might experience delayed MMS messages for US Shortcodes, Longcodes, numbers. The supplier is aware of this issue and investigating the root cause. We will issue an update as soon as more information becomes available. If you have any questions, please contact api.support.vonage.com

Affected components

2
MMS North AmericaGlobal Connectivity - MMS North America

Vonage API in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

57

Days with an incident

41

Median duration

3 h 23 min

This incident

65% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

35 days
median 3 h 23 min
90 days agoToday

Other Vonage API incidents

All incidents

Vonage API·USA MMS - Delivery Degradation affecting MMS traffic for AT&T network

MMS delivery degradation affects Vonage API MMS traffic to AT&T network subscribers in the United States. This issue affects MMS North America and Global Connectivity - MMS North America. Vonage reports the status as investigating. The carrier knows about the issue and investigates the root cause.

Degraded

Vonage 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.

Resolved

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.

Degraded

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.

Degraded

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.

Resolved

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=vonage
Slack
/feed subscribe https://outages.cc/feed.xml?providers=vonage

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane