Is Bandwidth Down Right Now? Check if there is a current outage ongoing.

We experienced an issue affecting some traffic over our Hong Kong PoP. This affected both inbound and outbound traffic. Issue is mitigated at this time and traffic has returned to normal.

For a brief period of time some inbound calls failed to complete as expected. At this time teams are observing expected call behavior.

Due to industry conditions, the Bandwidth Learning Lab inside the Bandwidth App may not function as expected, and support guides may fail to deploy as expected.

Bandwidth teams are investigating an industry condition impacting Inbound and Outbound Programmable Voice traffic. At this time, Prograable Voice traffic may not complete as expected.

We’ve seen traffic recover and we’re monitoring for stability.

We’re investigating an incident with our carrier in Switzerland casing failures to both inbound and outbound traffic.

We’re currently investigating an issue causing call failures for a small subset of outbound traffic to Canada. Relevant teams are engaged.

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

We’ve identified an issue with our regional partner causing SMS and MMS failures to Turkey, Saudi Arabia, and Kuwait. Relevant teams are engaged.

We experienced an issue that resulted in an increased amount of 5620 errors toward Verizon Wireless destination numbers between 2am and 12:40pm ET.

We’re currently investigating an issue causing some outbound MMS to expire and fail sending. Relevant teams are engaged.

We experienced an incident with our carrier in Croatia that affected outbound traffic to mobile destinations between 5:30am 6:02am ET. The issue has been resolved at this point and traffic is functioning normally at this time.

We experienced an incident with our carrier in Croatia that affected outbound traffic to mobile destinations between 5:30am 6:02am ET. The issue has been resolved at this point and traffic is functioning normally at this time.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth will be performing scheduled maintenance in the Los Angeles data center.As a part of the maintenance, Bandwidth will be disabling outbound services in the Los Angeles data center. During this time, all outbound traffic will be redirected to a geo-redundant site to ensure continued service availability. Bandwidth advises customers connecting exclusively to the Los Angeles data center to proactively re-route their outbound traffic to our geo-redundant data centers to avoid any possible disruption to services.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth will be performing scheduled maintenance in the New York data center.As a part of the maintenance, Bandwidth will be disabling outbound services in the New York data center. During this time, all outbound traffic will be redirected to a geo-redundant site to ensure continued service availability. Bandwidth advises customers connecting exclusively to the New York data center to proactively re-route their outbound traffic to our geo-redundant data centers to avoid any possible disruption to services.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth's downstream vendor will be performing maintenance that will potentially affect Bandwidth's SMS messaging platform. During the maintenance window, Bandwidth's customers may experience a delay in the delivery of inbound and outbound SMS messages.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth's downstream vendor will be performing maintenance that will potentially affect Bandwidth's Toll Free MMS/SMS messaging platform. During this maintenance window, brief periods of latency affecting inbound and outbound Toll Free MMS/SMS may be encountered.

This incident has been resolved.

Teams are investigating a degradation in service for Insights on the Bandwidth App. Specifically, EU-based data may not be accessible during this time.

This incident has been resolved.

Teams are investigating a degradation in service for Insights on the Bandwidth App. Specifically, EU-based data may not be accessible during this time.

This incident has been resolved.

Teams are investigating an incident impacting off-net port orders. These orders are delayed in activation.

This incident has been resolved.

Teams are investigating an incident impacting off-net port orders. These orders are delayed in activation.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth's downstream vendor will be performing maintenance that will potentially affect Bandwidth's Toll Free SMS messaging platform. During this maintenance window, brief periods of latency affecting inbound and outbound Toll Free SMS messages may be encountered.

This incident has been resolved.

Teams are observing the expected delivery of SMS and MMS Messages. We will continue to observe to ensure the impacted industry provider fully recovers.

Bandwidth Teams are investigating an Inbound Delivery incident where some inbound SMS/MMS Messages are not delivered to Bandwidth due to an industry provider network condition. Teams are working with the impaired industry provider to restore expected delivery of messages.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth will be performing scheduled maintenance in the Germany data center.As a part of the maintenance, Bandwidth will be disabling outbound services in the Germany data center. During this time, all outbound traffic will be redirected to a geo-redundant site to ensure continued service availability. Bandwidth advises customers connecting exclusively to the Germany data center to proactively re-route their outbound traffic to our geo-redundant data centers to avoid any possible disruption to services.

This incident has been resolved.

Teams are observing the expected delivery of SMS and MMS Messages. We will continue to observe to ensure the impacted industry provider fully recovers.

Bandwidth Teams are investigating an Inbound Delivery incident where some inbound SMS/MMS Messages are not delivered to Bandwidth due to an industry provider network condition. Teams are working with the impaired industry provider to restore expected delivery of messages.

We’ve confirmed stability and we’re considering this incident resolved.

We've implemented mitigation at this time, and messages are completing as expected at this time. We're currently monitoring for stability.

The issue has been identified and we're working to deploy a fix.

We're currently investigating an issue causing outbound message failures over Toll Free, to ATT, with error code 4360. Relevant teams are engaged, and we'll provide updates as they become available.

We’ve confirmed stability and we’re considering this incident resolved.

We've implemented mitigation at this time, and messages are completing as expected at this time. We're currently monitoring for stability.

The issue has been identified and we're working to deploy a fix.

We're currently investigating an issue causing outbound message failures over Toll Free, to ATT, with error code 4360. Relevant teams are engaged, and we'll provide updates as they become available.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth will be performing an emergency maintenance in the global Belgium data center.The following service will encounter interruptions during the maintenance:Messaging - VoxSMS

We experienced a brief incident with our ATL SBC that caused some dropped calls between 9:54pm and 10:01pm EDT. The SBC has recovered and the network has been stable since then.

The scheduled maintenance has been completed.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Bandwidth’s downstream vendor will be performing emergency maintenance that has the potential to affect call traffic in the Los Angeles & New York data centers.Customers that send call traffic via the internet to the Los Angeles & New York data centers may experience a brief interruption in service. Customers that connect directly to the Los Angeles & New York data centers will not be affected.

We experienced a brief impairment to the BWI network between 3:44am and 4:04am EDT through our POP in Belgium. Some calls will have experienced packet loss during the specified time window.

For a brief period of time 10DLC provisioning orders did not complete as expected. Failed orders will need be retried. At this time we are observing expected provisioning behavior.

This incident has been resolved.

Teams are currently investigating an incident impacting On-Net Port Order activations. These orders are delayed in activations.

During a brief window, some 10DLC MMS Messages did not complete as expected when delivering to the AT&T destination. At this time, messages are completing as expected.

This incident has been resolved.

Bandwidth teams are investigating an off-network incident with an industry vendor, resulting in possible delays for 10DLC Provisioning. Teams are escalating with the impaired vendor to restore expected provisioning behaviors.

This incident has been resolved.

Teams are currently investigating an off-network incident impacting Port Order Activations.

This incident has been resolved.

Teams are observing expected order activations. We will monitor for prolonged stability.

Teams have identified the source of this incident as isolated to an industry provider. We have escalated the issue and are working to bring about timely order activations.

Bandwidth teams are investigating an incident impacting Order Activations for Port Orders.

The impacted vendor has advised that work continues to restore the expected provisioning behavior. At this time, we are closing this open incident and adding this incident to our <a href="https://support.bandwidth.com/hc/en-us/articles/29835083936535-Known-Issues">Known Issues</a> page. Additional updates will be provided on the Known Issues page.

The impaired vendor has identified the source of this incident and is working to restore expected verification behavior.

The impaired vendor has identified the source of this incident and is working to restore expected verification behavior.

The impaired vendor has identified the source of this incident and is working to restore expected verification behavior.

The impaired vendor has identified the source of this incident and is working to restore expected verification behavior.

Teams are investigating an off-network incident where Toll Free Verifications are not completing as expected.

This incident has been resolved.

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

Teams continue to work to restore expected calling behavior.

Teams have identified the source of this incident, and are working to restore expected calling behaviors.

Teams are investigating and incident where outbound calls to a specific carrier are not completing as expected.

This incident has been resolved.

Teams are observing expected messaging behaviors and will continue to monitor.

Bandwidth Teams are investigating an incident impacting Toll-Free MMS, where some Toll-Free MMS messages towards AT&T may not complete as expected or be delayed in delivery.

This incident has been resolved.

The impaired vendor has identified the source of this incident and is working to restore expected verification behavior.

Teams are investigating an off-network incident where Toll Free Verifications are not completing as expected.

This incident has been resolved.

Teams are observing expected calling behavior.

Teams are currently investigating an incident in our LAX Data Center (06) where some calls transversing specific devices were disconnected.

We've confirmed stability and we're considering this incident resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We’re continuing to monitor for stability and push the carrier to confirm they have resolved the underlying issue.

The carrier has implemented a fix to increase capacity so messages are delivered on time. We’re confirming the fix is permanent and monitoring for stability.

We’ve identified an issue with ATT causing intermittent delays for SMS messages to their network. We’re directly engaged with the carrier and we’ll advise once we have further details.

We’ve confirmed stability and we’re considering this incident resolved.

We've deployed a fix and we're currently monitoring for stability.

We've identified the issue and we're working to deploy a fix.

We're currently investigating an incident with outbound call failures from the BW network. Customers are experiencing an increase in 404 failures for outbound traffic. Relevant teams are engaged.

We've confirmed stability and we're considering this incident resolved.

A fix has been implemented to correct the remaining affected TFNs on our network. We're currently monitoring the situation to confirm everything is corrected.

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

Reported numbers have been corrected at this time, but we are still working to deploy a fix for all affected numbers. That is currently scheduled for tomorrow, 4/30. Updates to follow at that time.

We’ve identified the issue and we’re in the process of deploying a fix.

We’re currently investigating an issue causing failed industry provisioning for TF numbers when they are added to BW accounts. Relevant teams are engaged.

We’ve confirmed stability and we’re considering this incident resolved.

The fix was successfully deployed and service is now working as expected. We're currently monitoring for stability.

We've identified the issue and we're working on deploying a fix.

Bandwidth Teams are investigating an incident impacting certain BXML verbs. The impacted verbs are SpeakSentence and Play Audio. These verbs may be unresponsive.

This incident has been resolved.

Teams are observing expected behavior. We I’ll monitor for prolonged stability.

Bandwidth teams are investigating an incident where 10DLC Orders are delayed as it relates to number messaging provisioning.

This incident has been resolved.

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

Teams have continued to work with the impacted vendor to restore expected MMS behavior. Additionally, this incident is only impacting a very small percentage of traffic; the vast majority of Toll Free MMS Traffic is not impacted.

Teams have continued to work with the impacted vendor to restore expected MMS behavior. Additionally, this incident is only impacting a very small percentage of traffic; the vast majority of Toll Free MMS Traffic is not impacted.

Teams have identified the source of the incident as an off network industry condition. We remain engaged with industry providers to bring about resolution.

Teams are investigating an increase of error code 4750 for Toll Free MMS messages transmitting to the AT&T network.

This incident has been resolved.

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

Teams have mitigated the issue, are observing expected SMS and MMS behavior, and have seen a reduction in errant 5620 DLR codes. Teams continue to work with the impacted parties. We will continue to monitor traffic stability.

Teams have mitigated the issue and are observing expected SMS and MMS behavior. Teams continue to work with the impacted parties. We will continue to monitor for traffic stability.

Teams continue to work towards a resolution for this incident.

Teams have identified the source of this incident and are working towards a resolution.

Teams are investigating an incident where SMS and MMS messages are failing to complete when sent to AT&T destinations.

We’ve confirmed stability and we’re considering this incident resolved.

We’ve deployed a fix and mitigated impact at this time. We’re currently monitoring for stability.

We’re currently investigating possible issues with CNAM delivery on inbound calls to the BW US network. Relevant teams are engaged.

We experienced an incident on our network that affected inbound calls in the following countries: Slovakia Greece Cyprus Czechia Bulgaria Romania Sweden Hungary Norway UK Traffic is functioning normally at this time.

We’ve confirmed stability and we’re considering this incident resolved.

Traffic has returned to normal and we’re monitoring for stability.

We’ve identified the issue and we’re working on deploying a fix.

We’re currently investigating a network issue that may be impacting both inbound and outbound voice traffic in Germany. Relevant teams are engaged.

We e confirmed stability and we’re considering this incident resolved.

Function has returned and traffic has recovered. We’re currently monitoring for stability.

We’re currently investigating an incident affecting both inbound and outbound traffic on our network in Poland. Relevant teams are engaged.

We’ve confirmed all affected TNs have been fixed and we’re considering this incident resolved.

We're still working on a fix for the underlying issue at this time. Updates to follow as they become available.

As we continue to work to resolve this incident, Toll-Free Messages are also impacted.

Teams have identified the source of this incident and are working towards restoring expected messaging behavior.

Bandwidth teams are investigating an incident where a fully provisioned number receives an errant 4740 error code. This is isolated to messages destined to the AT&T network.

This incident has been resolved.

Teams are observing expected call behavior via our ATL Data Center. We are monitoring for prolonged stability.

Bandwidth teams are investigating an incident impacting calls transversing our ATL Data Center. Calls may not set up as expected.

This incident has been resolved.

Teams are observing expected provisioning behavior. Queued requests are being processed. We will monitor for prolonged stability.

Teams have identified the source of this delay and are working to restore expected provisioning behavior.

Teams continue to investigate this provisioning delay. Requests are being queued.

Bandwidth teams are investigating an incident impacting the ability to timely provision messaging abilities to telephone numbers.

This incident has been resolved.

Teams are investigating an off-networking condition where 10DLC Campaigns are delayed in provisioning.

This incident has been resolved.

The impaired vendor has identified the source of this incident and is working to restore expected messaging behavior towards the T-Mobile network.

Bandwidth teams are investigating an off-network incident in which outbound 10DLC Messages to the T-Mobile network do not complete as expected. These messages may receive a 4773 error code despite being fully registered.

Bandwidth teams are investigating an off-network incident in which outbound 10DLC Messages to the T-Mobile network do not complete as expected. These messages may receive a 4773 error code despite being fully registered.

Bandwidth teams are investigating an off-network incident in which outbound 10DLC Messages to the T-Mobile network do not complete as expected. These messages may receive a 4773 error code despite being fully registered.

This incident has been resolved.

Teams are observing expected App behavior and will continue to monitor for stability.

Teams have identified the source of this incident and are working to restore expected Portal and API connectivity.

Bandwidth teams are investigating an incident where the Bandwidth App and associated APIs may not be responsive for users. Teams are working to restore normal App behavior.

This incident has been resolved.

Teams are observing Off-Net Port Orders completing as expected. We will monitor to ensure prolonged stability.

Bandwidth teams are investigating an incident where Off-Net Port Orders are not completing as expected.

This incident has been resolved.

We are observing expected traffic behavior and will continue to monitor.

We are currently investigating inbound call failures for China based traffic.

This incident has been resolved.

We are observing expected traffic behavior and will continue to monitor.

Teams are investigating an inbound calling calling incident impacting inbound Japan traffic.

Teams are investigating an inbound calling calling incident impacting inbound Japan traffic.

This incident has been resolved.

Teams are monitoring after a some 911 calls could not complete as expected via our DFW data center. Calls would have been successfully processed via our Geo Redundant ATL data center upon rerouting. We will continue to monitor for prolonged stability.

Note: Previous pending requests will show as pending until they expired. After which the customer will have to resubmit.

This incident has been resolved.

Teams have been advised that provisioning is completing as expected. We will monitor for prolonged stability.

Bandwidth teams are investigating an off-network incident that is impacting the ability to fully provision messaging as a line feature. Teams are working with the impacted vendor.

This incident has been resolved.

Bandwidth is observing an off-network incident with a vendor, in which 10DLC Campaign provisioning requests are delayed in completing. Teams are working with the impacted vendor.

This incident has been resolved.

Teams are investigating an incident impacting 911 provisioning only. Provisioning requests may not complete as expected.

This incident has been resolved.

Teams are observing expected provisioning behaviors and will monitor for prolonged stability.

The source of this incident has been identified, and the vendor is working to restore expected provisioning behaviors.

Teams are investigating an off-network incident impacting the ability to fully provision campaigns to numbers for messaging. Teams are working with the affected vendor to restore expected provisioning behavior.

This incident has been resolved.

Teams are investigating an incident impacting the timely responses of the Bandwidth App.

This incident has been resolved.

A fix has been deployed for affected numbers. We’re seeing that traffic has returned to expected function and we’re monitoring for stability.

At this time we have been advised that a fix for the underlying issue is scheduled for 4/2/25. We are continuing to engage with our partners to see if that can be expedited. Since we have an ETR, we'll hold further updates from here unless the ETR changes.

We're continuing to work with our partner on the issue, and they are engaged with the relevant parties. There is no ETR at this time.

We're continuing to escalate with our partner on the issue and they are engaged with the relevant parties. There is no ETR at this time.

We're continuing to escalate with our partner on the issue and they are engaged with the relevant parties. There is no ETR at this time.

We're continuing to escalate with our partner on the issue and they are engaged with the relevant parties. At this time we don’t anticipate any further updates tonight, but if we receive any, it will be passed along.

We're continuing to escalate with our partner on the issue and they are engaged with the relevant parties. There is no ETR at this time.

The issue has been identified by our partner and they are working to resolve.

We are continuing to investigate this issue.

Bandwidth teams are investigating a possible Inbound SMS and MMS Messaging incident. Inbound messaging traffic from T-Mobile is not delivering as expected, isolated to 10DLC Traffic. Teams are working to find the source of this incident.

This incident has been resolved.

Teams have identified an incident impacting a small subset of Inbound Canada that are forwarded may not complete with audio. Teams are working to restore expected calling behaviors.

We discovered the issue and successfully deployed a fix. Messaging provisioning is operating as expected at this time.

Bandwidth teams are investigating an off-network incident where messaging enablement or changes to messaging settings are not provisioning as expected. Teams have engaged the impacted vendor and are working with them to restore expected behaviors.

We’ve confirmed the underlying issue with the bind has been resolved and the bind is now back to normal function. Messages sent during the outage would be stored and retried. We’re consider g this incident resolved.

We're currently investigating an issue that caused messaging traffic to fail through our LAX datacenter. Relevant teams are engaged.

This incident has been resolved.

Teams are observing expected behavior. We will continue to monitor for prolonged stability.

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

The source of this off-network incident has been identified. The impaired vendor continues to work to restore expected behavior.

Bandwidth teams are investigating off network incident where some Messaging provisioning requests are not completed as expected. Teams are engaged with the impaired vendor.

This incident has been resolved.

Bandwidth teams have identified an Outbound Voice incident impacting global voice call completion. The impacted carrier is being removed from routes. Call may not complete as expected.