Bandwidth

Affected: 548 - Wichita Falls, TX

1. investigating 2026-10-21 15:28 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.

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 548 - Wichita Falls, TX

1. investigating 2026-10-21 15:17 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.

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 326 - Toledo, OH

1. investigating 2026-10-21 15:12 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 2026-10-21 16:55 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 140 - Buffalo, NY

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 23:43 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 2026-10-21 09:32 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 230 - Altoona, PA

1. investigating 2026-10-20 22:57 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 2026-10-21 01:07 UTC

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

3. monitoring 2026-10-21 02:33 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 2026-10-21 06:28 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 2026-10-21 10:01 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 2026-10-21 14:05 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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Outbound Calling- Japan

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-20 22:29 UTC

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

2. monitoring 2026-10-21 00:21 UTC

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

3. monitoring 2026-10-21 09:26 UTC

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

4. resolved 2026-10-21 13:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 924 - Erie, PA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 22:05 UTC

   We are currently investigating this issue.

2. identified 2026-10-21 02:52 UTC

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

3. monitoring 2026-10-21 03:59 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 2026-10-21 09:26 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-10-21 13:55 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 2026-10-21 14:46 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 246 - Culpeper, VA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-20 22:03 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 2026-10-21 02:56 UTC

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

3. monitoring 2026-10-21 04:08 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 2026-10-21 09:25 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 2026-10-21 13:58 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 2026-10-21 17:37 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 927 - Harrisonburg, VA

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 22:00 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 2026-10-21 02:49 UTC

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

3. monitoring 2026-10-21 03:49 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 2026-10-21 09:26 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2026-10-21 13:51 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-10-21 13:51 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Toll-Free calling - Outbound (SIP) - United States

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 21:10 UTC

   Bandwidth teams are investigating an outbound, toll-free calling incident where some outbound calls are receiving unexpected 404 SIP response codes

2. monitoring 2026-10-20 21:34 UTC

   Teams are observing expected toll-free traffic transmission across the Bandwidth network. We will monitor for prolonged stability.

3. resolved 2026-10-20 23:04 UTC

   This incident has been resolved.

4. postmortem 2026-10-21 10:31 UTC

   Between 19:48 UTC on October 15th and 22:55 UTC on October 20th, some outbound toll-free calls received unexpected 404 SIP response codes. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 632 - Des Moines, IA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 18:01 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 2026-10-20 18:49 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 2026-10-20 21:10 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: International A2P Platform (SMPP), International A2P Platform (HTTP)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 16:22 UTC

   Bandwidth teams are investigating an incident impacting Inbound and Outbound SMS messaging to Australia based destinations. Outbound messages may not result delivery receipts, inbound messages may not deliver as expected.

2. identified 2026-10-20 17:03 UTC

   Teams have identified the source of this incident as an off-network vendor condition. Teams are working with the impacted vendor to restore expected messaging behaviors.

3. monitoring 2026-10-20 18:45 UTC

   Teams are observing expected messaging behavior and are monitoring for stability.

4. resolved 2026-10-20 20:02 UTC

   This incident has been resolved.

5. postmortem 2026-10-21 09:20 UTC

   Between 14:45 UTC and 17:16 UTC on October 20, 2026, Inbound and Outbound SMS messaging to Australia based destinations experienced missing delivery receipts and failed or timed-out messages. Bandwidth is continuing to investigate this issue to identify all actions necessary to...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 951 - Rocky Mount, NC

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:50 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 2026-10-20 07:59 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 2026-10-20 08:01 UTC

   We are continuing to monitor for any further issues.

4. monitoring 2026-10-20 08:03 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-10-20 10:09 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 220 - Pleasantville, NJ

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 06:46 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 2026-10-20 07:41 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 2026-10-20 08:58 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 246 - Culpeper, VA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 01:21 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 2026-10-20 04:55 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 2026-10-20 07:44 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 2026-10-20 11:32 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 2026-10-20 13:50 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 2026-10-20 17:29 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 924 - Erie, PA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 01:12 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 2026-10-20 04:34 UTC

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

3. identified 2026-10-20 08:04 UTC

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

4. monitoring 2026-10-20 08:05 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 2026-10-20 10:06 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 230 - Altoona, PA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 01:11 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 2026-10-20 04:33 UTC

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

3. monitoring 2026-10-20 07:07 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 2026-10-20 09:15 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 2026-10-20 13:15 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 2026-10-20 17:14 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 927 - Harrisonburg, VA

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-20 01:08 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 2026-10-20 04:56 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 2026-10-20 08:02 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 2026-10-20 08:02 UTC

   We are continuing to monitor for any further issues.

5. resolved 2026-10-20 11:38 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: MMS Messaging (MM4)

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 23:12 UTC

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

2. monitoring 2026-10-20 04:39 UTC

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

3. resolved 2026-10-20 04:52 UTC

   This incident has been resolved.

4. postmortem 2026-10-20 12:58 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: SMS Messaging (SMPP), MMS Messaging (MM4)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-19 21:38 UTC

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

2. monitoring 2026-10-20 03:46 UTC

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

3. resolved 2026-10-20 05:36 UTC

   This incident has been resolved.

4. postmortem 2026-10-20 11:03 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Number Porting

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-19 13:06 UTC

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

2. identified 2026-10-19 18:39 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 2026-10-19 20:06 UTC

   This incident has been resolved.

4. postmortem 2026-10-20 12:49 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 542 - Midland, TX

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-18 08:06 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 2026-10-18 10:59 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 2026-10-18 15:34 UTC

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

4. identified 2026-10-18 18:55 UTC

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

5. monitoring 2026-10-18 22:01 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 2026-10-19 02:12 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 2026-10-19 06:12 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 2026-10-19 06:37 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: New Number Ordering

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-10-18 06:04 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 2026-10-18 15:27 UTC

   This incident has been resolved.

3. postmortem 2026-10-19 09:19 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: MMS Messaging (MM4)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-16 21:31 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 2026-10-16 22:55 UTC

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

3. resolved 2026-10-17 00:07 UTC

   This incident has been resolved.

4. postmortem 2026-10-19 08:50 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 635 - Cedar Rapids, IA

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 08:41 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 2026-10-16 11:52 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 644 - Omaha, NE

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 07:39 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 2026-10-16 10:37 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 646 - Grand Island, NE

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-16 07:32 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 2026-10-16 11:02 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: SMS Messaging (SMPP), MMS Messaging (MM4)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 21:39 UTC

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

2. identified 2026-10-15 23:17 UTC

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

3. monitoring 2026-10-16 02:13 UTC

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

4. resolved 2026-10-16 03:23 UTC

   This incident has been resolved.

5. postmortem 2026-10-16 08:59 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 521 - Jefferson City, MO

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-15 05:21 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 2026-10-15 07:19 UTC

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

3. identified 2026-10-15 11:08 UTC

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

4. monitoring 2026-10-15 12:45 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 2026-10-15 12:46 UTC

   We are continuing to monitor for any further issues.

6. resolved 2026-10-15 16:43 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: MMS Messaging (MM4)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 21:16 UTC

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

2. monitoring 2026-10-15 02:32 UTC

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

3. resolved 2026-10-15 03:45 UTC

   This incident has been resolved.

4. postmortem 2026-10-15 14:32 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 654 - Cheyenne, WY

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 15:32 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 2026-10-14 19:32 UTC

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

3. identified 2026-10-14 23:31 UTC

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

4. identified 2026-10-15 03:26 UTC

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

5. identified 2026-10-15 07:03 UTC

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

6. monitoring 2026-10-15 08:57 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 2026-10-15 12:20 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-14 13:41 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 2026-10-15 09:38 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 538 - Tulsa, OK

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 10:35 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 2026-10-14 14:53 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 2026-10-14 19:28 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 2026-10-14 22:15 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 536 - Oklahoma City, OK

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 05:26 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 2026-10-14 06:07 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 2026-10-14 09:47 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 977 - Macomb, IL

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-14 05:15 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 2026-10-14 07:56 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 2026-10-14 09:49 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 2026-10-14 12:01 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: MMS Messaging (MM4)

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-13 21:19 UTC

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

2. monitoring 2026-10-14 00:55 UTC

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

3. resolved 2026-10-14 01:59 UTC

   This incident has been resolved.

4. postmortem 2026-10-14 08:09 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...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 668 - Tucson, AZ

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-11 21:22 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 2026-10-12 01:07 UTC

   We are continuing to investigate this issue.

3. resolved 2026-10-12 17:25 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 956 - Johnson City, TN

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-11 06:39 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 2026-10-11 07:39 UTC

   We are continuing to investigate this issue.

3. resolved 2026-10-11 09:41 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 554 - Longview, TX

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 21:02 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 2026-10-10 01:13 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 2026-10-10 04:59 UTC

   We are continuing to investigate this issue.

4. identified 2026-10-10 08:58 UTC

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

5. identified 2026-10-10 10:50 UTC

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

6. identified 2026-10-10 11:43 UTC

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

7. monitoring 2026-10-10 14:06 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 2026-10-10 14:07 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 122 - Manchester, NH

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-10-09 08:45 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 2026-10-09 09:43 UTC

   We are continuing to investigate this issue.

3. investigating 2026-10-09 11:45 UTC

   We are continuing to investigate this issue.

4. investigating 2026-10-09 14:53 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 2026-10-09 15:53 UTC

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

6. identified 2026-10-09 19:56 UTC

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

7. identified 2026-10-10 00:11 UTC

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

8. identified 2026-10-10 04:02 UTC

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

9. identified 2026-10-10 07:59 UTC

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

10. identified 2026-10-10 11:49 UTC

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

11. identified 2026-10-10 15:46 UTC

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

12. identified 2026-10-10 19:54 UTC

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

13. identified 2026-10-10 19:54 UTC

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

14. identified 2026-10-11 01:03 UTC

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

15. identified 2026-10-11 04:45 UTC

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

16. identified 2026-10-11 08:42 UTC

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

17. identified 2026-10-11 13:52 UTC

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

18. monitoring 2026-10-11 18:40 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 2026-10-11 21:33 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 920 - New Haven, CT

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 05:39 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 2026-10-09 06:48 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 2026-10-09 08:47 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 977 - Macomb, IL

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 01:02 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 2026-10-09 02:45 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 2026-10-09 04:22 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 328 - Dayton, OH

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-09 00:18 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 2026-10-09 00:19 UTC

   We are continuing to investigate this issue.

3. resolved 2026-10-09 02:50 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Toll-Free SMS - Outbound

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-08 21:04 UTC

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

2. identified 2026-10-08 23:08 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 2026-10-09 02:41 UTC

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

4. resolved 2026-10-09 04:47 UTC

   This incident has been resolved.

5. postmortem 2026-10-09 11:43 UTC

   Bandwidth has concluded its investigation of this issue and determined that between 13:00 UTC on October 8, 2026 and 01:58 UTC on October 9, 2026, toll-free SMS delivery receipts for messages to Verizon were delayed. Due to the limited scope of impact, Bandwidth is closing this...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: SMS Messaging (SMPP), MMS Messaging (MM4)

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-07 21:51 UTC

   Bandwidth teams are investigating an incident impacting outbound 10DLC messages towards AT&T. These messages may incorrectly fail to deliver due to an off network condition labeling said messages as fraud.

2. monitoring 2026-10-08 02:18 UTC

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

3. resolved 2026-10-08 03:05 UTC

   This incident has been resolved.

4. postmortem 2026-10-08 09:35 UTC

   Between 20:20 UTC on October 7, 2026 and 20:40 UTC on October 8, 2026, outbound 10DLC SMS and MMS messages towards AT&T destinations incorrectly failed to deliver due to an off-network condition labeling the messages as fraud. Bandwidth is continuing to investigate this issue to...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Phone Number Lookup API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 20:07 UTC

   Bandwidth teams are investigating an incident impacting Telephone Number Lookup tool where results are delayed or failing to complete as expected.

2. investigating 2026-10-07 21:28 UTC

   This incident is resolved. Teams are observing customer TN lookup requests process in real-time without delays or time-outs.

3. resolved 2026-10-07 21:30 UTC

   This incident has been resolved.

4. postmortem 2026-10-09 10:10 UTC

   Between 17:35 UTC and 21:54 UTC on October 7, 2026, TN Lookup experienced request slowness and timeouts affecting all customers. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2026-10-07 19:32 UTC

   For a short period of time, some 10DLC SMS and MMS messages towards AT&T destinations incorrectly received a rejection related to Spam Filtering due to an off-network condition. The incident has been resolved and we are observing expected network behavior.

2. postmortem 2026-10-08 09:32 UTC

   Between 17:30 UTC and 18:15 UTC on October 7, 2026, some 10DLC SMS and MMS messages towards AT&T destinations incorrectly received a rejection related to Spam Filtering due to an off-network condition. Bandwidth is continuing to investigate this issue to identify all actions...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: Inbound Calling (SIP) - United States, REST APIs - HTTP Voice - United States, REST APIs - SIP Voice - United States, BXML - United States

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 19:20 UTC

   Bandwidth teams are investigating an Inbound Calling incident where a subset of inbound calls from the Lumen network are failing to connect to the Bandwidth network. Teams and this partner are working to restore expected calling services.

2. identified 2026-10-07 20:55 UTC

   Teams have identified the off network condition and are working to restore expected calling behaviors.

3. monitoring 2026-10-07 22:52 UTC

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

4. resolved 2026-10-08 00:23 UTC

   This incident has been resolved.

5. postmortem 2026-10-08 10:54 UTC

   Bandwidth has concluded its investigation of this issue and determined that between 15:09 UTC and 21:48 UTC on October 7, 2026, a subset of inbound voice calls experienced call drops or degraded audio quality. Due to the limited scope of impact, Bandwidth is closing this...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2026-10-07 11:48 UTC

   For a brief period of time, some inbound MMS messages may not have been delivered as expected due to of off-network vendor condition. Teams are seeing expected delivery at this and consider this incident resolved.

2. postmortem 2026-10-07 12:13 UTC

   Between 08:26 UTC and 08:55 UTC on October 7th, 2026, inbound MMS messaging was not delivered as expected for a subset of Bandwidth customers. Bandwidth has concluded its investigation of this issue and details can be found in the following Incident Report:...

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 932 - Bluefield, WV

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 06:33 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 2026-10-07 07:01 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 2026-10-07 10:29 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 256 - Clarksburg, WV

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 05:59 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 2026-10-07 10:09 UTC

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

3. identified 2026-10-07 13:48 UTC

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

4. monitoring 2026-10-07 13:58 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 2026-10-07 16:19 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 937 - Richmond, IN

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-07 04:25 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 2026-10-07 05:32 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 2026-10-07 09:16 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.

Affected: 548 - Wichita Falls, TX

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-06 17:29 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 2026-10-06 19:51 UTC

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

3. identified 2026-10-07 00:02 UTC

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

4. identified 2026-10-07 04:00 UTC

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

5. identified 2026-10-07 08:43 UTC

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

6. identified 2026-10-07 11:47 UTC

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

7. identified 2026-10-07 15:40 UTC

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

8. identified 2026-10-07 19:46 UTC

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

9. identified 2026-10-08 00:01 UTC

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

10. identified 2026-10-08 04:02 UTC

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

11. identified 2026-10-08 07:49 UTC

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

12. identified 2026-10-08 13:28 UTC

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

13. identified 2026-10-08 17:32 UTC

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

14. identified 2026-10-08 21:02 UTC

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

15. identified 2026-10-09 01:03 UTC

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

16. monitoring 2026-10-09 08:42 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.

17. resolved 2026-10-09 10:41 UTC

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

Excerpts are shortened. Read the full incident on Bandwidth's status page.