# Bandwidth: Potential V1 and V2 Failures

> Bandwidth status incident “Potential V1 and V2 Failures” on 2020-10-22: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0
Last updated: 2020-10-22T18:30:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2020-10-22 18:30 UTC · Resolved: 2020-10-22 18:30 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.bandwidth.com/incidents/nfdvrq4xm1f0](https://status.bandwidth.com/incidents/nfdvrq4xm1f0)
- [Company: Bandwidth](https://rewindex.com/company/bandwidth.md)

## Timeline of updates

- **resolved** 2020-10-22 18:30 UTC: Between 2:32 PM and 2:37 PM EST, customers may have experienced failures with V1 and V2 voice. The incident is now stable and we are actively investigating the cause of the issue.

_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 Bandwidth, started 2020-10-22 18:30 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0
- Citation: Bandwidth, “Potential V1 and V2 Failures” (2020-10-22 18:30 UTC). Archived by Rewindex: https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0 (CC BY 4.0).
- Markdown link: `[Bandwidth: Potential V1 and V2 Failures (2020-10-22)](https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0)`


---
Canonical: https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0 · Markdown: https://rewindex.com/company/bandwidth/incidents/nfdvrq4xm1f0.md · JSON: https://rewindex.com/api/v1/companies/bandwidth/incidents/nfdvrq4xm1f0 · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T15:02:53.961Z
