Live / Incidents / Vonage
Vonage: Voice API Latency Issue - US-East
Vonage · vonage.comImpact: minorResolved2026-09-21 13:42 UTC
Public — what happened
Summary
Vonage services have been fully restored following today's service interruption to your Voice API requests in the US-East-1 region, which began at 2026-09-21 01:28 UTC.
Full resolution has been confirmed effective 2026-09-21 04:13 UTC.
Thank you for your patience and understanding as we worked to restore services as quickly as possible.
If you have any questions, please contact api.support.vonage.com OR https://www.vonage.com/support/
Timeline
- Started — 2026-09-21 04:25 UTC
- Last update — 2026-09-21 13:42 UTC
- Resolved — 2026-09-21 13:42 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Vonage against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Vonage: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Vonage report →