Bandwidth Status

Resolved: This incident has been resolved.

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

Investigating: Bandwidth teams are investigating an incident impacting a small subsection of customers where RTP is unavailable. Teams are actively working to restore expected RTP behavior for the impacted calls.

Resolved: This incident has been resolved.

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

Investigating: Bandwidth teams are investigating an incident impacting a small subsection of customers where RTP is unavailable. Teams are actively working to restore expected RTP behavior for the impacted calls.

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

Monitoring: Errors have resumed to normal levels and we’re monitoring for stability.

Identified: We've identified an issue causing an increase in gateway timeouts (502 and 504 errors) for outbound traffic to the BW Messaging API. Relevant teams are engaged and we'll advise once we have further details.

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

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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

Investigating: We are continuing to investigate this issue.

Investigating: 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.

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

Monitoring: Errors have resumed to normal levels and we’re monitoring for stability.

Identified: We've identified an issue causing an increase in gateway timeouts (502 and 504 errors) for outbound traffic to the BW Messaging API. Relevant teams are engaged and we'll advise once we have further details.

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

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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

Investigating: We are continuing to investigate this issue.

Investigating: 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.

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

Monitoring: Errors have resumed to normal levels and we’re monitoring for stability.

Identified: We've identified an issue causing an increase in gateway timeouts (502 and 504 errors) for outbound traffic to the BW Messaging API. Relevant teams are engaged and we'll advise once we have further details.

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

Monitoring: Errors have resumed to normal levels and we’re monitoring for stability.

Identified: We've identified an issue causing an increase in gateway timeouts (502 and 504 errors) for outbound traffic to the BW Messaging API. Relevant teams are engaged and we'll advise once we have further details.

Resolved: This incident has been resolved.

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

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

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

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

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented, and function has returned to expected levels. We're currently monitoring for stability.

Identified: We've identified the issue and we're currently working on deploying a fix. Updates to follow.

Investigating: We're currently investigating an issue causing general delays with the BW App and API. Relevant teams are engaged.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented, and function has returned to expected levels. We're currently monitoring for stability.

Identified: We've identified the issue and we're currently working on deploying a fix. Updates to follow.

Investigating: We're currently investigating an issue causing general delays with the BW App and API. Relevant teams are engaged.

Resolved: This incident has been resolved.

Identified: 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.