- Detected by Pingoru
- Oct 04, 2026, 02:14 PM UTC
- Resolved
- Oct 04, 2026, 08:29 PM UTC
- Duration
- 6h 15m
Affected: 320 - Cleveland, OH
Timeline · 3 updates
-
investigating Oct 04, 2026, 02:14 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
monitoring Oct 04, 2026, 04:39 PM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Oct 04, 2026, 08:29 PM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 04, 2026, 02:03 PM UTC
- Resolved
- Oct 04, 2026, 08:28 PM UTC
- Duration
- 6h 25m
Affected: 336 - Indianapolis, IN
Timeline · 3 updates
-
investigating Oct 04, 2026, 02:03 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
monitoring Oct 04, 2026, 04:05 PM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Oct 04, 2026, 08:28 PM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 03, 2026, 08:00 PM UTC
- Resolved
- Oct 03, 2026, 08:00 PM UTC
- Duration
- —
Timeline · 2 updates
-
resolved Oct 03, 2026, 08:05 PM 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.
-
postmortem Oct 05, 2026, 11:28 AM UTC
Bandwidth has concluded its investigation of this issue and determined that between 12:13 UTC and 12:37 UTC on October 3, 2026, Voice service for calls traversing the Brussels data center experienced intermittent dropped calls. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
- Detected by Pingoru
- Oct 03, 2026, 10:12 AM UTC
- Resolved
- Oct 03, 2026, 11:46 AM UTC
- Duration
- 1h 34m
Affected: 236 - Washington, DC
Timeline · 3 updates
-
investigating Oct 03, 2026, 10:12 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
monitoring Oct 03, 2026, 11:02 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete.
-
resolved Oct 03, 2026, 11:46 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 03:30 AM UTC
- Resolved
- Oct 02, 2026, 03:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 02, 2026, 01:53 PM 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 sense observed expected network behavior, and consider this incident resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 03:04 AM UTC
- Resolved
- Oct 02, 2026, 01:27 PM UTC
- Duration
- 10h 22m
Affected: Line Feature Management
Timeline · 4 updates
-
investigating Oct 02, 2026, 03:04 AM UTC
Bandwidth teams are investigating an incident impacting Messaging Provisioning requests. These requests are delayed in processing.
-
identified Oct 02, 2026, 10:53 AM UTC
Teams continue work to restore expected portal performance.
-
resolved Oct 02, 2026, 01:27 PM UTC
This incident has been resolved.
-
postmortem Oct 02, 2026, 02:07 PM UTC
Between 00:43 UTC and 13:53 UTC on October 2nd, messaging provisioning and deprovisioning requests experienced delays and intermittent failures. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 04:31 PM UTC
- Resolved
- Oct 03, 2026, 01:18 AM UTC
- Duration
- 1d 8h
Affected: 532 - Wichita, KS
Timeline · 11 updates
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 04:14 PM UTC
- Resolved
- Oct 01, 2026, 08:00 PM UTC
- Duration
- 3h 46m
Affected: Line Feature Management
Timeline · 3 updates
-
investigating Oct 01, 2026, 04:14 PM UTC
Bandwidth teams are investigating an incident on the Bandwidth App where customers are unable to successfully search for, or view 10 DLC campaigns. Teams are working to score restore expected portal behavior.
-
resolved Oct 01, 2026, 08:00 PM UTC
This incident has been resolved.
-
postmortem Oct 02, 2026, 07:34 AM UTC
Bandwidth has concluded its investigation of this issue and determined that between 09:00 UTC and 19:31 UTC on October 1, 2026, Messaging customers experienced errors when attempting to view or search campaigns through the customer portal. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 04:34 AM UTC
- Resolved
- Oct 02, 2026, 06:39 AM UTC
- Duration
- 1d 2h
Affected: 256 - Clarksburg, WV
Timeline · 8 updates
-
investigating Oct 01, 2026, 04:34 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
investigating Oct 01, 2026, 09:36 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
identified Oct 01, 2026, 10:27 AM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Oct 01, 2026, 02:50 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Oct 01, 2026, 06:14 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
monitoring Oct 01, 2026, 10:04 PM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
monitoring Oct 02, 2026, 02:05 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Oct 02, 2026, 06:39 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Notice September 30, 2026 - Detected by Pingoru
- Sep 30, 2026, 01:35 PM UTC
- Resolved
- Sep 30, 2026, 05:36 PM UTC
- Duration
- 4h
Affected: 932 - Bluefield, WV
Timeline · 2 updates
-
investigating Sep 30, 2026, 01:35 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
resolved Sep 30, 2026, 05:36 PM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2026, 01:54 AM UTC
- Resolved
- Sep 30, 2026, 02:31 AM UTC
- Duration
- 36m
Affected: MMS Messaging (MM4)
Timeline · 3 updates
-
investigating Sep 30, 2026, 01:54 AM UTC
Bandwidth teams are investigating an incident impacting outbound MMS messages towards AT&T destinations. Theses messages are delayed in delivery.
-
resolved Sep 30, 2026, 02:31 AM UTC
This incident has been resolved.
-
postmortem Sep 30, 2026, 11:53 AM UTC
Between 23:37 UTC and 02:07 UTC on September 29-30, 2026, outbound MMS messages destined for AT&T 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 Incident Report after investigations have concluded. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
Notice September 30, 2026 - Detected by Pingoru
- Sep 30, 2026, 01:14 AM UTC
- Resolved
- Sep 30, 2026, 01:52 PM UTC
- Duration
- 12h 38m
Affected: 974 - Rochester, NY
Timeline · 6 updates
-
investigating Sep 30, 2026, 01:14 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
investigating Sep 30, 2026, 07:43 AM UTC
We are continuing to investigate this issue.
-
identified Sep 30, 2026, 08:24 AM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
monitoring Sep 30, 2026, 11:00 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete.
-
monitoring Sep 30, 2026, 12:27 PM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete.
-
resolved Sep 30, 2026, 01:52 PM 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
Read the full incident report →
Notice September 29, 2026 - Detected by Pingoru
- Sep 29, 2026, 07:49 AM UTC
- Resolved
- Sep 30, 2026, 12:07 PM UTC
- Duration
- 1d 4h
Affected: 326 - Toledo, OH
Timeline · 8 updates
-
investigating Sep 29, 2026, 07:49 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
investigating Sep 29, 2026, 12:01 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
identified Sep 29, 2026, 05:45 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Sep 29, 2026, 09:01 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Sep 30, 2026, 01:31 AM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Sep 30, 2026, 07:46 AM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
monitoring Sep 30, 2026, 08:56 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Sep 30, 2026, 12:07 PM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Notice September 27, 2026 - Detected by Pingoru
- Sep 27, 2026, 06:00 AM UTC
- Resolved
- Sep 27, 2026, 08:57 AM UTC
- Duration
- 2h 56m
Affected: 442 - Augusta, GA
Timeline · 2 updates
-
investigating Sep 27, 2026, 06:00 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
resolved Sep 27, 2026, 08:57 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Notice September 25, 2026 - Detected by Pingoru
- Sep 25, 2026, 12:13 PM UTC
- Resolved
- Sep 25, 2026, 12:13 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Sep 25, 2026, 07:00 PM 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 inbound to our network.
Read the full incident report →
Notice September 25, 2026 - Detected by Pingoru
- Sep 25, 2026, 10:45 AM UTC
- Resolved
- Sep 25, 2026, 10:45 AM UTC
- Duration
- —
Timeline · 2 updates
-
resolved Sep 25, 2026, 10:45 AM UTC
For a brief period of time the Bandwidth Global portal failed to properly display pricing information. Teams have resolved this incident.
-
postmortem Sep 25, 2026, 12:03 PM UTC
Bandwidth has concluded its investigation of this issue and determined that between 08:33 UTC and 09:13 UTC on September 25, 2026, the BWI Customer Portal pricing page was unavailable. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
Notice September 25, 2026 - Detected by Pingoru
- Sep 25, 2026, 04:35 AM UTC
- Resolved
- Sep 25, 2026, 11:13 AM UTC
- Duration
- 6h 37m
Affected: 721 - Las Vegas, NV
Timeline · 4 updates
-
investigating Sep 25, 2026, 04:35 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
identified Sep 25, 2026, 06:31 AM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
monitoring Sep 25, 2026, 07:03 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete.
-
resolved Sep 25, 2026, 11:13 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Critical September 25, 2026 - Detected by Pingoru
- Sep 25, 2026, 03:17 AM UTC
- Resolved
- Sep 26, 2026, 02:28 AM UTC
- Duration
- 23h 11m
Affected: 330 - Evansville, IN
Timeline · 7 updates
-
investigating Sep 25, 2026, 03:17 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
investigating Sep 25, 2026, 07:05 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
investigating Sep 25, 2026, 10:04 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
identified Sep 25, 2026, 12:35 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
identified Sep 25, 2026, 07:01 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
identified Sep 25, 2026, 11:47 PM UTC
Our carrier has identified the cause of this incident and is working to complete repairs.
-
resolved Sep 26, 2026, 02:28 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Notice September 25, 2026 - Detected by Pingoru
- Sep 25, 2026, 12:10 AM UTC
- Resolved
- Sep 25, 2026, 02:12 AM UTC
- Duration
- 2h 2m
Affected: MMS Messaging (MM4)
Timeline · 1 update
-
investigating Sep 25, 2026, 12:10 AM UTC
We are aware of an issue affecting a subset of inbound MMS messages. Impacted customers may observe inbound MMS being delivered as unexpected group messages containing unrelated content or participants. We are actively investigating and working with our messaging partners toward resolution. Updates will be provided as more information becomes available.
Read the full incident report →
Critical September 24, 2026 - Detected by Pingoru
- Sep 24, 2026, 08:25 PM UTC
- Resolved
- Sep 25, 2026, 12:32 AM UTC
- Duration
- 4h 6m
Affected: 340 - Southfield, MI
Timeline · 2 updates
-
investigating Sep 24, 2026, 08:25 PM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
resolved Sep 25, 2026, 12:32 AM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
Notice September 24, 2026 - Detected by Pingoru
- Sep 24, 2026, 07:49 AM UTC
- Resolved
- Sep 24, 2026, 12:59 PM UTC
- Duration
- 5h 10m
Affected: 636 - Fargo, ND
Timeline · 3 updates
-
investigating Sep 24, 2026, 07:49 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
monitoring Sep 24, 2026, 10:36 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Sep 24, 2026, 12:59 PM UTC
Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 23, 2026, 04:06 PM UTC
- Resolved
- Sep 23, 2026, 08:02 PM UTC
- Duration
- 3h 56m
Affected: MMS Messaging (MM4)
Timeline · 5 updates
-
identified Sep 23, 2026, 04:06 PM UTC
Bandwidth teams have identified an incident impacting outbound MMS messaging delays in delivery. Teams are working to restore expected MMS delivery.
-
identified Sep 23, 2026, 06:41 PM UTC
Bandwidth teams have confirmed this is an off-network industry condition impacting MMS messaging to AT&T destinations.
-
monitoring Sep 23, 2026, 07:18 PM UTC
Teams are observing expected MMS delivery towards AT&T. We will monitor for stability.
-
resolved Sep 23, 2026, 08:02 PM UTC
This incident has been resolved.
-
postmortem Sep 24, 2026, 11:05 AM UTC
Between 12:30 UTC and 18:45 UTC on September 23rd, 2026, 10DLC MMS messages sent to AT&T destinations experienced delayed delivery. Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an Incident Report after investigations have concluded. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
Notice September 23, 2026 - Detected by Pingoru
- Sep 23, 2026, 11:41 AM UTC
- Resolved
- Sep 23, 2026, 12:54 PM UTC
- Duration
- 1h 12m
Affected: Messaging Insights Dashboard
Timeline · 3 updates
-
monitoring Sep 23, 2026, 11:41 AM UTC
After a brief period of instability, teams are motoring stable reporting via Messaging Insights on the Bandwidth App.
-
resolved Sep 23, 2026, 12:54 PM UTC
This incident has been resolved.
-
postmortem Sep 24, 2026, 11:28 AM UTC
Bandwidth has concluded its investigation of this issue and determined that between 07:01 UTC and 11:23 UTC on September 23, 2026, Messaging Insights dashboards did not display data for customers. Due to the limited scope of impact, Bandwidth is closing this incident and this will be the extent of the information we will provide for this issue. If you have any questions, please contact us through the Bandwidth support portal. We are grateful you have entrusted Bandwidth as your communication partner and we are sorry if this issue resulted in any disruption to your services.
Read the full incident report →
Notice September 23, 2026 - Detected by Pingoru
- Sep 23, 2026, 05:13 AM UTC
- Resolved
- Sep 23, 2026, 09:35 AM UTC
- Duration
- 4h 21m
Affected: 522 - Springfield, MO
Timeline · 3 updates
-
investigating Sep 23, 2026, 05:13 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
monitoring Sep 23, 2026, 05:36 AM UTC
We have observed services in this market have recovered and our carrier is finalizing repairs. This incident will be resolved when we confirm all repairs are complete
-
resolved Sep 23, 2026, 09:35 AM UTC
This incident has been resolved.
Read the full incident report →
Critical September 23, 2026 - Detected by Pingoru
- Sep 23, 2026, 04:12 AM UTC
- Resolved
- Sep 23, 2026, 04:29 AM UTC
- Duration
- 17m
Affected: 444 - Albany , GA
Timeline · 2 updates
-
investigating Sep 23, 2026, 04:12 AM UTC
We are experiencing an impairment on the Bandwidth network which may affect a portion of calls. We are currently working with our carrier for resolution.
-
resolved Sep 23, 2026, 04:29 AM UTC
Bandwidth has observed continued stability to and is resolving this incident.
Read the full incident report →
