Vonage: Archiving Server restarted in APNE1
Timeline of updates
- resolved
At 10:45 PM UTC till 10:50 PM UTC, an archiving server in our standard environment in APNE1 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. [Update] Please note that this announcement was a false alarm. After further investigation, we were able to confirm that there was no customer impact, and no archives failed as a result of this. Please contact support@api.vonage.com if you have any questions.
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 2022-11-04 23:16 UTC, resolved after 0 min, 1 update(s).
- Title
- Archiving Server restarted in APNE1
- Vendor
- Vonage
- Date
- URL
- https://rewindex.com/company/vonage/incidents/csy9gf0z61rt
Vonage profileRecent Vonage incidentsAll outages on November 4, 2022Vonage in November 2022MarkdownJSON