Bandwidth: SLA evidence report
Bandwidth: SLA evidence report
We only started checking Bandwidth on 2026-11-02, so the window starts there.
We hold no probe record for Bandwidth: we read its status page, so the only incident record here is what Bandwidth declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Bandwidth declared
- 5
- On its own status page, in this window.
- Window
- 2026-11-02 to 2026-11-06
- UTC, 4 days.
Nov 2, 2026, 7:49 PM UTC to Nov 3, 2026, 3:43 AM UTC
Non-North American Emergency Address Validation Incident, impact major
Nov 2, 2026, 8:05 PM UTC to Nov 3, 2026, 12:34 PM UTC
Outbound 10DLC MMS Delivery Incident, impact minor
Nov 2, 2026, 9:07 PM UTC to Nov 2, 2026, 9:07 PM UTC
Brussels (BRU) data center incident, impact minor
Nov 3, 2026, 2:38 PM UTC to Nov 4, 2026, 2:17 AM UTC
Outbound 10DLC MMS Delivery Incident - T-Mobile, Verizon, AT&T, impact major
Nov 3, 2026, 10:59 PM UTC to Nov 4, 2026, 4:07 AM UTC
Voice Authentication Incident - Pindrop, impact major
Methodology
These incidents come from Bandwidth's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Bandwidth owes, if any, is decided under its own SLA.