Live

Dominican Republic SMS - Delivery Degradation towards Claro network

0

SMS delivery is degraded for the Claro network in the Dominican Republic. This affects SMS Latin America and Global Connectivity - SMS Latin America. Vonage API reports that the incident is under investigation.

State

Investigating

Started

Ongoing for

23 min

Worst impact

Degraded

Timeline

1 update
17:4517:5117:5618:0218:08
DegradedUpdate postedTimes in UTC

Investigating

23 min 100%

Updates

Times in UTC

As posted by Vonage API

Investigating

We are currently observing SMS delivery degradation towards Claro network. We are working with our carrier partners to resolve the issue and 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
SMS Latin AmericaGlobal Connectivity - SMS Latin America

Vonage API in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

65

Days with an incident

44

Median duration

3 h 26 min

This incident

89% 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 26 min
90 days agoToday

Other Vonage API incidents

All incidents

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.

Resolved

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.

Resolved

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.

Resolved

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.

Resolved

Vonage API·France SMS - Delivery degradation affecting SMS towards Orange France

SMS delivery to the Orange France network does not work correctly. The affected components are SMS Europe and Global Connectivity - SMS Europe. Vonage API reports that the incident is resolved after 103 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.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.

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane