rewindex

CompaniesBandwidthIncidents

Bandwidth: TN Lookup Incident

MinorStatus: resolvedStarted Resolved (2.5 h)1 updatestatus.bandwidth.com (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Oct 20, 2025 · 107 vendors, 151 incidents

Bandwidth’s incident depends on AWS (declared dependency, named as a cause before); it did not name AWS. (hop 1, posted +12 h 4 min vs AWS’s own post)

Swipe sideways to see the whole diagram.

depends on AWSblamed Twilioblamed Webflowblamed Basetenknown dependencyAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com +151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite +27Later45 vendors, 44 blamed AWSRudderStack, Airbyte, Unbounce +42Known dependency6 vendorsKlaviyo, Segment, Datadog +3Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did not name AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minBandwidth (this incident)posted +12 h 4 min
depends on AWSblamed Twilioblamed Webflowblamed Basetenknown dependencyAWS us-east-1posted 07:11 UTCPosted before AWS did5 vendors, 4 blamed AWSSalesforce, Descope, Ashby +2Within an hour18 vendors, 17 blamed AWSAsana, Firebolt, Monday.com+151 to 4 hours later30 vendors, 29 blamed AWSSingleStore, Loops, Buildkite+27Later45 vendors, 44 blamed AWSRudderStack, Airbyte,Unbounce +42Known dependency6 vendorsKlaviyo, Segment, Datadog +3Twilioposted +15 minBigCommerce+2 h 46 minWebflowposted +4 h 37 min, did notname AWSRootly+10 h 23 minBasetenposted +4 minZed+26 h 20 minBandwidth (this incident)posted +12 h 4 min
Bandwidth is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>posted 07:11 UTC"]:::root
  before["Posted before AWS did<br/>5 vendors, 4 blamed AWS<br/>Salesforce, Descope, Ashby +2"]:::blames
  root --> before
  h1["Within an hour<br/>18 vendors, 17 blamed AWS<br/>Asana, Firebolt, Monday.com +15"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>30 vendors, 29 blamed AWS<br/>SingleStore, Loops, Buildkite +27"]:::blames
  root --> h4
  later["Later<br/>45 vendors, 44 blamed AWS<br/>RudderStack, Airbyte, Unbounce +42"]:::blames
  root --> later
  dr["Known dependency<br/>6 vendors<br/>Klaviyo, Segment, Datadog +3"]:::hop2
  root -.->|"depends on AWS"| dr
  p0["Twilio<br/>posted +15 min"]:::blames
  root --> p0
  k0["BigCommerce<br/>+2 h 46 min"]:::hop2
  p0 -->|"blamed Twilio"| k0
  p1["Webflow<br/>posted +4 h 37 min, did not name AWS"]:::timing
  root -.-> p1
  k1["Rootly<br/>+10 h 23 min"]:::hop2
  p1 -->|"blamed Webflow"| k1
  p2["Baseten<br/>posted +4 min"]:::blames
  root --> p2
  k2["Zed<br/>+26 h 20 min"]:::hop2
  p2 -->|"blamed Baseten"| k2
  me["Bandwidth (this incident)<br/>posted +12 h 4 min"]:::me
  root -.->|"known dependency"| me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    This incident has been resolved.

From Bandwidth’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.bandwidth.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Bandwidth, started 2025-10-20 19:15 UTC, resolved after 2.5 h, 1 update(s).

Title
TN Lookup Incident
Vendor
Bandwidth
Date
URL
https://rewindex.com/company/bandwidth/incidents/sqy9r5kr4wm1

Bandwidth profileRecent Bandwidth incidentsAll outages on October 20, 2025Bandwidth in October 2025MarkdownJSON