Vonage API outage, 8 November 2026

DE and CR SMS - Delivery degradation affecting a subset of LVNs towards Germany and Costa Rica networks

Started
Resolved
9 Nov 2026, 11:15 UTC (after 22 h 56 min)
Impact
Minor
Affected
SMS Europe, SMS Latin America

Is this still happening?

No. Vonage API marked this incident resolved on 9 Nov 2026, 11:15 UTC, 22 h 56 min after it began.

Right now: Vonage API reports degraded performance on some systems. (as of 13 Nov, 20:53 UTC) Live Vonage API status

At a glance

Our summary from the Vonage API incidents we have recorded since 24 Sept 2026 - how we count.

Last update from Vonage API

This incident has been resolved.

9 Nov 2026, 11:15 UTC

Read the full incident on the official Vonage API status page

Similar Vonage API incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , still open

    France SMS - Delivery degradation affecting a subset of LVNs towards France networks

  2. , resolved after 1 h 53 min

    Dominican Republic SMS - Delivery Degradation towards Claro network

  3. , resolved after 4 h 3 min

    Czech Republic SMS - Delivery Degradation towards T-Mobile Network

  4. , resolved after 6 h 2 min

    UK SMS - Delivery degradation of SMS traffic towards O2 UK Network

  5. , resolved after 3 h 20 min

    France SMS - Delivery degradation affecting registered SMS towards Orange network

Other recent Vonage API incidents

  1. Issues Impacting WhatsApp API

  2. Vonage API Help Center - Ticket Email Degradation

  3. France SMS - Delivery Degradation towards Lebara France

  4. Austria SMS - Delivery Degradation affecting A1 Telekom and Hutchison Drei Austria

  5. Slovakia SMS - Delivery Degradation towards Orange

  6. France SMS - Delivery Degradation towards Lebara France

  7. USA SMS - Delivery degradation affecting 10DLC traffic towards AT&T operator

  8. USA MMS - Delivery latency affecting MMS messages affecting multiple networks

All recorded Vonage API incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Vonage API's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.