# Vonage: Archive Service Impacted

> Vonage status incident “Archive Service Impacted” on 2025-03-16: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/vonage/incidents/jjt3vgbq803c
Last updated: 2025-03-16T22:12:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2025-03-16 22:12 UTC · Resolved: 2025-03-16 22:12 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://vonageapi.statuspage.io/incidents/jjt3vgbq803c](https://vonageapi.statuspage.io/incidents/jjt3vgbq803c)
- [Company: Vonage](https://rewindex.com/company/vonage.md)

## Timeline of updates

- **resolved** 2025-03-16 22:12 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/vonage/incidents/jjt3vgbq803c
- Citation: Vonage, “Archive Service Impacted” (2025-03-16 22:12 UTC). Archived by Rewindex: https://rewindex.com/company/vonage/incidents/jjt3vgbq803c (CC BY 4.0).
- Markdown link: `[Vonage: Archive Service Impacted (2025-03-16)](https://rewindex.com/company/vonage/incidents/jjt3vgbq803c)`


---
Canonical: https://rewindex.com/company/vonage/incidents/jjt3vgbq803c · Markdown: https://rewindex.com/company/vonage/incidents/jjt3vgbq803c.md · JSON: https://rewindex.com/api/v1/companies/vonage/incidents/jjt3vgbq803c · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T16:06:12.350Z