# Bandwidth Local Market Impairment - 951 - Rocky Mount, NC - Provider: [Bandwidth](https://down.guide/bandwidth) - Level: confirmed - Impact: Major outage - lasted 4d 18h - started 2026-09-13 01:00 UTC - 951 - Rocky Mount, NC - id: DWN-0d987f2181 - Official page: https://stspg.io/mc22qm7x61vn ## Updates from Bandwidth ### 2026-09-13 01:00 UTC: investigating We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution. ### 2026-09-13 04:59 UTC: investigating We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution. ### 2026-09-13 07:51 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-13 11:22 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-13 15:22 UTC: investigating Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-13 19:33 UTC: investigating Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-13 21:11 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 00:50 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 09:01 UTC: identified We are continuing to work on a fix for this issue. ### 2026-09-14 09:09 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 10:13 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 14:13 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 18:13 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-14 22:14 UTC: identified We are continuing to work on a fix for this issue. ### 2026-09-15 03:37 UTC: identified We are continuing to work on a fix for this issue. ### 2026-09-15 13:11 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-15 17:00 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-15 23:04 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 02:58 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 06:40 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 10:29 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 13:42 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 18:27 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-16 22:30 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-17 02:27 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-17 07:16 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-17 11:22 UTC: identified Our carrier has identified the cause of this incident and is working to complete repairs. ### 2026-09-17 15:42 UTC: monitoring We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete ### 2026-09-17 19:09 UTC: resolved Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by Sazabi (https://sazabi.com/?utm_source=down-guide&utm_medium=markdown).