# Bandwidth: V2 Calling Incident

> Bandwidth status incident “V2 Calling Incident” on 2020-07-22: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/bandwidth/incidents/xfg5k3x163jd
Last updated: 2020-07-22T11:00:00Z

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

## Timeline of updates

- **resolved** 2020-07-22 11:00 UTC: Bandwidth teams identified a network condition impacting a small subset of customers. This condition caused inbound and outbound calls to be rejected. Bandwidth teams have resolved the incident, and we have observed inbound and outbound call traffic processing as expected. We consider this incident resolved.

_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-07-22 11:00 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/bandwidth/incidents/xfg5k3x163jd
- Citation: Bandwidth, “V2 Calling Incident” (2020-07-22 11:00 UTC). Archived by Rewindex: https://rewindex.com/company/bandwidth/incidents/xfg5k3x163jd (CC BY 4.0).
- Markdown link: `[Bandwidth: V2 Calling Incident (2020-07-22)](https://rewindex.com/company/bandwidth/incidents/xfg5k3x163jd)`


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