# Bandwidth: Possible MMS Failed Deliveries

> Bandwidth status incident “Possible MMS Failed Deliveries” on 2022-06-13: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb
Last updated: 2022-06-13T21:00:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2022-06-13 21:00 UTC · Resolved: 2022-06-13 21:00 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://status.bandwidth.com/incidents/7qlnvjyx2hmb](https://status.bandwidth.com/incidents/7qlnvjyx2hmb)
- [Company: Bandwidth](https://rewindex.com/company/bandwidth.md)

## Timeline of updates

- **resolved** 2022-06-13 21:00 UTC: Queuing of MMS with a routing vendor caused a failover between 5:05-5:06 PM ET. This could have caused delays starting around 4:48PM ET, as well as a short point of failed 10 DLC MMS, P2P MMS, and some TF MMS during the moment of fail over. Messages received during the outage would have failed and need to be resent.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## Cite this

Status incident (vendor impact label: none) posted by Bandwidth, started 2022-06-13 21:00 UTC, resolved after 0 min, 1 update(s).

- Canonical URL: https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb
- Citation: Bandwidth, “Possible MMS Failed Deliveries” (2022-06-13 21:00 UTC). Archived by Rewindex: https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb (CC BY 4.0).
- Markdown link: `[Bandwidth: Possible MMS Failed Deliveries (2022-06-13)](https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb)`


---
Canonical: https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb · Markdown: https://rewindex.com/company/bandwidth/incidents/7qlnvjyx2hmb.md · JSON: https://rewindex.com/api/v1/companies/bandwidth/incidents/7qlnvjyx2hmb · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:59:08.473Z
