Vonage API outage, 12 November 2026

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

Started
Resolved
12 Nov 2026, 04:40 UTC (after 3 h 25 min)
Impact
Minor
Affected
SMS North America

Is this still happening?

No. Vonage API marked this incident resolved on 12 Nov 2026, 04:40 UTC, 3 h 25 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.

12 Nov 2026, 04:40 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. , resolved after 25 h 29 min

    USA SMS- Delivery degradation affecting SMS 10DLC/SC traffic towards multiple operators

  2. , resolved after 2 h 17 min

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

  3. , resolved after 1 h 25 min

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

  4. , resolved after 4 h 54 min

    USA SMS & MMS - Delivery degradation affecting TFN & 10DLC traffic towards AT&T operator

  5. , resolved after 1 h 39 min

    USA SMS/MMS - Delivery degradation affecting SMS and MMS traffic towards AT&T operator

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 MMS - Delivery latency affecting MMS messages affecting multiple networks

  8. Issue with Spain Movistar RCS Delivery

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.