Need to monitor Bandwidth outages?
Stay on top of outages with IsDown. Monitor the official status pages of all your vendors, SaaS, and tools, including Bandwidth, and never miss an outage again.
Start Free Trial
Bandwidth teams have been advised by the impacted vendor of a prolonged complete resolution time and, as such, are closing this incident. A temporary resolution has been implemented to return (4)774 rather than (4)752.
Due to the prolonged complete resolution time given by the vendor, please visit our Known Issues support page for further details.
Bandwidth teams are investigating an incident affecting unregistered 10DLC Messaging Traffic. The affected vendor is currently blocking unregistered messaging traffic with error codes (4)750 or (4)752 instead of the expected codes (4)476 or (4)773.
To address this issue, a temporary adjustment has been implemented to return error code (4)774 instead of (4)752.
Bandwidth teams are investigating an incident affecting unregistered 10DLC Messaging Traffic. The affected vendor is currently blocking unregistered messaging traffic with error codes (4)750 or (4)752 instead of the expected codes (4)476 or (4)773.
To address this issue, a temporary adjustment has been implemented to return error code (4)774 instead of (4)752.
Bandwidth teams are investigating an incident affecting unregistered 10DLC Messaging Traffic. The affected vendor is currently blocking unregistered messaging traffic with error codes (4)750 or (4)752 instead of the expected codes (4)476 or (4)773.
To address this issue, a temporary adjustment has been implemented to return error code (4)774 instead of (4)752.
Bandwidth teams are investigating an incident affecting unregistered 10DLC Messaging Traffic. The affected vendor is currently blocking unregistered messaging traffic with error codes (4)750 or (4)752 instead of the expected codes (4)476 or (4)773.
To address this issue, a temporary adjustment has been implemented to return error code (4)774 instead of (4)752.
Bandwidth teams continue investigating this incident affecting Unregistered 10DLC Messaging Traffic. The impaired vendor is currently blocking unregistered messaging traffic with error codes (4)750 or (4)752 instead of the expected codes (4)476 or (4)773.
To mitigate this issue, a temporary adjustment has been made to return error code (4)774 instead of (4)752
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
At this time, a temporary change has been implemented to return (4)774 rather than (4)752.
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
At this time, a temporary change has been implemented to return (4)774 rather than (4)752.
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
At this time, a temporary change has been implemented to return (4)774 rather than (4)752.
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
Bandwidth teams continue to investigate this incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes.
Teams are actively working with the impaired vendor to restore expected error codes.
Bandwidth teams continue to investigate this incident in partnership with the impacted vendor.
Bandwidth teams continue to investigate this incident in partnership with the impacted vendor.
Bandwidth teams continue to investigate this incident.
Bandwidth teams continue to investigate this incident.
Bandwidth teams have identified an incident impacting Unregistered 10DLC Messaging Traffic. Unregistered messaging traffic is being blocked with error codes (4)750 or (4)752 rather than the expected (4)476 or (4)773 codes. Teams are actively working to ensure the correct error code is provided for Unregistered 10DLC Traffic blocking.
Additional details on 10DLC Registration can be found on our support site.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 3729 services available
Integrations with