Vendor reports: major outageResolved · vendor status “resolved”Official status API

Bandwidth Local Market Impairment - 536 - Oklahoma City, OK

Reported by Bandwidth · Communication & Messaging · source last read 6 min ago

Official source (opens in a new tab)
Vendor start
Nov 10, 2026, 17:24 UTC
Vendor's clock
Resolved
Nov 11, 2026, 02:22 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
8 h 58 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Bandwidth reports major outage: "Bandwidth Local Market Impairment - 536 - Oklahoma City, OK".[E1, E2]
  • The vendor marked it resolved at 2026-11-11 02:22 UTC.[E3, E7]

Affected products and regions

  • Components: 536 - Oklahoma City, OK.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:42 UTC · summary s1, evidence 50c7c45b5d1f48b9

Evidence (7)
  1. E1Bandwidth reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Bandwidth Local Market Impairment - 536 - Oklahoma City, OK". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-11-10 17:24 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: 536 - Oklahoma City, OK. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-11-11 02:22 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: 536 - Oklahoma City, OK

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Bandwidth is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 10, 2026, 17:24 UTCVendor-reported startVendor time
  2. Nov 11, 2026, 02:22 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:42 UTCVendor marked it resolvedSeen by Statuswall
  4. Nov 11, 2026, 02:42 UTCVendor status changed: monitoring → resolvedSeen by Statuswall