Bandwidth Status

Postmortem: Bandwidth has concluded its investigation of this issue and determined that between January 16 - January 19, Bandwidth customers observed a small percentage of outbound 10DLC, Shortcode, SMS, MMS messages receive errors and ultimately fail to deliver to Verizon subscribers.

Due to the limited scope of impact and that this issue was isolated to a problem outside of Bandwidth’s network, 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.

Resolved: This incident has been resolved.

Monitoring: Teams are observing expected messaging behavior, we remain engaged with the impacted industry provider, and will monitor for stability.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected. Teams remained engaged with industry partners.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected.

Investigating: Bandwidth teams continue to investigate an off network incident impacting outbound messages to the Verizon destinations. Customers will see messages fail with a 4720 error code.

Investigating: Bandwidth teams are investigating an off-network incident where we are observing an increase in 4720 messaging error codes. These error codes are intermittent at this time.

Postmortem: Bandwidth has concluded its investigation of this issue and determined that between January 16 - January 19, Bandwidth customers observed a small percentage of outbound 10DLC, Shortcode, SMS, MMS messages receive errors and ultimately fail to deliver to Verizon subscribers.

Due to the limited scope of impact and that this issue was isolated to a problem outside of Bandwidth’s network, 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.

Resolved: This incident has been resolved.

Monitoring: Teams are observing expected messaging behavior, we remain engaged with the impacted industry provider, and will monitor for stability.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected. Teams remained engaged with industry partners.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected.

Investigating: Bandwidth teams continue to investigate an off network incident impacting outbound messages to the Verizon destinations. Customers will see messages fail with a 4720 error code.

Investigating: Bandwidth teams are investigating an off-network incident where we are observing an increase in 4720 messaging error codes. These error codes are intermittent at this time.

Postmortem: Bandwidth has concluded its investigation of this issue and determined that between January 16 - January 19, Bandwidth customers observed a small percentage of outbound 10DLC, Shortcode, SMS, MMS messages receive errors and ultimately fail to deliver to Verizon subscribers.

Due to the limited scope of impact and that this issue was isolated to a problem outside of Bandwidth’s network, 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.

Resolved: This incident has been resolved.

Monitoring: Teams are observing expected messaging behavior, we remain engaged with the impacted industry provider, and will monitor for stability.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected. Teams remained engaged with industry partners.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected.

Investigating: Bandwidth teams continue to investigate an off network incident impacting outbound messages to the Verizon destinations. Customers will see messages fail with a 4720 error code.

Investigating: Bandwidth teams are investigating an off-network incident where we are observing an increase in 4720 messaging error codes. These error codes are intermittent at this time.

Postmortem: Bandwidth has concluded its investigation of this issue and determined that between January 16 - January 19, Bandwidth customers observed a small percentage of outbound 10DLC, Shortcode, SMS, MMS messages receive errors and ultimately fail to deliver to Verizon subscribers.

Due to the limited scope of impact and that this issue was isolated to a problem outside of Bandwidth’s network, 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.

Resolved: This incident has been resolved.

Monitoring: Teams are observing expected messaging behavior, we remain engaged with the impacted industry provider, and will monitor for stability.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic. Bandwidth continues to engage with this industry partner to restore expected messaging behavior.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident, however we are observing a very low impact on messaging traffic.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected. Teams remained engaged with industry partners.

Identified: Bandwidth teams have identified the source of this incident as an off-network incident. Messages to Verizon destinations continue to not process as expected.

Investigating: Bandwidth teams continue to investigate an off network incident impacting outbound messages to the Verizon destinations. Customers will see messages fail with a 4720 error code.

Investigating: Bandwidth teams are investigating an off-network incident where we are observing an increase in 4720 messaging error codes. These error codes are intermittent at this time.

Postmortem: Between February 4 16:08 - February 5 11:35 UTC, 10DLC provisioning requests were unable to be completed.

Bandwidth is continuing to investigate this issue to identify the root cause and 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.

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

Investigating: Teams are incident where TNs are not fully provisioned when attached to a 10DLC Campaign dispute order completion status. Teams are working to restore expected behavior.