outages.live
Live
Vonage APIMaintenance ·

Planned Maintenance Window 2 — API Platform

MaintenanceOfficial update

SCHEDULED INFRASTRUCTURE MAINTENANCE – NOVEMBER 2026 As part of our planned infrastructure maintenance, we will be performing two scheduled maintenance windows. MAINTENANCE WINDOW 1 Monday, 16 November 2026 | 05:00–05:30 UTC — ~15 second interruption expected. MAINTENANCE WINDOW 2 Monday, 23 November 2026 | 05:00–05:30 UTC — ~1 minute interruption expected. POTENTIAL IMPACT Fraud Defender - Windows 1 & 2: Rule updates, burst protection, custom alerts, and DNO Checker changes may be briefly unavailable. Existing rules remain active. SMS API – Vonage Traffic Control (VTC) - Windows 1 & 2: VTC configuration updates may be briefly unavailable. SMS API – Branded Text - Windows 1 & 2: Branded Text configuration updates may be briefly unavailable. Messages API – Email Channel - Windows 1 & 2: Email domain onboarding and provisioning may be briefly unavailable. Messages API – Channel Manager - Windows 1 & 2: The RCS Opt-out Management API may be briefly unavailable. Verify API – Email Channel

The latest update from Vonage API.

State

Scheduled

Starts

Ongoing for

Not started

Worst impact

Maintenance

Updates

Times in UTC

As posted by Vonage API

Scheduled

SCHEDULED INFRASTRUCTURE MAINTENANCE – NOVEMBER 2026 As part of our planned infrastructure maintenance, we will be performing two scheduled maintenance windows. MAINTENANCE WINDOW 1 Monday, 16 November 2026 | 05:00–05:30 UTC — ~15 second interruption expected. MAINTENANCE WINDOW 2 Monday, 23 November 2026 | 05:00–05:30 UTC — ~1 minute interruption expected. POTENTIAL IMPACT Fraud Defender - Windows 1 & 2: Rule updates, burst protection, custom alerts, and DNO Checker changes may be briefly unavailable. Existing rules remain active. SMS API – Vonage Traffic Control (VTC) - Windows 1 & 2: VTC configuration updates may be briefly unavailable. SMS API – Branded Text - Windows 1 & 2: Branded Text configuration updates may be briefly unavailable. Messages API – Email Channel - Windows 1 & 2: Email domain onboarding and provisioning may be briefly unavailable. Messages API – Channel Manager - Windows 1 & 2: The RCS Opt-out Management API may be briefly unavailable. Verify API – Email Channel

Affected components

26
Account Access & NotificationsSMSNetwork RegistryArchiving (Standard)Account Configuration & Feature AccessSMPPArchiving (Enterprise)Verify V2

Vonage API in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

77

Days with an incident

49

Median duration

3 h 24 min

This incident

Not comparable

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

35 days
median 3 h 24 min
90 days agoToday

Other Vonage API incidents

All incidents

Vonage API·Issue with Spain Movistar RCS Delivery

RCS delivery to Spain Movistar does not work. The problem affects RCS Connectivity and Global Connectivity - RCS Connectivity. Vonage API reports that it is investigating the issue.

Degraded

Vonage API·Issue with WhatsApp onboarding

Vonage API reports that WhatsApp onboarding does not work for WhatsApp Connectivity and Global Connectivity - Whatsapp Connectivity. Vonage reports that a third party provider identified the issue and put a fix in place. Vonage continues to monitor the situation.

Degraded

Vonage API·Service issue in Voice platform

Vonage reports a service issue that affects the Voice API and SIP Trunking, and PSTN/SIP connectivity in the APAC region. Vonage states that the issue is resolved. Vonage gives the start time as 2026-11-10 09:47 UTC and the resolution time as 2026-11-10 10:11 UTC.

Resolved

Vonage API·France SMS - Delivery Degradation towards Bouygues Telecom

Vonage API reported degraded SMS delivery toward Bouygues Telecom in France. The incident affected SMS Europe and Global Connectivity - SMS Europe. Vonage API resolved the incident after 79 minutes.

Resolved

Vonage API·France Silent Authentication - Service degradation affecting Bouygues Telecom networks

Vonage API reports degraded Silent Authentication on Bouygues Telecom networks in France. The affected components are Verify SilentAuth Europe and Global Connectivity - Verify SilentAuth Europe. Vonage API states that the incident is resolved, and it lasted 142 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