Bandwidth Outage History

Bandwidth is up right now

Bandwidth had 179 outages in the last 2 years totaling 292h 27m of downtime — averaging 7.4 incidents per month.

There were 179 Bandwidth outages since January 21, 2026 totaling 292h 27m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.bandwidth.com

Notice September 19, 2026

Messaging Incident - Verizon Wireless

Detected by Pingoru
Sep 19, 2026, 12:13 PM UTC
Resolved
Sep 19, 2026, 12:11 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 19, 2026, 12:13 PM UTC

    For a brief period of time outbound messages to Verizon Wireless destination were not delivering as expected. This was investigated and determined to be an off-network incident.

Read the full incident report →

Notice September 18, 2026

Bandwidth App - Insights Incident

Detected by Pingoru
Sep 18, 2026, 07:32 PM UTC
Resolved
Sep 18, 2026, 07:32 PM UTC
Duration
Timeline · 1 update
  1. resolved Sep 18, 2026, 07:32 PM UTC

    During this incident customers may have experienced delayed or duplicated call logs in Insights within the Bandwidth App. Teams have restored expected reporting behaviors.

Read the full incident report →

Critical September 17, 2026

Bandwidth Local Market Impairment - 234 - Pittsburgh, PA

Detected by Pingoru
Sep 17, 2026, 01:11 AM UTC
Resolved
Sep 17, 2026, 02:31 PM UTC
Duration
13h 19m
Affected: 234 - Pittsburgh, PA
Timeline · 7 updates
  1. investigating Sep 17, 2026, 01:11 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 Sep 17, 2026, 03: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. investigating Sep 17, 2026, 03:56 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 17, 2026, 07:46 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.

  5. monitoring Sep 17, 2026, 09:01 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

  6. monitoring Sep 17, 2026, 01:26 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

  7. resolved Sep 17, 2026, 02:31 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 September 16, 2026

Bandwidth Local Market Impairment - 920 - New Haven, CT

Detected by Pingoru
Sep 16, 2026, 05:35 AM UTC
Resolved
Sep 16, 2026, 10:25 AM UTC
Duration
4h 50m
Affected: 920 - New Haven, CT
Timeline · 3 updates
  1. investigating Sep 16, 2026, 05: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 Sep 16, 2026, 06: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 Sep 16, 2026, 10: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 →

Critical September 15, 2026

Bandwidth Local Market Impairment - 949 - Fayetteville, NC

Detected by Pingoru
Sep 15, 2026, 08:13 PM UTC
Resolved
Sep 16, 2026, 05:12 PM UTC
Duration
20h 59m
Affected: 949 - Fayetteville, NC
Timeline · 7 updates
  1. investigating Sep 15, 2026, 08:13 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 Sep 16, 2026, 12: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.

  3. investigating Sep 16, 2026, 01:50 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 16, 2026, 06:38 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.

  5. identified Sep 16, 2026, 09:11 AM UTC

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

  6. monitoring Sep 16, 2026, 12: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

  7. resolved Sep 16, 2026, 05:12 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 September 15, 2026

Bandwidth App Incident - IP Adding

Detected by Pingoru
Sep 15, 2026, 06:51 PM UTC
Resolved
Sep 15, 2026, 08:45 PM UTC
Duration
1h 54m
Affected: Bandwidth App
Timeline · 2 updates
  1. identified Sep 15, 2026, 06:51 PM UTC

    Bandwidth teams have identified an incident impacting the ability to add IPs for routing to the Bandwidth App. Teams are working to on restore expected portal behavior.

  2. resolved Sep 15, 2026, 08:45 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2026

Bandwidth App Incident - Registration Center — Brand Creation

Detected by Pingoru
Sep 14, 2026, 06:54 PM UTC
Resolved
Sep 15, 2026, 03:58 AM UTC
Duration
9h 4m
Affected: Bandwidth App
Timeline · 2 updates
  1. investigating Sep 14, 2026, 06:54 PM UTC

    Bandwidth teams are currently investigating an incident on the Bandwidth App impacting the Registration Center and Brand creation. Users are unable to create a new Brand at this time. Teams are working to restore expected portal behavior.

  2. resolved Sep 15, 2026, 03:58 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2026

Outbound SMS Incident - T-Mobile

Detected by Pingoru
Sep 14, 2026, 06:31 PM UTC
Resolved
Sep 16, 2026, 12:09 AM UTC
Duration
1d 5h
Affected: SMS Messaging (SMPP)
Timeline · 4 updates
  1. investigating Sep 14, 2026, 06:31 PM UTC

    Bandwidth teams are investigating an off network condition where outbound SMS messages to T-Mobile are receiving an unexpected error code of 4740. These messages may not complete as expected.

  2. identified Sep 14, 2026, 11:46 PM UTC

    This incident has been identified as an off network incident. T-Mobile is working to restore expected delivery results. Updates will be provided as they become available.

  3. identified Sep 15, 2026, 06:52 PM UTC

    This incident has been identified as an off network incident. T-Mobile is working to restore expected delivery results. Updates will be provided as they become available.

  4. resolved Sep 16, 2026, 12:09 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor September 14, 2026

Outbound SIP Auth Calling incident

Detected by Pingoru
Sep 14, 2026, 06:10 AM UTC
Resolved
Sep 14, 2026, 08:38 AM UTC
Duration
2h 27m
Affected: Outbound Calling (SIP) - United States
Timeline · 3 updates
  1. investigating Sep 14, 2026, 06:10 AM UTC

    Teams are investigating an incident impacting outbound SIP auth TLS calls. These calls may fail to complete as expected.

  2. identified Sep 14, 2026, 06:22 AM UTC

    Teams have identified the incident and are working to restore expected network performance.

  3. resolved Sep 14, 2026, 08:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 13, 2026

Bandwidth Local Market Impairment - 974 - Rochester, NY

Detected by Pingoru
Sep 13, 2026, 09:26 PM UTC
Resolved
Sep 13, 2026, 09:55 PM UTC
Duration
28m
Affected: 974 - Rochester, NY
Timeline · 2 updates
  1. investigating Sep 13, 2026, 09:26 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. resolved Sep 13, 2026, 09:55 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 September 12, 2026

LATA 248 - CLEC Market Outage - Richmond, VA

Detected by Pingoru
Sep 12, 2026, 12:49 AM UTC
Resolved
Sep 12, 2026, 01:34 PM UTC
Duration
12h 44m
Affected: 248 - Richmond, VA
Timeline · 7 updates
  1. investigating Sep 11, 2026, 10:25 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 Sep 12, 2026, 12:44 AM UTC

    Current Status: A field technician is onsite and actively working with the Core NOC to investigate the issue further. Service remains impacted at this time, and an estimated time to resolution is not yet available. Next Steps: The investigation will continue with the onsite technician and Core NOC working together to identify the cause of the outage and determine the actions needed to restore service. Additional updates will be provided as more information becomes available. Next Update Expected: 9/11/2026 10:05 PM EDT

  3. investigating Sep 12, 2026, 04:24 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. identified Sep 12, 2026, 08:29 AM UTC

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

  5. monitoring Sep 12, 2026, 01:33 PM UTC

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

  6. monitoring Sep 12, 2026, 01:34 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.

  7. resolved Sep 12, 2026, 01:34 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 September 11, 2026

Isolated LAX Datacenter Incident

Detected by Pingoru
Sep 11, 2026, 02:51 PM UTC
Resolved
Sep 11, 2026, 03:40 PM UTC
Duration
48m
Affected: Inbound Calling (SIP) - United StatesOutbound Calling (SIP) - United States
Timeline · 3 updates
  1. investigating Sep 11, 2026, 02:51 PM UTC

    Bandwidth teams are investigating an isolated incident in our LAX Datacenter. Some calls may not complete as expected.

  2. monitoring Sep 11, 2026, 03:24 PM UTC

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

  3. resolved Sep 11, 2026, 03:40 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 11, 2026

Bandwidth Local Market Impairment - 226 - Harrisburg, PA

Detected by Pingoru
Sep 11, 2026, 04:32 AM UTC
Resolved
Sep 11, 2026, 08:59 AM UTC
Duration
4h 27m
Affected: 226 - Harrisburg, PA
Timeline · 3 updates
  1. investigating Sep 11, 2026, 04: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. monitoring Sep 11, 2026, 08:01 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 Sep 11, 2026, 08:59 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 September 10, 2026

Messaging Delivery Incident- AT&T

Detected by Pingoru
Sep 10, 2026, 11:24 PM UTC
Resolved
Sep 11, 2026, 03:40 PM UTC
Duration
16h 15m
Affected: SMS Messaging (SMPP)MMS Messaging (MM4)REST APIs - HTTP SMS MessagingREST APIs - HTTP MMS Messaging
Timeline · 4 updates
  1. identified Sep 10, 2026, 06:04 PM UTC

    Bandwidth teams have identified an off-network incident resulting in intermittent messages delivery failures to AT&T destinations. These failures result in a 4740 code. Teams are working with AT&T to restore expected delivery of messages.

  2. identified Sep 10, 2026, 11:24 PM UTC

    Band with teams continue to partner with the impacted industry provider.

  3. identified Sep 11, 2026, 01:17 PM UTC

    Bandwidth teams continue to partner with the impacted industry provider. Updates will be provided as they become available.

  4. resolved Sep 11, 2026, 06:20 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 10, 2026

Bandwidth Local Market Impairment - 330 - Evansville, IN

Detected by Pingoru
Sep 10, 2026, 04:24 AM UTC
Resolved
Sep 10, 2026, 10:01 AM UTC
Duration
5h 37m
Affected: 330 - Evansville, IN
Timeline · 3 updates
  1. investigating Sep 10, 2026, 04:24 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 Sep 10, 2026, 05:40 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 Sep 10, 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 →

Critical September 10, 2026

Bandwidth Local Market Impairment - 340 - DETROIT, M

Detected by Pingoru
Sep 10, 2026, 03:13 AM UTC
Resolved
Sep 10, 2026, 02:22 PM UTC
Duration
11h 8m
Affected: 340 - Southfield, MI
Timeline · 7 updates
  1. investigating Sep 10, 2026, 03: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.

  2. investigating Sep 10, 2026, 03:14 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 Sep 10, 2026, 06: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.

  4. investigating Sep 10, 2026, 10:36 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.

  5. monitoring Sep 10, 2026, 01:35 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 Sep 10, 2026, 02:22 PM UTC

    We are continuing to monitor for any further issues.

  7. resolved Sep 10, 2026, 02:22 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 September 9, 2026

Bandwidth Local Market Impairment - 636 - Fargo, ND

Detected by Pingoru
Sep 09, 2026, 03:02 PM UTC
Resolved
Sep 09, 2026, 07:35 PM UTC
Duration
4h 33m
Affected: 636 - Fargo, ND
Timeline · 3 updates
  1. investigating Sep 09, 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. monitoring Sep 09, 2026, 04:24 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 Sep 09, 2026, 07:35 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 September 9, 2026

Bandwidth Local Market Impairment - 340 - Southfield, MI

Detected by Pingoru
Sep 09, 2026, 09:13 AM UTC
Resolved
Sep 09, 2026, 08:26 PM UTC
Duration
11h 12m
Affected: 340 - Southfield, MI
Timeline · 5 updates
  1. investigating Sep 09, 2026, 09: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.

  2. monitoring Sep 09, 2026, 10: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. investigating Sep 09, 2026, 01:33 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.

  4. monitoring Sep 09, 2026, 03:36 PM UTC

    We have observed services in this market have recovered. This incident will be resolved when we confirm all repairs are complete

  5. resolved Sep 09, 2026, 08:26 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 September 8, 2026

Port Order Delays - Toll Free Numbers

Detected by Pingoru
Sep 08, 2026, 01:36 PM UTC
Resolved
Sep 08, 2026, 06:04 PM UTC
Duration
4h 27m
Affected: Number Porting
Timeline · 2 updates
  1. identified Sep 08, 2026, 01:36 PM UTC

    Bandwidth teams have identified an incident impact the timely activations of Port Orders. Currently; Port Orders are not activating. Teams are working to restore expected porting behaviors.

  2. resolved Sep 08, 2026, 06:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 8, 2026

Germany Datacenter Incident

Detected by Pingoru
Sep 08, 2026, 11:02 AM UTC
Resolved
Sep 08, 2026, 01:01 PM UTC
Duration
1h 58m
Affected: Inbound Calling - GermanyOutbound Calling - Germany
Timeline · 3 updates
  1. investigating Sep 08, 2026, 11:02 AM UTC

    Bandwidth teams are investigating an incident with our Germany datacenter. Calls transversing over this location may experience low call quality. Teams are working to restore expected network performance.

  2. monitoring Sep 08, 2026, 11:22 AM UTC

    Teams are observing, expected network behavior, and will continue to monitor for stability.

  3. resolved Sep 08, 2026, 01:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 7, 2026

Bandwidth Local Market Impairment - 240 - Frederick, MD

Detected by Pingoru
Sep 07, 2026, 07:33 AM UTC
Resolved
Sep 07, 2026, 10:57 AM UTC
Duration
3h 23m
Affected: 240 - Frederick, MD
Timeline · 3 updates
  1. investigating Sep 07, 2026, 07:33 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 Sep 07, 2026, 08:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 07, 2026, 10:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 7, 2026

Bandwidth Local Market Impairment - 973 - Palm Springs, CA

Detected by Pingoru
Sep 07, 2026, 02:47 AM UTC
Resolved
Sep 07, 2026, 01:33 PM UTC
Duration
10h 46m
Affected: 973 - Palm Springs, CA
Timeline · 6 updates
  1. investigating Sep 07, 2026, 02:47 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 Sep 07, 2026, 07:07 AM UTC

    We are continuing to investigate this issue.

  3. investigating Sep 07, 2026, 08:51 AM UTC

    We are continuing to investigate this issue.

  4. investigating Sep 07, 2026, 11:24 AM UTC

    We are continuing to investigate this issue.

  5. monitoring Sep 07, 2026, 12:22 PM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Sep 07, 2026, 01:33 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical September 4, 2026

Bandwidth Local Market Impairment - 638 - Bismarck, ND

Detected by Pingoru
Sep 04, 2026, 05:06 PM UTC
Resolved
Sep 05, 2026, 01:18 AM UTC
Duration
8h 11m
Affected: 638 - Bismarck,ND
Timeline · 4 updates
  1. investigating Sep 04, 2026, 05:06 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 Sep 04, 2026, 08:05 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.

  3. monitoring Sep 05, 2026, 12: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

  4. resolved Sep 05, 2026, 01:18 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 September 4, 2026

STIR/SHAKEN Signing Incident

Detected by Pingoru
Sep 04, 2026, 01:09 AM UTC
Resolved
Sep 04, 2026, 01:09 AM UTC
Duration
Timeline · 1 update
  1. resolved Sep 04, 2026, 01:09 AM UTC

    For a short period of time calls were not being signed with regards to STIR/SHAKEN. No call failure were observed with this incident. Proper call signing has been restored.

Read the full incident report →