Vonage: Archive Service Impacted
Timeline of updates
- resolved
We experienced a brief incident involving a pod restart in the Video API service. The issue has been resolved. The last affected archive occurred at 2025-03-13T20:32:58 GMT. Archives started after this timestamp were not impacted by delays or partial data loss. If you have additional questions, please contact us at support@api.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 2025-03-16 22:12 UTC, resolved after 0 min, 1 update(s).
- Title
- Archive Service Impacted
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/jjt3vgbq803c
Vonage profileRecent Vonage incidentsAll outages on March 16, 2025Vonage in March 2025MarkdownJSON