Bandwidth outage, 10 November 2026

Bandwidth Local Market Impairment - 532 - Wichita, KS

Started
Resolved
10 Nov 2026, 10:29 UTC (after 2 h 50 min)
Impact
Not stated
Affected
532 - Wichita, KS

Is this still happening?

No. Bandwidth marked this incident resolved on 10 Nov 2026, 10:29 UTC, 2 h 50 min after it began.

Right now: Bandwidth reports all systems operational. (as of 13 Nov, 20:15 UTC) Live Bandwidth status

At a glance

Our summary from the Bandwidth incidents we have recorded since 6 Oct 2026 - how we count.

Last update from Bandwidth

Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.

10 Nov 2026, 10:29 UTC

Read the full incident on the official Bandwidth status page

Similar Bandwidth incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved after 7 h 7 min

    Bandwidth Local Market Impairment - 548 - Wichita Falls, TX

  2. , still open

    Bandwidth Local Market Impairment - 548 - Wichita Falls, TX

  3. , resolved after 3 h 25 min

    Bandwidth Local Market Impairment - 548 - Wichita Falls, TX

  4. , resolved after 8 h 57 min

    Bandwidth Local Market Impairment - 536 - Oklahoma City, OK

  5. , resolved after 4 h 33 min

    Bandwidth Local Market Impairment - Grand Island, NE

Other recent Bandwidth incidents

  1. Bandwidth AppPostmortem

  2. Intermittent Call FailuresPostmortem

  3. AT&T SMS DelaysPostmortem

  4. JFK Calling Incident - Inbound/Outbound CallingPostmortem

  5. Toll-Free Port Activation DelaysPostmortem

  6. Bandwidth Local Market Impairment - 256 Clarksburg WV

  7. Bandwidth Local Market Impairment - 248 - Richmond, VA

  8. Voice Authentication Incident - PindropPostmortem

All recorded Bandwidth incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Bandwidth's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.