Vonage API incident

Service Issue With Our Platform - Numbers Deactivation

Minor Resolved View vendor source →

Vonage API experienced a minor incident on May 11, 2026 affecting Number Deactivation, lasting 2h 52m. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 09:51 AM UTC
Resolved
May 11, 2026, 12:44 PM UTC
Duration
2h 52m
Detected by Pingoru
May 11, 2026, 09:51 AM UTC

Affected components

Number Deactivation

Update timeline

  1. investigating May 11, 2026, 09:51 AM UTC

    Our monitoring system has alerted us to a potential service issue with our platform. Customers may face issues wherein the number deactivations API are currently unable to return the deactivation files. If there is a customer impact, it is likely to be affecting the following products: Numbers Deactivation We aim to provide an update on our investigation within 1 hour. Please see this article - https://api.support.vonage.com/hc/en-us/articles/6749696044828-Vonage-API-Support-Incident-Handling - for an explanation of our approach to publishing incidents.

  2. monitoring May 11, 2026, 11:40 AM UTC

    Thank you for your patience. Our Engineering team has identified the issue impacing Number Deactivation and have applied mitigations to help resolve this issue. We are observing signs of recovery across the affected service. We will continue to monitor this issue for some more time and reach back here should anything change. Incident Start Time: 2026-05-07 15:00 UTC Incident End Time: 2026-05-11 9:15 UTC If you have any questions, please contact api.support.vonage.com

  3. resolved May 11, 2026, 12:44 PM UTC

    Vonage services have been restored and this incident has been fully resolved. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any further questions, please contact api.support.vonage.com