Bandwidth: A2P Messaging Incident
Timeline of updates
- resolved
Due to an industry condition Bandwidth teams observed a higher than normal message failure rate for A2P Messaging Traffic. Industry vendors took actions to correct and resolve this condition. After the corrective actions were taken by the industry vendor, Bandwidth Teams saw A2P message traffic restore to normal levels. This incident is considered resolved.
From Bandwidth’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.bandwidth.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Bandwidth, started 2020-07-09 04:00 UTC, resolved after 0 min, 1 update(s).
- Title
- A2P Messaging Incident
- Vendor
- Bandwidth
- Date
- URL
- https://rewindex.com/company/bandwidth/incidents/4kcn9wrz7lbm
Bandwidth profileRecent Bandwidth incidentsAll outages on July 9, 2020Bandwidth in July 2020MarkdownJSON