# Vonage: Archiving Server restarted in APS1

> Vonage status incident “Archiving Server restarted in APS1” on 2022-11-05: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/vonage/incidents/9m44zn0c14bv
Last updated: 2022-11-05T08:14:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2022-11-05 08:14 UTC · Resolved: 2022-11-05 08:14 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://vonageapi.statuspage.io/incidents/9m44zn0c14bv](https://vonageapi.statuspage.io/incidents/9m44zn0c14bv)
- [Company: Vonage](https://rewindex.com/company/vonage.md)

## Timeline of updates

- **resolved** 2022-11-05 08:14 UTC: From 7:45 am UTC till 7:50 am UTC an archiving server in our standard environment in aps1 rebooted. Some active archives on that server would have failed at that time. The server was immediately taken out of service, resolving the incident. Please contact support@api.vonage.com for any questions.

_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 2022-11-05 08:14 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/vonage/incidents/9m44zn0c14bv
- Citation: Vonage, “Archiving Server restarted in APS1” (2022-11-05 08:14 UTC). Archived by Rewindex: https://rewindex.com/company/vonage/incidents/9m44zn0c14bv (CC BY 4.0).
- Markdown link: `[Vonage: Archiving Server restarted in APS1 (2022-11-05)](https://rewindex.com/company/vonage/incidents/9m44zn0c14bv)`


---
Canonical: https://rewindex.com/company/vonage/incidents/9m44zn0c14bv · Markdown: https://rewindex.com/company/vonage/incidents/9m44zn0c14bv.md · JSON: https://rewindex.com/api/v1/companies/vonage/incidents/9m44zn0c14bv · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T13:06:04.985Z