# Bandwidth: V1 & V2 Voice and Messaging Incident

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2020-07-28 10:22 UTC · Resolved: 2020-07-28 12:29 UTC · Duration: 2.1 h
- Updates: 1
- [Vendor status page: https://status.bandwidth.com/incidents/rdq9wjxfp12n](https://status.bandwidth.com/incidents/rdq9wjxfp12n)
- [Company: Bandwidth](https://rewindex.com/company/bandwidth.md)

## Part of an outage event

- [AWS outage, Jul 28, 2020: 18 vendors, 18 incidents](https://rewindex.com/events/2020-07-28-aws)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +1 h 52 min vs the first vendor naming AWS)

```mermaid
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
  root --> h4
  me["Bandwidth (this incident)<br/>posted +1 h 52 min"]:::me
  root -.->|"same window"| me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2020-07-28 12:29 UTC: We have seen traffic restore and process as expected. With continued stability, Bandwidth considers this incident resolved.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/bandwidth/incidents/rdq9wjxfp12n · Markdown: https://rewindex.com/company/bandwidth/incidents/rdq9wjxfp12n.md · JSON: https://rewindex.com/api/v1/companies/bandwidth/incidents/rdq9wjxfp12n · Generated 2026-10-20T00:04:08.241Z