# Bandwidth: Inbound Calling Incident

**Deleted by the vendor** (gone from the status page since 2026-10-20 01:13 UTC). The content below is the last version Rewindex archived.

- Impact (vendor’s label): none
- Status: postmortem
- Started: 2026-10-02 03:30 UTC · Resolved: 2026-10-02 03:30 UTC · Duration: 0 min
- Updates: 2
- [Vendor status page: https://stspg.io/8jrbpr445t7s](https://stspg.io/8jrbpr445t7s)
- [Company: Bandwidth](https://rewindex.com/company/bandwidth.md)

## Timeline of updates

- **resolved** 2026-10-02 03:30 UTC: During a scheduled maintenance window, inbound calls for some customers did not deliver as expected. These calls failed to complete as expected during the impact window. We have since observed expected network behavior, and consider this incident resolved.
- **postmortem** 2026-10-07 08:25 UTC: Between 03:15 UTC and 03:30 UTC on October 2nd, inbound voice calls were unable to be completed.  Bandwidth has concluded its investigation of this issue and details can be found in the following Incident Report: \[https://www.bandwidth.com/support/en/articles/17429376-20261002-voice-inbound-proxy-403-rejections-during-acl-reload-window\](https://www.bandwidth.com/support/en/articles/17429376-20261002-voice-inbound-proxy-403-rejections-during-acl-reload-window). 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.

## Rewindex changes for this incident

- 2026-10-20 01:13 UTC: [Incident deleted: Inbound Calling Incident](https://rewindex.com/change/d46d3a8b7b5512e.md)


---
Canonical: https://rewindex.com/company/bandwidth/incidents/p7cfm049pdgs · Markdown: https://rewindex.com/company/bandwidth/incidents/p7cfm049pdgs.md · JSON: https://rewindex.com/api/v1/companies/bandwidth/incidents/p7cfm049pdgs · Generated 2026-10-20T01:30:49.323Z