Bandwidth

Affected: 973 - Palm Springs, CA

1. investigating 2026-10-22 07:04 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: 234 - Pittsburgh, PA

1. identified 2026-10-22 06:07 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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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

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

2. monitoring 2026-10-22 01:41 UTC

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

3. resolved 2026-10-22 02:54 UTC

   This incident has been resolved.

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

Affected: Number Porting

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

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

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

Affected: 951 - Rocky Mount, NC

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

   We are continuing to investigate this issue.

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

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

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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.

2. monitoring 2026-10-21 18: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

3. resolved 2026-10-21 18: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: 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.

3. identified 2026-10-21 20:51 UTC

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

4. identified 2026-10-22 00:56 UTC

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

5. identified 2026-10-22 05:05 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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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

7. monitoring 2026-10-21 18: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

8. resolved 2026-10-21 20: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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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: 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-06 19:45 UTC

   This incident has been resolved.

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

Affected: 548 - Wichita Falls, 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-06 22: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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-06 21:33 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-10-06 12:04 UTC

   This incident has been resolved.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-06 12:21 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: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-05 22:57 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-04 20: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-04 20:28 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: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-03 20:00 UTC

   For a brief period of time calls transversing across our Brussels Datacenter may have failed to complete as expected. We are currently observing expected network behavior and consider this incident 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-03 11: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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-02 03:30 UTC

   During a scheduled maintenance window, inbound calls for some customers did not deliver as expected. These calls failed to complete as expected during the impact window. We have since observed expected network behavior, and consider this incident resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-02 13:27 UTC

   This incident has been 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-10-03 01:18 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-10-01 20:00 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-10-02 06:39 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-30 17:36 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-30 11:57 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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-30 02:31 UTC

   This incident has been 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: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-30 13:52 UTC

   Final: Our carrier has completed all necessary repairs (equipment failure) and Bandwidth can confirm all services are restored. This incident is being resolved. Start Time: 09/29/2026 21:05 ET Stop Time: 09/30/2026 09:43 ET

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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-30 12: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-27 08:57 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-25 12:13 UTC

   For a period of time the Bandwidth network was incorrectly receiving MMS messages to Bandwidth powered numbers. This was identified as an off-network event and isolated to a specific industry provider. This incident has been resolved and we are observing expected MMS traffic...

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-25 10:45 UTC

   For a brief period of time the Bandwidth Global portal failed to properly display pricing information. Teams have resolved this incident.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-25 11:13 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-26 02:28 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-25 00: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.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Network or DNS. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-24 12:59 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-23 20:02 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-23 12:54 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-23 10: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.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-23 09:35 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-23 04:29 UTC

   Bandwidth has observed continued stability to and is resolving this incident.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-23 10:04 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-22 12:13 UTC

   This incident has been 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: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 19: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 12:42 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 22:17 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-22 01: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 01: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-22 14: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-21 22: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-22 20:34 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-21 17:56 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-19 12:11 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.

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

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-18 19:32 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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-17 14:31 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-16 10: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.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: Hardware or facility. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-16 15: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-16 17:12 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 20:45 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-15 03:58 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-16 00:09 UTC

   This incident has been resolved.

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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-14 08:38 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-13 21:55 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-17 19: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-12 13:34 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 zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-11 15:40 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-11 08:59 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-11 15:40 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-10 10: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

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

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-09 19:35 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-09 20:26 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 18:04 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-08 13:01 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-07 22: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.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-07 10:03 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 10:57 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-07 13:33 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-05 01:18 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-04 01:09 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.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-03 22:18 UTC

   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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-04 12:28 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: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-03 11:55 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-09-04 02: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.

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-04 12: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.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-03 17:54 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-02 11:56 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 17:29 UTC

   This incident has been resolved.

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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-09-01 11:11 UTC

   Final: Our carrier has completed all necessary repairs (SSL certificate update) and Bandwidth can confirm all services are restored. This incident is being resolved. Start Time: 2026-09-01 07:11:00 UTC End Time: 2026-09-01 08:55:00 UTC

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-09-01 04:29 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-31 21:13 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-31 15:46 UTC

   For a brief period of time, some Toll Free port orders were delayed in provisioning due to network condition with a industry partner. At this time provisioning activities are processing as expected.

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 deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-28 15:54 UTC

   For a brief period of time, a sub-set of Toll Free Origination voice traffic was unable to complete due to an off-network incident. This incident has been resolved and we are observing expected network behavior.

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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-26 18:23 UTC

   For a brief period of time a subset of customer traffic, with a specific account settings were until not route traffic as expected. Teams have resolved this incident and are observing expected traffic behaviors.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-25 15:01 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-24 20:32 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-21 15:09 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 21:39 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-20 13:13 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-19 11:16 UTC

   For a brief period of time, number orders in the Bandwidth App were delayed or failed to complete. This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-18 14:08 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-17 23:24 UTC

   This incident has been resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: A human mistake during operations. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-17 10:04 UTC

   Bandwidth teams resolved an incident where RCS Agents were deployed to the incorrect region resulting in potential traffic issues.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-16 10:59 UTC

   For a brief period of time new telephone number orders were delayed in processing. At this time, orders are processing as expected, and we consider this incident resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-14 14:21 UTC

   For a brief period of time, a sub-set of traffic transiting over porting of our ATL datacenter may have unexpectedly failed to complete as intended. At this time this portion of traffic has restored and our network is operating as expected.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-14 18:15 UTC

   This incident has been resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-08-14 12:09 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-11 20:10 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-11 18:39 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-12 04:30 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-08-07 16:20 UTC

   This incident has been resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-05 06:50 UTC

   This incident has been resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 21:48 UTC

   For a brief period of a time, a small subset of voice traffic transversing our DFW datacenter experienced unexpected call failures. This incident is now resolved and we are observing expected network behavior.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 12:39 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-08-03 10:50 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 23:02 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-31 15:05 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-30 14:00 UTC

   Customers experienced delays in receiving Delivery Receipts (DLRs) for messaging traffic. This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-28 05:27 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 15:40 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-27 16:52 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-23 08:30 UTC

   For a brief period of time, the Bandwidth App may have been unresponsive to users. At this time the App is stable and we consider this incident resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-22 23:23 UTC

   For a brief period of time, a small subset of Programable Voice traffic experienced traffic disruption. Traffic has since stabilized and we consider this incident resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 02:36 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-22 00:07 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-21 18:10 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-20 12:53 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-17 19:49 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-15 15:23 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

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

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. resolved 2026-07-10 02:18 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-09 04:09 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-07 21:56 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-06 15:24 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-02 15:45 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-07-01 18:41 UTC

   This incident has been 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: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-07-01 03:26 UTC

   This incident has been 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 deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-30 14:48 UTC

   This incident has been resolved.

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

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 deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. resolved 2026-06-30 12:50 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 16:10 UTC

   This incident has been resolved.

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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-25 08:37 UTC

   This incident has been resolved.

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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. resolved 2026-06-24 21:28 UTC

   This incident has been resolved.

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

1. resolved 2026-06-23 13:00 UTC

   For a brief period if time a small subset of traffic transferring our ATL datacenter reviewed unexpected 404 and 503 errors. Teams have resolved these errors, and consider this incident resolved.

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

1. resolved 2026-06-22 23:08 UTC

   This incident has been resolved.

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

1. resolved 2026-06-20 13:19 UTC

   This incident has been resolved.

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

1. resolved 2026-06-20 00:51 UTC

   This incident has been resolved.

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

1. resolved 2026-06-19 18:37 UTC

   This incident has been resolved.

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

1. resolved 2026-06-17 17:34 UTC

   This incident has been resolved.

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

1. resolved 2026-06-12 11:23 UTC

   This incident has been resolved.

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

1. resolved 2026-06-11 16:31 UTC

   This incident has been resolved.

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

1. resolved 2026-06-10 10:45 UTC

   For a brief period of time users of Bandwidths' Global Portal may have experienced degraded portal behavior. This has since been resoled and the portal remains stable.

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

1. resolved 2026-06-10 10:30 UTC

   During this incident some Toll-Free & 10DLC provisioning requests may have encountered unexpected delays or failures. This incident has been resolved and expected Toll-Free & 10DLC provisioning requests are processing as expected without delay.

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

1. resolved 2026-06-10 08:00 UTC

   For a brief period of time customers may have experienced Inbound Outbound call failures for New Zealand based numbers and/or destinations. Teams resolved the incident and are observing expected calling behavior.

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

1. resolved 2026-06-09 18:00 UTC

   For a brief period of time, some inbound MMS messages failed to deliver to Bandwidth destinations as expected. Teams resolved the incident and observed expected MMS delivery during prolonged monitoring.

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

1. resolved 2026-06-10 11:40 UTC

   This incident has been resolved.

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

1. resolved 2026-06-08 11:44 UTC

   This incident has been resolved.

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

1. resolved 2026-06-05 20:11 UTC

   This incident has been resolved.

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

1. resolved 2026-06-04 17:34 UTC

   This incident has been resolved.

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

1. resolved 2026-06-02 18:07 UTC

   This incident has been resolved.

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

1. resolved 2026-05-30 11:19 UTC

   This incident has been resolved.

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

1. resolved 2026-05-28 19:08 UTC

   For a brief period of of time, some inbound calls from the Fibernetics network were not reaching the Bandwidth network. Teams have resolved the incident and are observing expected inbound traffic. We consider this incident resolved.

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

1. resolved 2026-05-29 22:00 UTC

   This incident has been resolved.

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

1. resolved 2026-05-26 19:41 UTC

   Customers may have experienced inbound and outbound call failures when routing through our DFW Datacenter. This incident has been resolved after prolonged stability was observed.

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

1. resolved 2026-05-25 05:43 UTC

   This incident has been resolved.

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

1. resolved 2026-05-21 23:27 UTC

   For a brief period of time an isolated event resulted in a small subset of 10DLC Messages to fail to deliver as expected. Traffic has since recovered and we consider this incident resolved.

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

1. resolved 2026-05-20 10:59 UTC

   For a brief period of time, some outbound Norway based calls may have failed to complete as expected. Traffic patterns have normalized and we consider this incident resolved.

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

1. resolved 2026-05-21 20:34 UTC

   This incident has been resolved.

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

1. resolved 2026-05-19 19:01 UTC

   This incident has been resolved.

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

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

   For a brief period of time, South Africa voice traffic experienced intermittent inbound and outbound call instability resulting in calls falling to complete as expected. This incident has since resolved and we are observing expected network behavior.

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

1. resolved 2026-05-20 10:48 UTC

   This incident has been resolved.

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

1. resolved 2026-05-15 19:46 UTC

   This incident has been resolved.

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

1. resolved 2026-05-14 20:42 UTC

   This incident has been resolved.

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

1. resolved 2026-05-14 04:36 UTC

   This incident has been resolved.

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

1. resolved 2026-05-12 22:22 UTC

   This incident has been resolved.

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

1. resolved 2026-05-14 22:23 UTC

   This incident has been resolved.

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

1. resolved 2026-05-12 13:35 UTC

   This incident has been resolved.

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

1. resolved 2026-05-08 22:10 UTC

   This incident has been resolved.

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

1. resolved 2026-05-07 13:45 UTC

   This incident has been resolved.

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

1. resolved 2026-05-06 17:47 UTC

   This incident has been resolved.

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

1. resolved 2026-05-06 21:19 UTC

   This incident has been resolved.

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

1. resolved 2026-04-30 10:00 UTC

   During this incident; inbound calls to German based numbers which were ported to the Bandwidth Universal Platform were failing to complete as expected. This incident has recovered and calls are processing as expected. Teams will monitor ensuring stability, however we consider...

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

1. resolved 2026-04-29 00:07 UTC

   This incident has been resolved.

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

1. resolved 2026-04-28 12:52 UTC

   Final: There may have been failed calls for international toll-free service during this period but all services are now restored. Start Time: 2026-04-28 12:01:37 PM UTC Stop Time: 2026-04-28 12:40:04 PM UTC

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

1. resolved 2026-04-30 15:57 UTC

   This incident has been resolved.

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

1. resolved 2026-04-27 15:52 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 19:20 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 11:48 UTC

   This incident has been resolved.

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

1. resolved 2026-04-23 05:29 UTC

   For a brief period of time, some traffic transversing our ATL Data center may have encountered unexpected failures. Teams are observing expected network behavior and connectivity- resulting in this incident being resolved.

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

1. resolved 2026-04-23 14:03 UTC

   This incident has been resolved.

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

1. resolved 2026-04-22 14:44 UTC

   This incident has been resolved.

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

1. resolved 2026-04-22 07:43 UTC

   For a brief period of time customers may have experienced a delay in outbound messaging and associated reports. Teams are observing expected network behavior and consider this incident resolved.

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

1. resolved 2026-04-22 02:28 UTC

   This incident has been resolved.

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

1. resolved 2026-04-20 08:52 UTC

   Outage for Lata 668 (Tucson, AZ) is now resolved.

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

1. resolved 2026-04-18 00:30 UTC

   For a brief period of time, SMS and MMS messages with AT&T destinations were either delayed in delivery or failed to deliver as expected. Teams are observing expected network behavior at this time and consider this incident resolved.

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

1. resolved 2026-04-17 01:04 UTC

   This incident has been resolved.

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

1. resolved 2026-04-15 21:46 UTC

   For a brief period of time users of the Bandwidth App may have experienced portal latency or general unavailability of the Bandwidth App. Teams are observing expected portal behavior and consider this incident resolved.

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

1. resolved 2026-04-16 01:28 UTC

   This incident has been resolved.

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

1. resolved 2026-04-15 14:52 UTC

   This incident has been resolved.

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

1. resolved 2026-04-15 08:38 UTC

   Bandwidth has observed continued stability in SMS delivery to France and is resolving this incident.

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

1. resolved 2026-04-14 21:30 UTC

   For a brief period of time the Bandwidth App may have been unavailable for some users. We consider this incident resolved.

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

1. resolved 2026-04-14 13:40 UTC

   This incident has been resolved.

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

1. resolved 2026-04-13 15:55 UTC

   This incident has been resolved.

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

1. resolved 2026-04-12 04:40 UTC

   This incident has been resolved.

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

1. resolved 2026-04-09 12:57 UTC

   This incident has been resolved.

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

1. resolved 2026-04-09 11:14 UTC

   This incident has been resolved.

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

1. resolved 2026-04-09 11:47 UTC

   This incident has been resolved.

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

1. resolved 2026-04-08 15:36 UTC

   This incident has been resolved.

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

1. resolved 2026-04-07 21:41 UTC

   This incident has been resolved.

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

1. resolved 2026-04-07 21:07 UTC

   This incident has been resolved. Impacted telephone numbers have been restored to their campaigns.

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

1. resolved 2026-04-06 22:50 UTC

   This incident has been resolved.

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

1. resolved 2026-04-06 18:09 UTC

   This incident has been resolved.

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

1. resolved 2026-04-03 21:25 UTC

   This incident has been resolved.

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

1. resolved 2026-04-03 21:27 UTC

   This incident has been resolved.

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

1. resolved 2026-04-03 14:29 UTC

   This incident has been resolved.

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

1. resolved 2026-03-31 20:35 UTC

   This incident has been resolved.

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

1. resolved 2026-03-30 19:30 UTC

   For a brief period of time, Bulk TN Lookup Queries were not completing as expected. At this time, we are observing expected App behavior.

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

1. resolved 2026-03-30 14:15 UTC

   For a brief period of time, some users of the Bandwidth App may have experienced unexpected errors. Teams are observing expected portal behavior.

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

1. resolved 2026-03-30 14:17 UTC

   This incident has been resolved.

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

1. resolved 2026-03-27 22:17 UTC

   This incident has been resolved.

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

1. resolved 2026-03-27 03:07 UTC

   This incident has been resolved.

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

1. resolved 2026-03-24 19:08 UTC

   This incident has been resolved.

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

1. resolved 2026-03-23 21:37 UTC

   This incident has been resolved.

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

1. resolved 2026-03-18 05:30 UTC

   For a brief period of time, a segment of calls transversing a specific node in our JFK Datacenter encountered unexpected failures. We are observing expected network behavior, and consider this incident resolved.

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

1. resolved 2026-03-13 18:39 UTC

   For a brief period of time, due to an industry incident, inbound SMS messages were delayed in delivery to their Bandwidth destination. Teams are observing, expected network behaviors and consider this incident.

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

1. resolved 2026-03-03 16:33 UTC

   This incident has been resolved.

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

1. resolved 2026-03-03 13:30 UTC

   For a brief period of time, customers may have not been able to access the the Bandwidth App as expected for both UP and API users. At this time, access has been restored and teams consider this incident resolved.

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

1. resolved 2026-03-03 04:28 UTC

   This incident has been resolved.

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

1. resolved 2026-02-27 20:47 UTC

   This incident has been resolved.

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

1. resolved 2026-02-27 15:00 UTC

   This incident has been resolved.

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

1. resolved 2026-02-27 17:30 UTC

   This incident has been resolved.

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

1. resolved 2026-02-21 04:52 UTC

   This incident has been resolved.

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

1. resolved 2026-02-20 18:27 UTC

   For a brief period of time some calls transversing our ATL data center could not be completed as expected. At this time, calls are completing as expected. We consider this incident resolved.

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

1. resolved 2026-02-19 21:59 UTC

   This incident has been resolved.

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

1. resolved 2026-02-19 21:26 UTC

   This incident has been resolved.

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

1. resolved 2026-02-18 01:00 UTC

   This incident has been resolved.

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

1. resolved 2026-02-17 20:38 UTC

   This incident has been resolved.

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

1. resolved 2026-02-17 13:10 UTC

   This incident has been resolved.

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

1. resolved 2026-02-16 17:23 UTC

   This incident has been resolved.

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

1. resolved 2026-02-05 12:35 UTC

   This incident has been resolved. Customers may retry any failed provisioning request at this time.

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

1. resolved 2026-02-04 18:54 UTC

   This incident has been resolved.

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

1. resolved 2026-02-04 08:26 UTC

   This incident has been resolved.

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

1. resolved 2026-02-04 12:50 UTC

   This incident has been resolved.

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

1. resolved 2026-01-31 20:15 UTC

   This incident has been resolved.

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

1. resolved 2026-01-30 21:19 UTC

   This incident has been resolved.

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

1. resolved 2026-01-28 17:05 UTC

   This incident has been resolved.

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

1. resolved 2026-01-27 21:03 UTC

   This incident has been resolved.

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

1. resolved 2026-01-31 18:13 UTC

   The FCC has DEACTIVATED PRD-EAST DIRS for Winter Storm Fern; Bandwidth’s network operated as expected throughout this weather event.

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

1. resolved 2026-01-23 17:30 UTC

   For a brief period of time, some 10DLC enabled numbers may not have been able to transmit messages to AT&T Destinations. Those numbers were identified and reprovisioned. Teams are observing expected messaging behavior and will continue to monitor.

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

1. resolved 2026-01-26 16:59 UTC

   The storm has officially cleared out, and those signature Carolina blue skies are back. As we expected, our network held strong throughout the weekend with zero impact to our services. Our teams have given the "all clear," but we’ll continue to do what we do best—monitoring...

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

1. resolved 2026-01-23 14:02 UTC

   This incident has been resolved.

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

1. resolved 2026-02-05 23:42 UTC

   This incident has been resolved.

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

1. resolved 2026-01-21 15:32 UTC

   This incident has been resolved.

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

1. resolved 2026-01-22 00:22 UTC

   This incident has been resolved.

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

1. resolved 2026-01-20 20:06 UTC

   For a short period of time, the Bandwidth App experienced a delay in order processing. Orders during this time were queued and processed after a delay. At this time, timely order processing is being observed and we consider this incident resolved.

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

1. resolved 2026-01-15 15:58 UTC

   This incident has been resolved.

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

1. resolved 2026-01-09 21:30 UTC

   This incident has been resolved.

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

1. resolved 2026-01-08 23:54 UTC

   This incident has been resolved.

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

1. resolved 2026-01-08 12:50 UTC

   For a brief period some outbound Germany based calls failed to process as expected. At this time we are observing expected network behavior and conceder this incident resolved.

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

1. resolved 2026-01-07 23:28 UTC

   This incident has been resolved.

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

1. resolved 2026-01-07 15:12 UTC

   This incident has been resolved.

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

1. resolved 2026-01-05 09:30 UTC

   For a brief period time inbound and outbound Romania base calls were not completing as expected. At this time expected network behavior is being observed.

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

1. resolved 2025-12-22 15:35 UTC

   This incident has been resolved.

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

1. resolved 2025-12-18 20:07 UTC

   This incident has been resolved.

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

1. resolved 2025-12-18 01:08 UTC

   This incident has been resolved.

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

1. resolved 2025-12-18 01:09 UTC

   This incident has been resolved.

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

1. resolved 2025-12-15 20:03 UTC

   This incident has been resolved.

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

1. resolved 2025-12-12 18:45 UTC

   This incident has been resolved.

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

1. resolved 2025-12-12 00:19 UTC

   This incident has been resolved.

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

1. resolved 2025-12-16 22:13 UTC

   This incident has been resolved.

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

1. resolved 2025-12-12 00:19 UTC

   This incident has been resolved.

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

1. resolved 2025-12-11 03:00 UTC

   For a brief period of time, some calls transversing our Atlanta data center failed to complete as expected. At this time teams are observing expected network behavior in Atlanta and we consider this incident resolved.

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

1. resolved 2025-12-10 17:52 UTC

   This incident has been resolved.

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

1. resolved 2025-12-09 17:04 UTC

   This incident has been resolved.

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

1. resolved 2025-12-08 06:02 UTC

   This incident has been resolved.

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

1. resolved 2025-12-08 06:02 UTC

   This incident has been resolved.

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

1. resolved 2025-12-02 06:50 UTC

   This incident has been resolved.

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

1. resolved 2025-11-28 20:30 UTC

   For a brief period of time some Toll Free SMS messages to Verizon Wireless Destinations were delayed in delivery. At this time we are observing expected network behavior and expected Toll Free Delivery.

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

1. resolved 2025-12-01 16:33 UTC

   This incident has been resolved.

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

1. resolved 2025-11-24 22:34 UTC

   This incident has been resolved.

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

1. resolved 2025-11-20 18:44 UTC

   This incident has been resolved.

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

1. resolved 2025-11-19 02:14 UTC

   This incident has been resolved.

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

1. resolved 2025-11-10 22:57 UTC

   This incident has been resolved.

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

1. resolved 2025-11-07 18:13 UTC

   This incident has been resolved.

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

1. resolved 2025-11-07 12:29 UTC

   This incident has been resolved.

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

1. resolved 2025-11-04 21:08 UTC

   This incident has been resolved.

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

1. resolved 2025-11-01 02:08 UTC

   This incident has been resolved.

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

1. resolved 2025-10-30 20:55 UTC

   This incident has been resolved.

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

1. resolved 2025-10-29 20:50 UTC

   This incident has been resolved.

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

1. resolved 2025-10-29 00:46 UTC

   This incident has been resolved.

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

1. resolved 2025-10-27 20:00 UTC

   For a brief period of time email notifications from the Bandwidth App were delayed in delivery. At this time, email notifications are processing as expected.

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

1. resolved 2025-10-27 23:29 UTC

   This incident has been resolved.

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

1. resolved 2025-10-23 22:38 UTC

   This incident has been resolved.

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

1. resolved 2025-10-23 11:44 UTC

   This incident has been resolved.

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

1. resolved 2025-10-22 21:55 UTC

   This incident has been resolved.

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

1. resolved 2025-10-21 13:36 UTC

   This incident has been resolved.

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

1. resolved 2025-10-21 13:40 UTC

   This incident has been resolved.

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

1. resolved 2025-10-21 17:19 UTC

   This incident has been resolved.

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

1. resolved 2025-10-20 23:26 UTC

   This incident has been resolved.

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

1. resolved 2025-10-20 21:43 UTC

   This incident has been resolved.

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

1. resolved 2025-10-21 13:40 UTC

   This incident has been resolved.

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

1. resolved 2025-10-08 21:09 UTC

   This incident has been resolved.

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

1. resolved 2025-10-07 22:08 UTC

   This incident has been resolved.

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

1. resolved 2025-10-06 21:09 UTC

   This incident has been resolved.

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

1. resolved 2025-10-02 01:22 UTC

   This incident has been resolved.

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

1. resolved 2025-10-03 17:29 UTC

   This incident has been resolved.

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

1. resolved 2025-09-29 19:39 UTC

   This incident has been resolved.

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

1. resolved 2025-09-27 23:19 UTC

   This incident has been resolved.

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

1. resolved 2025-09-26 20:49 UTC

   This incident has been resolved.

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

1. resolved 2025-09-25 04:07 UTC

   This incident has been resolved.

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

1. resolved 2025-09-24 22:18 UTC

   This incident has been resolved.

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

1. resolved 2025-09-23 16:33 UTC

   For a brief period of time, some users of the Bandwidth App may have experienced unexpected 504 errors or portal timeouts. At this time, the App is stable and we consider this incident resolved.

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

1. resolved 2025-09-23 14:00 UTC

   This incident has been resolved.

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

1. resolved 2025-09-22 10:43 UTC

   For a brief period MMS messages were not completing ad expected. Teams are observing expected MMS deliver behavior at this time.

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

1. resolved 2025-09-20 01:04 UTC

   This incident has been resolved.

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

1. resolved 2025-09-18 16:01 UTC

   This incident has been resolved.

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

1. resolved 2025-09-18 09:04 UTC

   For a brief moment all inbound calling for India was unavailable. At the time all services have been restored.

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

1. resolved 2025-09-17 16:13 UTC

   This incident has been resolved.

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

1. resolved 2025-09-16 06:00 UTC

   For a brief period of time, some inbound and outbound Australian base calls failed to complete as expected. Teams are observing, expected network behavior, and will monitor for prolonged stability.

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

1. resolved 2025-09-12 22:11 UTC

   This incident has been resolved.

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

1. resolved 2025-09-11 02:27 UTC

   This incident has been resolved.

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

1. resolved 2025-09-10 08:27 UTC

   For a brief period of time, some Outbound and Inbound Calls received unexpected 404 SIP Error codes for both calling directions. Teams have resolved the impact and are observing expected call transit behavior. We will continue to monitor for stability.

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

1. resolved 2025-09-08 22:47 UTC

   This incident has been resolved.

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

1. resolved 2025-09-12 19:17 UTC

   Monitoring for this issue has been completed. Services should be restored. Resolving at this time

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

1. resolved 2025-09-06 02:13 UTC

   This incident has been resolved.

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

1. resolved 2025-09-03 09:00 UTC

   For a brief period of time, outbound calls from Norway over a specific provider did not complete as expected. Teams have resolved the issue and are observing expect network connectivity.

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

1. resolved 2025-09-11 18:29 UTC

   This incident has been resolved.

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

1. resolved 2025-09-03 01:35 UTC

   This incident has been resolved.

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

1. resolved 2025-08-31 01:50 UTC

   This incident has been resolved.

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

1. resolved 2025-09-11 19:42 UTC

   This incident has been resolved.

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

1. resolved 2025-08-29 09:10 UTC

   This incident has been resolved.

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

1. resolved 2025-08-28 10:57 UTC

   This incident has been resolved.

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

1. resolved 2025-08-27 11:24 UTC

   For a brief period of time, some 10DLC messages were either delayed in delivery after a successful retry or failed to deliver as expected. Teams are observing expected deliver behaviors at this time.

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

1. resolved 2025-08-22 22:30 UTC

   We experienced a disruption with one of our DFW SBCs that impacted some voice traffic with disconnections between 6:38pm and 6:45 pm ET today. The network recovered and has been stable since.

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

1. resolved 2025-08-21 17:50 UTC

   We’ve confirmed stability and we’re considering this incident resolved.

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

1. resolved 2025-08-21 20:54 UTC

   We’ve confirmed stability with the issue and we’re considering this incident resolved.

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

1. resolved 2025-08-20 20:42 UTC

   A fix was implemented for the issue and we’ve confirmed orders are completing as expected at this time. We’re considering this incident resolved.

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

1. resolved 2025-08-20 16:35 UTC

   We've confirmed stability and we're considering this incident resolved.

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

1. resolved 2025-08-19 11:00 UTC

   Between 7:09am and 7:50am EDT we experienced an incident with our network in Israel that caused inbound traffic failures. The issue is resolved at this time and the network is functioning normally.

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

1. resolved 2025-08-17 00:11 UTC

   This incident has been resolved.

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

1. resolved 2025-08-15 20:33 UTC

   This incident has been resolved.

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

1. resolved 2025-08-15 18:05 UTC

   This incident has been resolved.

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

1. resolved 2025-08-13 20:37 UTC

   This incident has been resolved.

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

1. resolved 2025-08-13 20:30 UTC

   This incident has been resolved.

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

1. resolved 2025-08-13 02:52 UTC

   This incident has been resolved.

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

1. resolved 2025-08-12 18:47 UTC

   Bandwidth teams identified an off-network incident with intermittent call failures for inbound Toll-Free Origination from Canada that were not completing as expected. At this time, this incident has been resolved.

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

1. resolved 2025-08-12 22:54 UTC

   This incident has been resolved.

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

1. resolved 2025-08-10 20:00 UTC

   Between 4:04pm and 5:08pm ET today, we experienced an issue with outbound MM7 deliveries over short code through one of our partners, causing some messages to be delayed or expired.

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

1. resolved 2025-08-07 17:43 UTC

   We’ve confirmed stability and we’re considering this incident resolved.

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

1. resolved 2025-08-06 19:03 UTC

   We've confirmed stability and we're considering this incident resolved.

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

1. resolved 2025-08-06 15:30 UTC

   We experienced a brief outage in some specific ATL SBCs between 11:51am and 11:53am ET today that caused a small amount of calls to disconnect. The SBCs were restored and are working g properly now.

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

1. resolved 2025-08-06 11:41 UTC

   This incident has been resolved.

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

1. resolved 2025-08-12 21:13 UTC

   This incident has been resolved.

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

1. resolved 2025-08-04 16:00 UTC

   Between 12:07pm and 12:31pm EDT today we experienced an issue with our JFK data center that caused some call failures on inbound traffic. The issue has been resolved at this time and traffic is functioning as expected.

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

1. resolved 2025-08-02 17:39 UTC

   This incident has been resolved.

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