# Bandwidth: Messaging Insights Outage

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2022-07-28 18:08 UTC · Resolved: 2022-07-28 19:24 UTC · Duration: 1.3 h
- Updates: 1
- [Vendor status page: https://status.bandwidth.com/incidents/8fpgtgbxb6qt](https://status.bandwidth.com/incidents/8fpgtgbxb6qt)
- [Company: Bandwidth](https://rewindex.com/company/bandwidth.md)

## Part of an outage event

- [AWS us-east-2 outage, Jul 28, 2022: 25 vendors, 26 incidents](https://rewindex.com/events/2022-07-28-aws-us-east-2)
- This incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +57 min vs the first vendor naming AWS)

```mermaid
flowchart LR
  root["AWS us-east-2<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Elastic Cloud, Coralogix, Confluent, Aptible +1"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Stream (GetStream)"]:::blames
  root --> h4
  me["Bandwidth (this incident)<br/>posted +57 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** 2022-07-28 19:24 UTC: We've confirmed stability with function of the Messaging insights dashboard, and we're considering 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/8fpgtgbxb6qt · Markdown: https://rewindex.com/company/bandwidth/incidents/8fpgtgbxb6qt.md · JSON: https://rewindex.com/api/v1/companies/bandwidth/incidents/8fpgtgbxb6qt · Generated 2026-10-20T00:03:25.674Z