Bandwidth outage, 20 October 2026

Bandwidth Local Market Impairment - 246 - Fredericksburg/Culpepper, VA

Started
Resolved
20 Oct 2026, 17:29 UTC (after 16 h 8 min)
Impact
Not stated
Affected
246 - Culpeper, VA

Is this still happening?

No. Bandwidth marked this incident resolved on 20 Oct 2026, 17:29 UTC, 16 h 8 min after it began.

Right now: Bandwidth reports all systems operational. (as of 26 Oct, 03:49 UTC) Live Bandwidth status

Last update from Bandwidth

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

20 Oct 2026, 17: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 19 h 33 min

    Bandwidth Local Market Impairment - 246 - Culpeper, VA

  2. , resolved after 15 h 50 min

    Bandwidth Local Market Impairment - 972 - Harrisonburg, VA

  3. , resolved after 10 h 29 min

    Bandwidth Local Market Impairment - 927 - Harrisonburg, VA

  4. , resolved after 2 days

    Bandwidth Local Market Impairment - 951 - Rocky Mount, NC

  5. , resolved after 5 h 4 min

    Bandwidth Local Market Impairment - 668 - Tucson, AZ

Other recent Bandwidth incidents

  1. Toll-Free Port Activation Incident

  2. Bandwidth Local Market Impairment - Fresno/Los Angeles/San Luis Obispo, CA

  3. Inbound Messaging - Verizon & T-Mobile

  4. Voice Authentication Incident - Pindrop

  5. Bandwidth Local Market Impairment - 328 - Dayton, OH

  6. Off-Net Port Activations

  7. US Voice Traffic

  8. Bandwidth Local Market Impairment - 521 - Jefferson City, MO

All recorded Bandwidth incidents