Bandwidth Outage History

Bandwidth major outage · 1 active incident View live status →

Pingoru has recorded 310 incidents for Bandwidth: 310 in the last 12 months and 186 in the last 90 days.

Source: status.bandwidth.com

310incidents recorded
310last 12 months
186last 90 days
9 hourstypical duration
Incidents per month
050100AprMayJunJulAugSepOct83
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct75%
Pingoru began tracking Bandwidth in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202634288 of 720 (40%)
May 202623251 of 744 (34%)
June 20262380 of 720 (11%)
July 20262396 of 744 (13%)
August 20262997 of 744 (13%)
September 202668368 of 720 (51%)
October 202683424 of 570 (75%)

Incidents, newest first

Notice October 20, 2026 Bandwidth Local Market Impairment - 246 - Fredericksburg/Culpepper, VA 16h 8m 246 - Culpeper, VA

Started Oct 20, 2026, 01:21 AM UTC· resolved Oct 20, 2026, 05:29 PM UTC

  1. investigating Oct 20, 2026, 01:21 AM UTC

    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.

  2. investigating Oct 20, 2026, 04:55 AM UTC

    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.

  3. monitoring Oct 20, 2026, 07:44 AM UTC

    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.

  4. monitoring Oct 20, 2026, 11:32 AM UTC

    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.

  5. monitoring Oct 20, 2026, 01:50 PM UTC

    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.

  6. resolved Oct 20, 2026, 05:29 PM UTC

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

Read the full incident report →

Notice October 20, 2026 Bandwidth Local Market Impairment - 927 - Harrisonburg, VA 10h 29m 927 - Harrisonburg, VA

Started Oct 20, 2026, 01:08 AM UTC· resolved Oct 20, 2026, 11:38 AM UTC

  1. investigating Oct 20, 2026, 01:08 AM UTC

    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.

  2. investigating Oct 20, 2026, 04:56 AM UTC

    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.

  3. monitoring Oct 20, 2026, 08:02 AM UTC

    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.

  4. monitoring Oct 20, 2026, 08:02 AM UTC

    We are continuing to monitor for any further issues.

  5. resolved Oct 20, 2026, 11:38 AM UTC

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

Read the full incident report →

Minor October 19, 2026 MMS Delivery Incident - Verizon 5h 39m MMS Messaging (MM4)

Started Oct 19, 2026, 11:12 PM UTC· resolved Oct 20, 2026, 04:52 AM UTC

  1. investigating Oct 19, 2026, 11:12 PM UTC

    Bandwidth teams are investigating a deliverability incident for MMS messages to Verizon destinations.

  2. monitoring Oct 20, 2026, 04:39 AM UTC

    Teams are observing export network vehicle performance. We will monitor for stability

  3. resolved Oct 20, 2026, 04:52 AM UTC

    This incident has been resolved.

  4. postmortem Oct 20, 2026, 12:58 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 22:21 UTC on October 19th and 02:02 UTC on October 20th, MMS messages sent to Verizon were delivered with delays. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Minor October 19, 2026 SMS and MMS Delivery Delays - AT&T 7h 58m SMS Messaging (SMPP), MMS Messaging (MM4)

Started Oct 19, 2026, 09:38 PM UTC· resolved Oct 20, 2026, 05:36 AM UTC

  1. investigating Oct 19, 2026, 09:38 PM UTC

    Teams are investigating outbound, SMS and MMS messaging delivery delays towards AT&T destinations.

  2. monitoring Oct 20, 2026, 03:46 AM UTC

    Teams are observing expected messaging behavior and will monitor for stability.

  3. resolved Oct 20, 2026, 05:36 AM UTC

    This incident has been resolved.

  4. postmortem Oct 20, 2026, 11:03 AM UTC

    Between 22:27 UTC and 23:54 UTC on October 19, 2026, SMS and MMS messages sent to AT&T subscribers experienced delivery delays. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an Incident Report after investigations have concluded. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Minor October 19, 2026 Toll-free Port Activation Delays 6h 59m Number Porting

Started Oct 19, 2026, 01:06 PM UTC· resolved Oct 19, 2026, 08:06 PM UTC

  1. investigating Oct 19, 2026, 01:06 PM UTC

    Bandwidth teams are investigating an incident, impacting the timely activation of toll-free port orders.

  2. identified Oct 19, 2026, 06:39 PM UTC

    Due to an off-network condition, toll-free port orders remain delayed in activation. Teams are working with the impacted provider to restore expected port activation times.

  3. resolved Oct 19, 2026, 08:06 PM UTC

    This incident has been resolved.

  4. postmortem Oct 20, 2026, 12:49 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 12:00 UTC and 19:34 UTC on October 19, 2026, new Toll Free number activation requests were delayed. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 18, 2026 Bandwidth Local Market Impairment - 542 - Midland, TX 22h 30m 542 - Midland, TX

Started Oct 18, 2026, 08:06 AM UTC· resolved Oct 19, 2026, 06:37 AM UTC

  1. investigating Oct 18, 2026, 08:06 AM UTC

    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.

  2. investigating Oct 18, 2026, 10:59 AM UTC

    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

  3. identified Oct 18, 2026, 03:34 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  4. identified Oct 18, 2026, 06:55 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  5. monitoring Oct 18, 2026, 10:01 PM UTC

    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

  6. monitoring Oct 19, 2026, 02:12 AM UTC

    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

  7. monitoring Oct 19, 2026, 06:12 AM UTC

    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.

  8. resolved Oct 19, 2026, 06:37 AM UTC

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

Read the full incident report →

Notice October 18, 2026 New Number Order Delays 9h 22m New Number Ordering

Started Oct 18, 2026, 06:04 AM UTC· resolved Oct 18, 2026, 03:27 PM UTC

  1. monitoring Oct 18, 2026, 06:04 AM UTC

    Some number order orders may have been delayed in completing in a timely fashion. However, teams are observing expected portal behavior and are monitoring for stability.

  2. resolved Oct 18, 2026, 03:27 PM UTC

    This incident has been resolved.

  3. postmortem Oct 19, 2026, 09:19 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 03:33 UTC and 05:30 UTC on October 18th, new number orders were delayed. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 16, 2026 MMS Delivery Incident 2h 35m MMS Messaging (MM4)

Started Oct 16, 2026, 09:31 PM UTC· resolved Oct 17, 2026, 12:07 AM UTC

  1. investigating Oct 16, 2026, 09:31 PM UTC

    Bandwidth teams are investigating outbound MMS messaging delivery failures due to an off network industry condition. This incident impacts delivery to Verizon Wireless, AT&T, and T-Mobile destinations.

  2. monitoring Oct 16, 2026, 10:55 PM UTC

    Bandwidth teams are observing expected messaging behavior. Upon further investigation, it was deemed messages were delayed in delivery rather than failing.

  3. resolved Oct 17, 2026, 12:07 AM UTC

    This incident has been resolved.

  4. postmortem Oct 19, 2026, 08:50 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 19:16 UTC and 19:40 UTC on October 16th, MMS delivery to Verizon Wireless, AT&T, and T-Mobile destinations experienced sporadic delays. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 16, 2026 Bandwidth Local Market Impairment - 635 - Cedar Rapids, IA 3h 11m 635 - Cedar Rapids, IA

Started Oct 16, 2026, 08:41 AM UTC· resolved Oct 16, 2026, 11:52 AM UTC

  1. investigating Oct 16, 2026, 08:41 AM UTC

    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.

  2. resolved Oct 16, 2026, 11:52 AM UTC

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

Read the full incident report →

Notice October 16, 2026 Bandwidth Local Market Impairment - 644- Omaha, NE 2h 57m 644 - Omaha, NE

Started Oct 16, 2026, 07:39 AM UTC· resolved Oct 16, 2026, 10:37 AM UTC

  1. investigating Oct 16, 2026, 07:39 AM UTC

    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.

  2. resolved Oct 16, 2026, 10:37 AM UTC

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

Read the full incident report →

Notice October 16, 2026 Bandwidth Local Market Impairment - 646 - Grand Island, NE 3h 29m 646 - Grand Island, NE

Started Oct 16, 2026, 07:32 AM UTC· resolved Oct 16, 2026, 11:02 AM UTC

  1. investigating Oct 16, 2026, 07:32 AM UTC

    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.

  2. resolved Oct 16, 2026, 11:02 AM UTC

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

Read the full incident report →

Minor October 15, 2026 Messaging Delays - Verizon and T-Mobile 5h 44m SMS Messaging (SMPP), MMS Messaging (MM4)

Started Oct 15, 2026, 09:38 PM UTC· resolved Oct 16, 2026, 03:23 AM UTC

  1. investigating Oct 15, 2026, 09:39 PM UTC

    Bandwidth teams are investigating increased delays of messages toward Verizon and T-Mobile destinations.

  2. identified Oct 15, 2026, 11:17 PM UTC

    Teams have identified this incident as a result of an off network industry condition.

  3. monitoring Oct 16, 2026, 02:13 AM UTC

    Teams are observing expected messaging behavior. We will monitor for stability.

  4. resolved Oct 16, 2026, 03:23 AM UTC

    This incident has been resolved.

  5. postmortem Oct 16, 2026, 08:59 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 18:29 UTC on October 15th and 02:02 UTC on October 16th, messaging delivery to Verizon and T-Mobile was delayed. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 14, 2026 MMS Delivery Delays -T-Mobile & Verizon 6h 28m MMS Messaging (MM4)

Started Oct 14, 2026, 09:16 PM UTC· resolved Oct 15, 2026, 03:45 AM UTC

  1. investigating Oct 14, 2026, 09:16 PM UTC

    Bandwidth teams are investigating delays in MMS messages to T-Mobile and Verizon destinations. Specifically Long Code 10DLC.

  2. monitoring Oct 15, 2026, 02:32 AM UTC

    Teams are observing expected delivery of messages and will monitor for stability.

  3. resolved Oct 15, 2026, 03:45 AM UTC

    This incident has been resolved.

  4. postmortem Oct 15, 2026, 02:32 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 20:00 UTC on October 14th and 01:07 UTC on October 15th, MMS messages to T-Mobile and Verizon were delayed. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 14, 2026 Bandwidth Local Market Impairment - 654 - Cheyenne, WY 20h 48m 654 - Cheyenne, WY

Started Oct 14, 2026, 03:32 PM UTC· resolved Oct 15, 2026, 12:20 PM UTC

  1. investigating Oct 14, 2026, 03:32 PM UTC

    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.

  2. identified Oct 14, 2026, 07:32 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  3. identified Oct 14, 2026, 11:31 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  4. identified Oct 15, 2026, 03:26 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  5. identified Oct 15, 2026, 07:03 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  6. monitoring Oct 15, 2026, 08:57 AM UTC

    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.

  7. resolved Oct 15, 2026, 12:20 PM UTC

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

Read the full incident report →

Notice October 14, 2026 Toll-free port activation incident 1h 18m

Started Oct 14, 2026, 12:01 PM UTC· resolved Oct 14, 2026, 01:19 PM UTC

  1. resolved Oct 14, 2026, 01:42 PM UTC

    For a brief period of time, some toll-free port activations may have failed to activate as expected. Teams are observing normal toll-free report activations at this time and consider this incident resolved.

  2. postmortem Oct 15, 2026, 09:38 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 12:01 UTC and 13:19 UTC on October 14, 2026, new Toll Free activation requests routed through Lumen were delayed. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 14, 2026 Bandwidth Local Market Impairment - 538 - Tulsa, OK 11h 39m 538 - Tulsa, OK

Started Oct 14, 2026, 10:35 AM UTC· resolved Oct 14, 2026, 10:15 PM UTC

  1. investigating Oct 14, 2026, 10:35 AM UTC

    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.

  2. monitoring Oct 14, 2026, 02:53 PM UTC

    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.

  3. monitoring Oct 14, 2026, 07:28 PM UTC

    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.

  4. resolved Oct 14, 2026, 10:15 PM UTC

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

Read the full incident report →

Notice October 14, 2026 Bandwidth Local Market Impairment - 536 - Oklahoma City, OK 4h 21m 536 - Oklahoma City, OK

Started Oct 14, 2026, 05:26 AM UTC· resolved Oct 14, 2026, 09:47 AM UTC

  1. investigating Oct 14, 2026, 05:26 AM UTC

    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.

  2. monitoring Oct 14, 2026, 06:07 AM UTC

    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

  3. resolved Oct 14, 2026, 09:47 AM UTC

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

Read the full incident report →

Critical October 14, 2026 Bandwidth Local Market Impairment - 977 - Macomb, IL 6h 46m 977 - Macomb, IL

Started Oct 14, 2026, 05:15 AM UTC· resolved Oct 14, 2026, 12:01 PM UTC

  1. investigating Oct 14, 2026, 05:15 AM UTC

    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.

  2. investigating Oct 14, 2026, 07:56 AM UTC

    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.

  3. monitoring Oct 14, 2026, 09:49 AM UTC

    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.

  4. resolved Oct 14, 2026, 12:01 PM UTC

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

Read the full incident report →

Notice October 13, 2026 Outbound MMS Delays - T-Mobile 4h 39m MMS Messaging (MM4)

Started Oct 13, 2026, 09:19 PM UTC· resolved Oct 14, 2026, 01:59 AM UTC

  1. investigating Oct 13, 2026, 09:19 PM UTC

    Bandwidth teams are investigating outbound messages towards T-Mobile destinations. These messages are delayed in delivery.

  2. monitoring Oct 14, 2026, 12:55 AM UTC

    Teams are observing expected messaging delivery. We will monitor for stability.

  3. resolved Oct 14, 2026, 01:59 AM UTC

    This incident has been resolved.

  4. postmortem Oct 14, 2026, 08:09 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 20:00 UTC and 23:55 UTC on October 13th, outbound 10DLC MMS traffic to T-Mobile and Verizon experienced intermittent delivery delays. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →

Notice October 11, 2026 Bandwidth Local Market Impairment 956 - Johnson City, TN 3h 2m 956 - Johnson City, TN

Started Oct 11, 2026, 06:39 AM UTC· resolved Oct 11, 2026, 09:41 AM UTC

  1. investigating Oct 11, 2026, 06:39 AM UTC

    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.

  2. investigating Oct 11, 2026, 07:39 AM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 11, 2026, 09:41 AM UTC

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

Read the full incident report →

Critical October 9, 2026 Bandwidth Local Market Impairment - 554 - Longview, TX 17h 4m 554 - Longview, TX

Started Oct 09, 2026, 09:02 PM UTC· resolved Oct 10, 2026, 02:07 PM UTC

  1. investigating Oct 09, 2026, 09:02 PM UTC

    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.

  2. investigating Oct 10, 2026, 01:13 AM UTC

    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.

  3. investigating Oct 10, 2026, 04:59 AM UTC

    We are continuing to investigate this issue.

  4. identified Oct 10, 2026, 08:58 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  5. identified Oct 10, 2026, 10:50 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  6. identified Oct 10, 2026, 11:43 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  7. monitoring Oct 10, 2026, 02:06 PM UTC

    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.

  8. resolved Oct 10, 2026, 02:07 PM UTC

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

Read the full incident report →

Notice October 9, 2026 Bandwidth Local Market Impairment - 122 - Manchester, NH 2d 12h 122 - Manchester, NH

Started Oct 09, 2026, 08:45 AM UTC· resolved Oct 11, 2026, 09:33 PM UTC

  1. investigating Oct 09, 2026, 08:45 AM UTC

    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.

  2. investigating Oct 09, 2026, 09:43 AM UTC

    We are continuing to investigate this issue.

  3. investigating Oct 09, 2026, 11:45 AM UTC

    We are continuing to investigate this issue.

  4. investigating Oct 09, 2026, 02:53 PM UTC

    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.

  5. identified Oct 09, 2026, 03:53 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  6. identified Oct 09, 2026, 07:56 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  7. identified Oct 10, 2026, 12:11 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  8. identified Oct 10, 2026, 04:02 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  9. identified Oct 10, 2026, 07:59 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  10. identified Oct 10, 2026, 11:49 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  11. identified Oct 10, 2026, 03:46 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  12. identified Oct 10, 2026, 07:54 PM UTC

    We are continuing to work on a fix for this issue.

  13. identified Oct 10, 2026, 07:54 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  14. identified Oct 11, 2026, 01:03 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  15. identified Oct 11, 2026, 04:45 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  16. identified Oct 11, 2026, 08:42 AM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  17. identified Oct 11, 2026, 01:52 PM UTC

    Our carrier has identified the cause of this incident and is working to complete repairs.

  18. monitoring Oct 11, 2026, 06:40 PM UTC

    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

  19. resolved Oct 11, 2026, 09:33 PM UTC

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

Read the full incident report →

Notice October 9, 2026 Bandwidth Local Market Impairment - 920 - New Haven, CT 3h 8m 920 - New Haven, CT

Started Oct 09, 2026, 05:39 AM UTC· resolved Oct 09, 2026, 08:47 AM UTC

  1. investigating Oct 09, 2026, 05:39 AM UTC

    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.

  2. monitoring Oct 09, 2026, 06:48 AM UTC

    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.

  3. resolved Oct 09, 2026, 08:47 AM UTC

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

Read the full incident report →

Major October 9, 2026 Bandwidth Local Market Impairment - 328 (Dayton, OH) 2h 32m 328 - Dayton, OH

Started Oct 09, 2026, 12:18 AM UTC· resolved Oct 09, 2026, 02:50 AM UTC

  1. investigating Oct 09, 2026, 12:18 AM UTC

    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.

  2. investigating Oct 09, 2026, 12:19 AM UTC

    We are continuing to investigate this issue.

  3. resolved Oct 09, 2026, 02:50 AM UTC

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

Read the full incident report →

Minor October 8, 2026 Toll Free SMS Delays - Verizon 7h 42m Toll-Free SMS - Outbound

Started Oct 08, 2026, 09:04 PM UTC· resolved Oct 09, 2026, 04:47 AM UTC

  1. investigating Oct 08, 2026, 09:04 PM UTC

    Bandwidth teams are currently investigating toll-free SMS messaging delays to Verizon destination.

  2. identified Oct 08, 2026, 11:08 PM UTC

    Teams have identified the source of this incident as an off-network condition. We are engaged with the impacted industry provider and are working to restore expected messaging delivery.

  3. monitoring Oct 09, 2026, 02:41 AM UTC

    Teams are observing expected messaging traffic behavior and will monitor for stability.

  4. resolved Oct 09, 2026, 04:47 AM UTC

    This incident has been resolved.

  5. postmortem Oct 09, 2026, 11:43 AM UTC

    Between 13:00 UTC on October 8, 2026 and 01:58 UTC on October 9, 2026, toll-free SMS messages to Verizon experienced intermittent delivery failures and delays. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an Incident Report after investigations have concluded. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.

Read the full incident report →