Inbound Calling Incident
Incident
Report for Bandwidth
Postmortem
Between July 9 13:30 - July 11 20:30 UTC, inbound calls from AT&T to a small subset of Bandwidth numbers were unable to be completed.
Bandwidth has concluded its investigation of this issue and details can be found in the following Incident Report:
Please note that this link will remain active for 30 days. To access the Incident Report after 30 days, a request for the report can be made 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
This vendor has advised Bandwidth that they have resolved an industry condition impacting these call types. Bandwidth will monitor for prolonged stability.
Update
Bandwidth teams have identified the source of this incident as an off-network industry condition. We remain engaged with our vendors to bring about calling restoration. Updates will be provided as they become available.
Update
Bandwidth teams have identified the source of this incident as an off-network industry condition. We remain engaged with our vendors to bring about calling restoration. Updates will be provided as they become available.
Identified
Bandwidth teams have identified the source of this incident as an off-network industry condition. We remain engaged with our vendors to bring about calling restoration.
Investigating
Bandwidth is investigating an incident in which inbound calls from the AT&T Network, whose destination is an off-network Bandwidth number, may not be complete as expected.
This incident affected: United States Inbound Calling Services (Inbound Calling (SIP) - United States, REST APIs - HTTP Voice - United States, REST APIs - SIP Voice - United States, BXML - United States).