- Detected by Pingoru
- Apr 30, 2026, 10:28 AM UTC
- Resolved
- Apr 30, 2026, 10:00 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 30, 2026, 10:28 AM 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 this incident resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 11:15 PM UTC
- Resolved
- Apr 29, 2026, 12:07 AM UTC
- Duration
- 51m
Affected: MMS Messaging (MM4)REST APIs - HTTP MMS Messaging
Timeline · 2 updates
-
investigating Apr 28, 2026, 11:15 PM UTC
Bandwidth teams are investigating an outbound MMS incident impacting Hosted Media.
-
resolved Apr 29, 2026, 12:07 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 28, 2026, 12:52 PM UTC
- Resolved
- Apr 28, 2026, 12:52 PM UTC
- Duration
- —
Affected: Inbound Calling - Israel
Timeline · 1 update
-
resolved Apr 28, 2026, 12:52 PM 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
Read the full incident report →
- Detected by Pingoru
- Apr 27, 2026, 01:05 PM UTC
- Resolved
- Apr 30, 2026, 03:57 PM UTC
- Duration
- 3d 2h
Affected: SMS Messaging (SMPP)MMS Messaging (MM4)Toll-Free SMS - OutboundToll Free MMS - Outbound
Timeline · 9 updates
-
investigating Apr 27, 2026, 01:05 PM UTC
Bandwidth teams are investigating an outbound messaging incident, where customers are experiencing unexpected 4452 error codes. Teams are working to restore expected messaging behavior.
-
investigating Apr 27, 2026, 03:55 PM UTC
Teams continue to investigate this incident.
-
investigating Apr 27, 2026, 07:04 PM UTC
Teams continue to investigate this incident.
-
identified Apr 27, 2026, 07:59 PM UTC
Teams have identified the source of this incident and are working to restore expected network behavior.
-
identified Apr 28, 2026, 12:27 PM UTC
Trams continue work to resolve this incident. Ongoing mitigation work is underway.
-
identified Apr 28, 2026, 05:52 PM UTC
Trams continue work to resolve this incident. Ongoing mitigation work is underway.
-
monitoring Apr 28, 2026, 06:56 PM UTC
Teams are observing expected messaging behaviors, and will continue to monitor for stability.
-
monitoring Apr 29, 2026, 05:02 PM UTC
Teams continue to observe expected messaging behaviors, and will continue to monitor for stability.
-
resolved Apr 30, 2026, 03:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 24, 2026, 04:55 PM UTC
- Resolved
- Apr 27, 2026, 03:52 PM UTC
- Duration
- 2d 22h
Affected: Inbound Calling (SIP) - United States
Timeline · 6 updates
-
investigating Apr 24, 2026, 04:55 PM UTC
Bandwidth teams are investigating an off net inbound calling incident impacting Alaska based numbers. Teams are working with the impaired vendor to restored expected call processing.
-
identified Apr 24, 2026, 06:24 PM UTC
The source of this incidnet has been identified by the impaired vender. They are working to restore expected calling behavior.
-
identified Apr 24, 2026, 09:40 PM UTC
Teams continue to work to restore expected calling behavior.
-
monitoring Apr 24, 2026, 11:26 PM UTC
Teams are observing expected calling behavior. We will monitor for prolonged stability.
-
monitoring Apr 25, 2026, 05:57 PM UTC
We are continuing to monitor for stability.
-
resolved Apr 27, 2026, 03:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 01:22 PM UTC
- Resolved
- Apr 23, 2026, 07:20 PM UTC
- Duration
- 5h 57m
Affected: Bandwidth AppLine Feature Management
Timeline · 4 updates
-
investigating Apr 23, 2026, 01:22 PM UTC
Bandwidth teams are investigating an incident where campaign registrations made on the Bandwidth App are not processing as expected. Teams are working to restore expected processing behavior.
-
identified Apr 23, 2026, 05:20 PM UTC
Teams have identified the source of this incident and are working to restore expected portal behavior.
-
monitoring Apr 23, 2026, 05:44 PM UTC
Teams are observing expected portal behavior and will monitor for stability.
-
resolved Apr 23, 2026, 07:20 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 08:23 AM UTC
- Resolved
- Apr 23, 2026, 05:29 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 23, 2026, 08:23 AM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 23, 2026, 06:59 AM UTC
- Resolved
- Apr 23, 2026, 11:48 AM UTC
- Duration
- 4h 49m
Affected: Bandwidth AppMessaging Insights Dashboard
Timeline · 3 updates
-
investigating Apr 23, 2026, 06:59 AM UTC
Teams are also investigating an incident impacting Insights on the Bandwidth App. Insights may fail to load or display properly.
-
identified Apr 23, 2026, 08:18 AM UTC
Teams have identified the source of this incident and are working to restore expected services.
-
resolved Apr 23, 2026, 11:48 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 03:26 PM UTC
- Resolved
- Apr 23, 2026, 02:03 PM UTC
- Duration
- 22h 37m
Affected: 9-1-1 Dashboard
Timeline · 8 updates
-
investigating Apr 22, 2026, 03:26 PM UTC
Bandwidth teams are investigating an incident where reports generated by the 9-1-1 Dashboard may contain duplicated data points. Teams are working to restore expected reporting behavior. Note: This incident does not impact emergency call routing.
-
identified Apr 22, 2026, 03:46 PM UTC
Teams have identified the source of the incident and are working to restore expect record processing behaviors. Note: This incident does not impact emergency call routing.
-
identified Apr 22, 2026, 08:28 PM UTC
Teams have identified the source of the incident and are working to restore expect record processing behaviors.
-
identified Apr 22, 2026, 11:30 PM UTC
Teams have identified the source of the incident and are working to restore expect record processing behaviors.
-
identified Apr 23, 2026, 02:04 AM UTC
Teams have identified the source of the incident and are working to restore expect record processing behaviors.
-
monitoring Apr 23, 2026, 06:55 AM UTC
Teams are observing expected behavior and will continue to monitor.
-
monitoring Apr 23, 2026, 01:23 PM UTC
We are continuing to monitor for any further issues.
-
resolved Apr 23, 2026, 02:03 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 11:58 AM UTC
- Resolved
- Apr 22, 2026, 02:44 PM UTC
- Duration
- 2h 45m
Affected: MMS Messaging (MM4)
Timeline · 3 updates
-
investigating Apr 22, 2026, 11:58 AM UTC
Bandwidth teams are currently investigating an incident impacting MMS DLRs. These DLRs are delayed in population.
-
monitoring Apr 22, 2026, 12:36 PM UTC
Teams are observing expected network performance. We will monitor for continued stability.
-
resolved Apr 22, 2026, 02:44 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 22, 2026, 07:45 AM UTC
- Resolved
- Apr 22, 2026, 07:43 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 22, 2026, 07:45 AM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 21, 2026, 09:44 PM UTC
- Resolved
- Apr 22, 2026, 02:28 AM UTC
- Duration
- 4h 43m
Affected: Bandwidth App
Timeline · 3 updates
-
investigating Apr 21, 2026, 09:44 PM UTC
Bandwidth teams are investigating an incident where hosted messaging requests are failing to complete as expected. Teams are working to restore expected portal behavior.
-
identified Apr 21, 2026, 11:20 PM UTC
Teams have identified the source of this incident and are working to restore expected portal behaviors.
-
resolved Apr 22, 2026, 02:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 07:46 AM UTC
- Resolved
- Apr 20, 2026, 08:52 AM UTC
- Duration
- 1h 6m
Timeline · 2 updates
-
investigating Apr 20, 2026, 07:46 AM UTC
Lata 668 (Tucson, AZ) is currently experiencing a complete market outage. NOC is working with the carrier for resolution to this issue.
-
resolved Apr 20, 2026, 08:52 AM UTC
Outage for Lata 668 (Tucson, AZ) is now resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 18, 2026, 12:30 AM UTC
- Resolved
- Apr 18, 2026, 12:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 18, 2026, 01:03 PM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 04:29 PM UTC
- Resolved
- Apr 17, 2026, 01:04 AM UTC
- Duration
- 8h 34m
Affected: Bandwidth App
Timeline · 4 updates
-
investigating Apr 16, 2026, 04:29 PM UTC
Bandwidth teams are investigating intermittent service interruptions or connectivity issues for users attempting to access the Bandwidth App platform. Teams are working to restore expected portal behavior.
-
monitoring Apr 16, 2026, 06:38 PM UTC
Bandwidth teams are observing expected and stable App behavior. We will monitor for prolonged stability.
-
identified Apr 16, 2026, 08:58 PM UTC
Teams continue work resolve this incident.
-
resolved Apr 17, 2026, 01:04 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 10:24 PM UTC
- Resolved
- Apr 15, 2026, 09:46 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Apr 15, 2026, 10:24 PM 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.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 04:19 PM UTC
- Resolved
- Apr 16, 2026, 01:28 AM UTC
- Duration
- 9h 9m
Affected: Bandwidth App
Timeline · 4 updates
-
investigating Apr 15, 2026, 04:19 PM UTC
Bandwidth teams are currently investigating an incident on the Bandwidth App where IP self-provisioning requests are resulting an unexpected errors.
-
investigating Apr 15, 2026, 07:29 PM UTC
Teams continue work to restore expected portal behavior.
-
investigating Apr 15, 2026, 09:26 PM UTC
Teams continue work to restore expected portal behavior.
-
resolved Apr 16, 2026, 01:28 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 15, 2026, 02:30 PM UTC
- Resolved
- Apr 15, 2026, 02:52 PM UTC
- Duration
- 21m
Affected: Line Feature Management
Timeline · 2 updates
-
investigating Apr 15, 2026, 02:30 PM UTC
Bandwidth teams are investigating a delay in 10DLC Provisioning requests. We are working to restore expected provisioning behavior.
-
resolved Apr 15, 2026, 02:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 11:58 PM UTC
- Resolved
- Apr 15, 2026, 08:38 AM UTC
- Duration
- 8h 40m
Affected: Europe
Timeline · 3 updates
-
investigating Apr 14, 2026, 11:58 PM UTC
Bandwidth is observing delays in SMS delivery in France. Teams are working to identify this issue an mitgate any impairments.
-
monitoring Apr 15, 2026, 08:02 AM UTC
Bandwidth upstream partner has implemented a fix to recover SMS delivery in France. At this time, impairments are fully mitigated and Bandwidth is continuing to monitor to ensure stability. We will resolve this incident after we observe continued stability.
-
resolved Apr 15, 2026, 08:38 AM UTC
Bandwidth has observed continued stability in SMS delivery to France and is resolving this incident.
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 11:53 AM UTC
- Resolved
- Apr 14, 2026, 01:40 PM UTC
- Duration
- 1h 46m
Affected: Ticketing SupportHelp Center
Timeline · 3 updates
-
investigating Apr 14, 2026, 11:53 AM UTC
Bandwidth teams have identified in incident with our vendor where users may not be able to interact with Synthi as expected. Users may still open support requests via email.
-
monitoring Apr 14, 2026, 01:24 PM UTC
Bandwidth is observing expected Synthi behavior. We will monitor for stability.
-
resolved Apr 14, 2026, 01:40 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 01:27 PM UTC
- Resolved
- Apr 13, 2026, 03:55 PM UTC
- Duration
- 2h 27m
Affected: Bandwidth App
Timeline · 3 updates
-
investigating Apr 13, 2026, 01:27 PM UTC
Bandwidth teams are investigating a small segment of users of the Bandwidth App who are unable to purchase telephone numbers as expected. Teams are working to restore expected number purchasing behaviors.
-
monitoring Apr 13, 2026, 02:00 PM UTC
Teams are observing expected portal behaviors and are monitoring for stability.
-
resolved Apr 13, 2026, 03:55 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 12, 2026, 01:08 AM UTC
- Resolved
- Apr 12, 2026, 04:40 AM UTC
- Duration
- 3h 31m
Affected: Bandwidth App
Timeline · 4 updates
-
identified Apr 12, 2026, 01:08 AM UTC
Bandwidth teams have identified an incident within the Bandwidth App and API where available Number Inventory may not display accurately leading to incomplete number orders. Teams are working to restore expected numbers order and inventory behavior.
-
identified Apr 12, 2026, 02:13 AM UTC
We continue to work to restore expected portal behavior.
-
monitoring Apr 12, 2026, 02:39 AM UTC
Teams are observing expected portal and inventory behavior. Teams will monitor for stability.
-
resolved Apr 12, 2026, 04:40 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 09, 2026, 11:51 AM UTC
- Resolved
- Apr 09, 2026, 12:57 PM UTC
- Duration
- 1h 6m
Affected: Outbound Calling - Belgium
Timeline · 3 updates
-
identified Apr 09, 2026, 11:51 AM UTC
Teams have identified an incident impacting outbound calling in Belgium. These calls may not complete as expected.
-
monitoring Apr 09, 2026, 12:21 PM UTC
Teams are observing expected network behavior and will continue to monitor for stability.
-
resolved Apr 09, 2026, 12:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 07:00 PM UTC
- Resolved
- Apr 09, 2026, 11:14 AM UTC
- Duration
- 16h 14m
Affected: Ticketing SupportHelp Center
Timeline · 3 updates
-
investigating Apr 08, 2026, 07:00 PM UTC
Bandwidth teams are observing a vendor incident where email-to-ticket functionality is not generating a ticket as expected. Customers are encouraged to open a ticket via our Help Center Portal with the assistance of Synthi.
-
identified Apr 08, 2026, 07:29 PM UTC
Bandwidths vendor has identified the sourced of this intermittent incident and are working to restore expected email behavior. While this incident is intermittent in nature, we still encourage customers to open a ticket via our Help Center Portal with the assistance of Synthi.
-
resolved Apr 09, 2026, 11:14 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 08, 2026, 05:00 PM UTC
- Resolved
- Apr 09, 2026, 11:47 AM UTC
- Duration
- 18h 46m
Affected: Bandwidth International (fka Voxbone) Portal
Timeline · 4 updates
-
investigating Apr 08, 2026, 05:00 PM UTC
Bandwidth teams are currently investigating an incident impacting auto top offs via credit card on the legacy global portal. Teams are working to restore expected portal payment behavior.
-
identified Apr 08, 2026, 06:16 PM UTC
Teams have identified the source of this incident, and are working to restore expected portal behavior.
-
monitoring Apr 09, 2026, 11:16 AM UTC
We are observing expected portal behavior and continue to monitor.
-
resolved Apr 09, 2026, 11:47 AM UTC
This incident has been resolved.
Read the full incident report →