Bandwidth Outage History

Bandwidth is up right now

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

Source: status.bandwidth.com

328incidents recorded
328last 12 months
194last 90 days
11 hourstypical duration
Incidents per month
050100AprMayJunJulAugSepOctNov8
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOctNov29%
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 20262373 of 720 (10%)
July 20262396 of 744 (13%)
August 20262997 of 744 (13%)
September 202668296 of 720 (41%)
October 202693288 of 744 (39%)
November 2026830 of 104 (29%)

Incidents, newest first

Notice November 4, 2026 Bandwidth Local Market Impairment - 248 - Richmond, VA 5h 41m 248 - Richmond, VA

Started Nov 04, 2026, 05:22 AM UTC· resolved Nov 04, 2026, 11:04 AM UTC

  1. identified Nov 04, 2026, 05:22 AM UTC

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

  2. monitoring Nov 04, 2026, 10:22 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 Nov 04, 2026, 11:04 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 November 3, 2026 Voice Authentication Incident - Pindrop 5h 7m Inbound Calling (SIP) - United States

Started Nov 03, 2026, 10:59 PM UTC· resolved Nov 04, 2026, 04:07 AM UTC

  1. investigating Nov 03, 2026, 10:59 PM UTC

    Bandwidth teams have identified an incident impacting our inbound Voice Authentication services. Teams are working to restore expected voice authentication behaviors.

  2. monitoring Nov 04, 2026, 03:01 AM UTC

    Teams are observing expected verification behavior and will monitor for prolonged stability.

  3. resolved Nov 04, 2026, 04:07 AM UTC

    This incident has been resolved.

Read the full incident report →

Major November 3, 2026 Outbound 10DLC MMS Delivery Incident - T-Mobile, Verizon, AT&T 11h 39m MMS Messaging (MM4)

Started Nov 03, 2026, 02:38 PM UTC· resolved Nov 04, 2026, 02:17 AM UTC

  1. investigating Nov 03, 2026, 02:38 PM UTC

    Bandwidth teams have identified an off-network incident impacting the timely delivery of MMS messages to T-Mobile and Verizon destinations. Bandwidth is working with this industry provider to restore expected MMS delivery.

  2. investigating Nov 03, 2026, 03:25 PM UTC

    Teams continue to work with the off net provided to resolve MMS delivery delays. This delay includes 10DLC Outbound MMS and Short Code MMS messages for T-Mobile, Verizon, and AT&T destinations.

  3. monitoring Nov 04, 2026, 01:24 AM UTC

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

  4. resolved Nov 04, 2026, 02:17 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 3, 2026 Bandwidth Local Market Impairment - 246 - Culpeper, VA 4h 55m 246 - Culpeper, VA

Started Nov 03, 2026, 06:31 AM UTC· resolved Nov 03, 2026, 11:26 AM UTC

  1. investigating Nov 03, 2026, 06:31 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 Nov 03, 2026, 09:25 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 Nov 03, 2026, 11:26 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 November 2, 2026 Outbound 10DLC MMS Delivery Incident 16h 29m MMS Messaging (MM4)

Started Nov 02, 2026, 08:05 PM UTC· resolved Nov 03, 2026, 12:34 PM UTC

  1. investigating Nov 02, 2026, 08:05 PM UTC

    Bandwidth teams have identified an off-network incident impacting the timely delivery of MMS messages to T-Mobile and Verizon destinations. Bandwidth is working with this industry provider to restore expected MMS delivery.

  2. resolved Nov 03, 2026, 12:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major November 2, 2026 Non-North American Emergency Address Validation Incident 7h 54m Bandwidth App, Bandwidth International (fka Voxbone) Portal

Started Nov 02, 2026, 07:49 PM UTC· resolved Nov 03, 2026, 03:43 AM UTC

  1. investigating Nov 02, 2026, 07:49 PM UTC

    Bandwidth teams are investigating an incident impacting the ability to validate non-North American addresses. These address validation requests may not complete as expected.

  2. identified Nov 02, 2026, 09:11 PM UTC

    Teams have identified the source of this incident and are working with the impacted vendor to restore expected address validation.

  3. resolved Nov 03, 2026, 03:43 AM UTC

    This incident has been resolved.

  4. postmortem Nov 03, 2026, 01:13 PM UTC

    Between 20:35 UTC on October 30 and 03:16 UTC November 3, customers encountered a disruption in the ability to validate non-North American addresses. 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 November 2, 2026 Brussels (BRU) data center incident 1m

Started Nov 02, 2026, 07:07 PM UTC· resolved Nov 02, 2026, 07:08 PM UTC

  1. resolved Nov 02, 2026, 09:07 PM UTC

    For a brief period of time, some inbound calls transversing our BRU data center failed to set up as expected. The data center has since recovered, and processing traffic as expected.

  2. postmortem Nov 03, 2026, 12:52 PM UTC

    Between 19:07 - 19:08 UTC on November 2, a subset of outbound calls were unable to be completed through our Brussels data center. 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 →

Notice November 2, 2026 Bandwidth Local Market Impairment - 130 - Providence, RI 5h 28m 130 - Providence, RI

Started Nov 02, 2026, 05:45 AM UTC· resolved Nov 02, 2026, 11:14 AM UTC

  1. identified Nov 02, 2026, 05:45 AM UTC

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

  2. monitoring Nov 02, 2026, 07: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 Nov 02, 2026, 11:14 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 31, 2026 Outbound 10DLC MMS Delivery Delays - T-Mobile & Verizon 2h 41m MMS Messaging (MM4)

Started Oct 31, 2026, 11:37 PM UTC· resolved Nov 01, 2026, 02:19 AM UTC

  1. identified Oct 31, 2026, 11:37 PM UTC

    Bandwidth teams have identified an off-network incident impacting the timely delivery of MMS messages to T-Mobile and Verizon destinations. Bandwidth is working with this industry provider to restore expected MMS delivery.

  2. resolved Nov 01, 2026, 02:19 AM UTC

    This incident has been resolved.

  3. postmortem Nov 02, 2026, 01:11 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between October 31 16:43 - November 1 01:04 UTC, outbound MMS messages to T-Mobile and Verizon may have encountered minimal delays in delivery. 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 30, 2026 Bandwidth Local Market Impairment - 246 - Culpeper, VA 10h 24m 246 - Culpeper, VA

Started Oct 30, 2026, 02:05 AM UTC· resolved Oct 30, 2026, 12:29 PM UTC

  1. investigating Oct 30, 2026, 02:05 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 30, 2026, 05:25 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 30, 2026, 08: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.

  4. monitoring Oct 30, 2026, 11: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.

  5. resolved Oct 30, 2026, 12: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 →

Critical October 29, 2026 Bandwidth Local Market Impairment - 658 - Colorado Springs, CO 1h 15m 658 - Colorado Springs, CO

Started Oct 29, 2026, 05:27 PM UTC· resolved Oct 29, 2026, 06:42 PM UTC

  1. investigating Oct 29, 2026, 05:27 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. monitoring Oct 29, 2026, 05: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.

  3. monitoring Oct 29, 2026, 06:42 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Oct 29, 2026, 06:42 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 →

Major October 29, 2026 Number Portability Checker Incident 2h 32m Number Porting

Started Oct 29, 2026, 03:09 PM UTC· resolved Oct 29, 2026, 05:42 PM UTC

  1. investigating Oct 29, 2026, 03:09 PM UTC

    Bandwidth teams are investigating the Number Portability Checker for both UI and API requests. These requests may return unexpected results or fail to complete.

  2. resolved Oct 29, 2026, 05:42 PM UTC

    This incident has been resolved.

  3. postmortem Oct 30, 2026, 09:15 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 16:59 UTC on October 28 and 17:19 UTC on October 29, requests to the Number Portability Checker API that asked for a JSON response returned an empty response instead of the portability information. 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 29, 2026 Bandwidth Local Market Impairment - 362 - Carbondale, IL 4h 25m 362 - Carbondale, IL

Started Oct 29, 2026, 05:42 AM UTC· resolved Oct 29, 2026, 10:08 AM UTC

  1. investigating Oct 29, 2026, 05:42 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 29, 2026, 09:33 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 29, 2026, 10:08 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 28, 2026 10DLC Campaign Provisioning - Order Delay 3h

Started Oct 28, 2026, 12:26 PM UTC· resolved Oct 28, 2026, 03:26 PM UTC

  1. resolved Oct 28, 2026, 05:20 PM UTC

    For a brief period of time, some 10DLC campaign requests were delayed in provisioning. At this time, we are observing expected provisioning times.

  2. postmortem Oct 29, 2026, 01:01 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 12:26 UTC and 15:26 UTC on October 28, some 10DLC campaign provisioning 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 28, 2026 Bandwidth Local Market Impairment - 548 - Wichita Falls, TX 7h 6m 548 - Wichita Falls, TX

Started Oct 28, 2026, 02:54 AM UTC· resolved Oct 28, 2026, 10:01 AM UTC

  1. investigating Oct 28, 2026, 02:54 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 28, 2026, 07:37 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 28, 2026, 10:01 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 27, 2026 Outbound MMS Delays - AT&T 1h 37m MMS Messaging (MM4)

Started Oct 27, 2026, 02:45 PM UTC· resolved Oct 27, 2026, 04:22 PM UTC

  1. investigating Oct 27, 2026, 02:45 PM UTC

    Bandwidth teams are investigating outbound MMS messages experiencing a delivery delay towards AT&T destinations.

  2. resolved Oct 27, 2026, 04:22 PM UTC

    This incident has been resolved.

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

    Bandwidth has concluded its investigation of this issue and determined that between 11:58 UTC and 15:09 UTC on October 27, 10DLC MMS sent to AT&T 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 →

Critical October 27, 2026 Bandwidth Local Market Impairment - 658 - Colorado Springs, CO 10h 10m 658 - Colorado Springs, CO

Started Oct 27, 2026, 04:45 AM UTC· resolved Oct 27, 2026, 02:56 PM UTC

  1. investigating Oct 27, 2026, 04: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. identified Oct 27, 2026, 09:46 AM UTC

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

  3. resolved Oct 27, 2026, 02:56 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 →

Minor October 26, 2026 LAX Data Center Incident 2h 39m Outbound Calling (SIP) - United States

Started Oct 26, 2026, 07:59 PM UTC· resolved Oct 26, 2026, 10:38 PM UTC

  1. investigating Oct 26, 2026, 07:59 PM UTC

    Bandwidth teams are currently investigating an outbound calling incident in our LAX data center. Outbound calls may in intermittently fail to complete as expected

  2. monitoring Oct 26, 2026, 09:36 PM UTC

    Bandwidth teams are observing expected network behavior and are monitoring for continued stability.

  3. resolved Oct 26, 2026, 10:38 PM UTC

    This incident has been resolved.

  4. postmortem Oct 27, 2026, 10:23 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 18:22 UTC and 20:52 UTC on October 26, a portion of outbound calls through the LAX data center experienced increased post-dial delay. 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 23, 2026 Toll-Free Port Activation Incident 2h 45m Number Porting

Started Oct 23, 2026, 12:11 PM UTC· resolved Oct 23, 2026, 02:57 PM UTC

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

    Bandwidth teams are investigating intermittent port activation failures for Toll-Free ports. These orders may fail with an unexpected error code.

  2. monitoring Oct 23, 2026, 01:40 PM UTC

    Teams are observing expected port activations and will continue to monitor for stability.

  3. resolved Oct 23, 2026, 02:57 PM UTC

    This incident has been resolved.

  4. postmortem Oct 29, 2026, 01:05 PM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 11:09 UTC and 12:05 UTC on October 23, some Toll-Free port activation orders experienced errors. 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 23, 2026 Bandwidth Local Market Impairment - 668 - Tucson, AZ 5h 4m 668 - Tucson, AZ

Started Oct 23, 2026, 06:20 AM UTC· resolved Oct 23, 2026, 11:25 AM UTC

  1. investigating Oct 23, 2026, 06:20 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 23, 2026, 09: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.

  3. resolved Oct 23, 2026, 11:25 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 22, 2026 Bandwidth Local Market Impairment - Fresno/Los Angeles/San Luis Obispo, CA 5h 7m 728 - Fresno, CA, 730 - Los Angeles, CA, 740 - San Luis Obispo, CA

Started Oct 22, 2026, 07:17 PM UTC· resolved Oct 23, 2026, 12:25 AM UTC

  1. investigating Oct 22, 2026, 07:17 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. monitoring Oct 22, 2026, 10:12 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. resolved Oct 23, 2026, 12:25 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 22, 2026 Inbound Messaging - Verizon & T-Mobile 2h 9m SMS Messaging (SMPP), MMS Messaging (MM4)

Started Oct 22, 2026, 06:31 PM UTC· resolved Oct 22, 2026, 08:40 PM UTC

  1. investigating Oct 22, 2026, 06:31 PM UTC

    Bandwidth teams are investigating an inbound messaging incident from Verizon and T-Mobile. These messages may not reach a Bandwidth subscriber due to an off network vendor incident.

  2. resolved Oct 22, 2026, 08:40 PM UTC

    This incident has been resolved.

  3. postmortem Oct 23, 2026, 10:39 AM UTC

    Bandwidth has concluded its investigation of this issue and determined that between 17:51 UTC on October 20 and 18:03 UTC on October 22, inbound SMS and MMS messages from T-Mobile and Verizon were not delivered to a limited set of Bandwidth telephone numbers. 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 22, 2026 Voice Authentication Incident - Pindrop 1h 39m Inbound Calling (SIP) - United States

Started Oct 22, 2026, 03:14 PM UTC· resolved Oct 22, 2026, 04:53 PM UTC

  1. identified Oct 22, 2026, 03:14 PM UTC

    Bandwidth teams have identified an off-network incident impacting our inbound Voice Authentication services. The impacted vendor is working to restore expected voice authentication behaviors.

  2. resolved Oct 22, 2026, 04:53 PM UTC

    This incident has been resolved.

  3. postmortem Oct 23, 2026, 08:36 AM UTC

    Between 00:00 UTC on October 21 and 16:05 UTC on October 22, some inbound calls using Voice Authentication services in the US region failed to complete. Bandwidth has concluded its investigation of this issue and details can be found in the following Incident Report: [https://www.bandwidth.com/support/en/articles/17756424-20261022-voice-us-pindrop-inbound-call-failures-after-siprec-release.](https://www.bandwidth.com/support/en/articles/17756424-20261022-voice-us-pindrop-inbound-call-failures-after-siprec-release.) 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 →

Critical October 22, 2026 Bandwidth Local Market Impairment - 328 - Dayton, OH 8h 59m 328 - Dayton, OH

Started Oct 22, 2026, 03:02 PM UTC· resolved Oct 23, 2026, 12:01 AM UTC

  1. investigating Oct 22, 2026, 03: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. identified Oct 22, 2026, 07:48 PM UTC

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

  3. resolved Oct 23, 2026, 12:01 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 22, 2026 Off-Net Port Activations 6h 51m Number Porting

Started Oct 22, 2026, 02:57 PM UTC· resolved Oct 22, 2026, 09:48 PM UTC

  1. identified Oct 22, 2026, 02:57 PM UTC

    Bandwidth teams have identified that due to a vendor condition some off net port orders are not activating as expected.

  2. monitoring Oct 22, 2026, 04:18 PM UTC

    Teams are observing expected port activation times and will monitor for stability.

  3. resolved Oct 22, 2026, 09:48 PM UTC

    This incident has been resolved.

  4. postmortem Oct 23, 2026, 09:34 AM UTC

    Between 12:40 UTC and 21:27 UTC on October 22, 2026, some off net port orders were not activating as expected due to a vendor condition. 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 →