Vonage: Service issue in Voice API platform
Timeline of updates
- resolved
We have identified and subsequently resolved an issue impacting a subset of outbound voice calls, with the disruption occurring between 2026-06-30 23:29 UTC and 2026-06-30 23:30 UTC. During the above window, some customers may have observed HTTP 500 responses for calls processed in the US East region. All services are now restored. 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.
From Vonage’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on vonageapi.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Vonage, started 2026-07-01 13:31 UTC, resolved after 0 min, 1 update(s).
- Title
- Service issue in Voice API platform
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/y8fqm92pgh0g
Vonage profileRecent Vonage incidentsAll outages on July 1, 2026Vonage in July 2026MarkdownJSON