Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Bandwidth outage history

    261 recorded Bandwidth incidents since April 2026, with official updates, affected components, duration and resolution information.

    Back to current status

    LAX Data Center Incident

    Started October 26, 2026 at 7:59 PM UTC · 2h 39m

    IssuesMinor incident
    Affected components
    Outbound Calling (SIP) - United States
    1. October 26, 2026 at 7:59 PM UTCinvestigating

      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. October 26, 2026 at 9:36 PM UTCmonitoring

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

    3. October 26, 2026 at 10:38 PM UTCresolved

      This incident has been resolved.

    Toll-Free Port Activation Incident

    Started October 23, 2026 at 12:11 PM UTC · 2h 46m

    IssuesMinor incident
    Affected components
    Number Porting
    1. October 23, 2026 at 12:11 PM UTCinvestigating

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

    2. October 23, 2026 at 1:40 PM UTCmonitoring

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

    3. October 23, 2026 at 2:57 PM UTCresolved

      This incident has been resolved.

    Bandwidth Local Market Impairment - 668 - Tucson, AZ

    Started October 23, 2026 at 6:20 AM UTC · 5h 5m

    Pending
    Affected components
    668 - Tucson, AZ
    1. October 23, 2026 at 9:21 AM UTCinvestigating

      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. October 23, 2026 at 11:25 AM UTCresolved

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

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

    Started October 22, 2026 at 7:17 PM UTC · 5h 8m

    OutageMajor incident
    Affected components
    740 - San Luis Obispo, CA728 - Fresno, CA730 - Los Angeles, CA
    1. October 22, 2026 at 7:17 PM UTCinvestigating

      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. October 22, 2026 at 10:12 PM UTCmonitoring

      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. October 23, 2026 at 12:25 AM UTCresolved

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

    Inbound Messaging - Verizon & T-Mobile

    Started October 22, 2026 at 6:31 PM UTC · 2h 9m

    IssuesMinor incident
    Affected components
    SMS Messaging (SMPP)MMS Messaging (MM4)
    1. October 22, 2026 at 6:31 PM UTCinvestigating

      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. October 22, 2026 at 8:40 PM UTCresolved

      This incident has been resolved.

    3. October 23, 2026 at 10:39 AM UTCpostmortem

      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.

    Voice Authentication Incident - Pindrop

    Started October 22, 2026 at 3:14 PM UTC · 1h 39m

    IssuesMinor incident
    Affected components
    Inbound Calling (SIP) - United States
    1. October 22, 2026 at 3:14 PM UTCidentified

      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. October 22, 2026 at 4:53 PM UTCresolved

      This incident has been resolved.

    3. October 23, 2026 at 8:36 AM UTCpostmortem

      Between 14:00 UTC and 16:05 UTC on October 22, 2026, inbound Voice Authentication services experienced inbound call failures. 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.

    Bandwidth Local Market Impairment - 328 - Dayton, OH

    Started October 22, 2026 at 3:02 PM UTC · 8h 59m

    OutageCritical incident
    Affected components
    328 - Dayton, OH
    1. October 22, 2026 at 3:02 PM UTCinvestigating

      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. October 22, 2026 at 7:48 PM UTCidentified

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

    3. October 23, 2026 at 12:01 AM UTCresolved

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

    Off-Net Port Activations

    Started October 22, 2026 at 2:57 PM UTC · 6h 51m

    OutageMajor incident
    Affected components
    Number Porting
    1. October 22, 2026 at 2:57 PM UTCidentified

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

    2. October 22, 2026 at 4:18 PM UTCmonitoring

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

    3. October 22, 2026 at 9:48 PM UTCresolved

      This incident has been resolved.

    4. October 23, 2026 at 9:34 AM UTCpostmortem

      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.

    US Voice Traffic

    Started October 22, 2026 at 11:16 AM UTC · 0m

    OutageMajor incident
    1. October 22, 2026 at 11:18 AM UTCresolved

      For a brief period of time, some customers may have experienced a reduction of inbound voice traffic. This was due to an off-network condition of a carrier.

    2. October 22, 2026 at 11:51 AM UTCpostmortem

      Between 04:10 UTC and 08:03 UTC on October 22, 2026, US Voice Traffic experienced a reduction of inbound voice traffic due to an off-network condition of a carrier. 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.

    Bandwidth Local Market Impairment - 521 - Jefferson City, MO

    Started October 22, 2026 at 8:35 AM UTC · 2h 47m

    Pending
    Affected components
    521 - Jefferson City, MO
    1. October 22, 2026 at 8:35 AM UTCinvestigating

      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. October 22, 2026 at 10:36 AM UTCmonitoring

      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. October 22, 2026 at 11:21 AM UTCresolved

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

    Bandwidth Local Market Impairment - 973 - Palm Springs, CA

    Started October 22, 2026 at 7:04 AM UTC · 16h 58m

    OutageCritical incident
    Affected components
    973 - Palm Springs, CA
    1. October 22, 2026 at 9:43 AM UTCinvestigating

      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. October 22, 2026 at 7:51 PM UTCidentified

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

    3. October 23, 2026 at 12:02 AM UTCresolved

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

    Bandwidth Local Market Impairment - 234 - Pittsburgh, PA

    Started October 22, 2026 at 6:07 AM UTC · 4h 36m

    Pending
    Affected components
    234 - Pittsburgh, PA
    1. October 22, 2026 at 6:07 AM UTCidentified

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

    2. October 22, 2026 at 9:23 AM UTCmonitoring

      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. October 22, 2026 at 10:43 AM UTCresolved

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

    Outbound MMS Messaging - AT&T

    Started October 21, 2026 at 9:45 PM UTC · 5h 9m

    IssuesMinor incident
    Affected components
    MMS Messaging (MM4)
    1. October 21, 2026 at 9:45 PM UTCinvestigating

      Teams are investigating an incident impacting outbound MMS messages towards AT&T destinations. These messages may fail unexpectedly.

    2. October 22, 2026 at 1:41 AM UTCmonitoring

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

    3. October 22, 2026 at 2:54 AM UTCresolved

      This incident has been resolved.

    4. October 22, 2026 at 8:38 AM UTCpostmortem

      Bandwidth has concluded its investigation of this issue and determined that between 18:58 UTC on October 21, 2026 and 01:02 UTC on October 22, 2026, outbound MMS messages towards AT&T destinations 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.

    Toll-Free Port Activation Incident

    Started October 21, 2026 at 9:36 PM UTC · 22h 3m

    OutageMajor incident
    Affected components
    Number Porting
    1. October 21, 2026 at 9:36 PM UTCinvestigating

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

    2. October 22, 2026 at 7:40 PM UTCresolved

      This incident has been resolved.

    Bandwidth Local Market Impairment - 951 - Rocky Mount, NC

    Started October 21, 2026 at 9:33 PM UTC · 4d 1h

    OutageCritical incident
    Affected components
    951 - Rocky Mount, NC
    1. October 22, 2026 at 2:56 AM UTCinvestigating

      We are continuing to investigate this issue.

    2. October 22, 2026 at 8:12 AM UTCinvestigating

      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. October 22, 2026 at 12:12 PM UTCinvestigating

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

    4. October 24, 2026 at 8:28 PM UTCidentified

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

    5. October 25, 2026 at 7:47 PM UTCidentified

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

    6. October 25, 2026 at 9:54 PM UTCmonitoring

      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. October 25, 2026 at 11:00 PM UTCresolved

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

    Bandwidth Local Market Impairment - 548 - Wichita Falls, TX

    Started October 21, 2026 at 3:17 PM UTC · 3h 25m

    Pending
    Affected components
    548 - Wichita Falls, TX
    1. October 21, 2026 at 3:17 PM UTCinvestigating

      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. October 21, 2026 at 6:42 PM UTCmonitoring

      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. October 21, 2026 at 6:43 PM UTCresolved

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

    Bandwidth Local Market Impairment - 326 - Toledo, OH

    Started October 21, 2026 at 3:12 PM UTC · 1d 17h

    Pending
    Affected components
    326 - Toledo, OH
    1. October 21, 2026 at 3:12 PM UTCinvestigating

      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. October 22, 2026 at 9:14 AM UTCidentified

      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. October 23, 2026 at 3:46 AM UTCidentified

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

    4. October 23, 2026 at 8:57 AM UTCresolved

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

    Bandwidth Local Market Impairment - 140 - Buffalo, NY

    Started October 20, 2026 at 11:43 PM UTC · 9h 49m

    Pending
    Affected components
    140 - Buffalo, NY
    1. October 20, 2026 at 11:43 PM UTCinvestigating

      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. October 21, 2026 at 9:32 AM UTCresolved

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

    Bandwidth Local Market Impairment - 230 - Altoona, PA

    Started October 20, 2026 at 10:57 PM UTC · 21h 17m

    Pending
    Affected components
    230 - Altoona, PA
    1. October 20, 2026 at 10:57 PM UTCinvestigating

      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. October 21, 2026 at 1:07 AM UTCidentified

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

    3. October 21, 2026 at 6:48 PM UTCmonitoring

      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. October 21, 2026 at 8:14 PM UTCresolved

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

    Japan outbound calling incident

    Started October 20, 2026 at 10:29 PM UTC · 15h 12m

    OutageMajor incident
    Affected components
    Outbound Calling- Japan
    1. October 20, 2026 at 10:29 PM UTCinvestigating

      Bandwidth teams are investigating outbound Japan based calls that may not complete as expected at this time.

    2. October 21, 2026 at 9:26 AM UTCmonitoring

      Teams are observing expected outbound, calling behaviors and will monitor for prolonged stability.

    3. October 21, 2026 at 1:41 PM UTCresolved

      This incident has been resolved.

    4. October 22, 2026 at 7:23 AM UTCpostmortem

      Between 16:09 UTC and 23:12 UTC on October 20th, 2026, outbound Japan based calls may not have completed as expected. 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/17734056-20261020-bwi-voice-japan-outbound-calls-failing.](https://www.bandwidth.com/support/en/articles/17734056-20261020-bwi-voice-japan-outbound-calls-failing.) 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.