# Vonage: Voice Incident

> Vonage status incident “Voice Incident” on 2022-07-27: impact none (vendor’s label), 30 h, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/vonage/incidents/mjttc1vwb2q1
Last updated: 2022-07-28T23:07:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2022-07-27 17:17 UTC · Resolved: 2022-07-28 23:07 UTC · Duration: 30 h
- Updates: 1
- [Vendor status page: https://vonageapi.statuspage.io/incidents/mjttc1vwb2q1](https://vonageapi.statuspage.io/incidents/mjttc1vwb2q1)
- [Company: Vonage](https://rewindex.com/company/vonage.md)

## Timeline of updates

- **resolved** 2022-07-28 23:07 UTC: We have monitored for 24 hours to investigate fully. We are working to gather what happened and what we can do to prevent this in the future. We'll provide more details in a post-mortem. Please contact support@vonage.com if you have any further concerns on this matter.

_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-07-27 17:17 UTC, resolved after 30 h, 1 update(s).

- Canonical URL: https://rewindex.com/company/vonage/incidents/mjttc1vwb2q1
- Citation: Vonage, “Voice Incident” (2022-07-27 17:17 UTC). Archived by Rewindex: https://rewindex.com/company/vonage/incidents/mjttc1vwb2q1 (CC BY 4.0).
- Markdown link: `[Vonage: Voice Incident (2022-07-27)](https://rewindex.com/company/vonage/incidents/mjttc1vwb2q1)`


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