We started checking Bandwidth on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Bandwidth reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Bandwidth's own status page declared. Below it, any public chatter we saw about Bandwidth and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Bandwidth's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Bandwidth in the last 24 hours, which is not evidence that nothing is wrong.
Bandwidth's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Bandwidth's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Bandwidth next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
100.00%
586
US-West
100.00%
461
Europe
100.00%
417
Asia-Pacific
100.00%
253
Their declared record
Bandwidth's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Bandwidth Local Market Impairment - 248 - Richmond, VAAll systems operational
Nov 4, 2026, 5:22 AM UTC to Nov 4, 2026, 11:04 AM UTC (5h 42m)resolved
their latest update (Nov 4, 2026, 11:04 AM UTC): Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Nov 3, 2026, 2:38 PM UTC to Nov 4, 2026, 2:17 AM UTC (11h 40m)postmortem published
their latest update (Nov 5, 2026, 12:28 PM UTC): Between 13:40 UTC on November 3 and 01:00 UTC November 4, customers encountered intermittent disruption in the form of delays and expired messages for the following message types:
* Outbound 10DLC MMS to Verizon and T-Mobile Subscribers
* Outbound Shortcode MMS to Verizon, T-Mob…
Bandwidth Local Market Impairment - 246 - Culpeper, VAAll systems operational
Nov 3, 2026, 6:31 AM UTC to Nov 3, 2026, 11:26 AM UTC (4h 55m)resolved
their latest update (Nov 3, 2026, 11:26 AM UTC): Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Brussels (BRU) data center incidentMinor incident
Nov 2, 2026, 9:07 PM UTC to Nov 2, 2026, 9:07 PM UTC (0 min)postmortem published
their latest update (Nov 3, 2026, 12:52 PM UTC): Between 19:07 - 19:08 UTC on November 2, a subset of outbound calls were unable to be completed through our Brussels data center.
Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will update this post with an…
Nov 2, 2026, 8:05 PM UTC to Nov 3, 2026, 12:34 PM UTC (16h 29m)postmortem published
their latest update (Nov 5, 2026, 12:32 PM UTC): Between 13:40 UTC on November 3rd and 01:00 UTC on November 4th, outbound MMS delivery to T-Mobile and Verizon was delayed, and some messages expired before delivery. Short code MMS to AT&T was also delayed.
Bandwidth is continuing to investigate this issue to identify all acti…
Non-North American Emergency Address Validation IncidentPartial outage
Nov 2, 2026, 7:49 PM UTC to Nov 3, 2026, 3:43 AM UTC (7h 54m)postmortem published
their latest update (Nov 3, 2026, 1:13 PM UTC): Between 20:35 UTC on October 30 and 03:16 UTC November 3, customers encountered a disruption in the ability to validate non-North American addresses.
Bandwidth is continuing to investigate this issue to identify all actions necessary to prevent this from recurring and will upda…
Bandwidth Local Market Impairment - 130 - Providence, RIAll systems operational
Nov 2, 2026, 5:45 AM UTC to Nov 2, 2026, 11:14 AM UTC (5h 29m)resolved
their latest update (Nov 2, 2026, 11:14 AM UTC): Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Oct 31, 2026, 11:37 PM UTC to Nov 1, 2026, 2:19 AM UTC (2h 42m)postmortem published
their latest update (Nov 2, 2026, 1:11 PM UTC): Bandwidth has concluded its investigation of this issue and determined that between October 31 16:43 - November 1 01:04 UTC, outbound MMS messages to T-Mobile and Verizon may have encountered minimal delays in delivery.
Due to the limited scope of impact, Bandwidth is closing t…
Bandwidth Local Market Impairment - 246 - Culpeper, VAAll systems operational
Oct 30, 2026, 2:05 AM UTC to Oct 30, 2026, 12:29 PM UTC (10h 25m)resolved
their latest update (Oct 30, 2026, 12:29 PM UTC): Our carrier has completed all necessary repairs and Bandwidth can confirm all services are restored. This incident is resolved.
Showing the 10 most recent of 57 incidents Bandwidth has declared in the history we hold.
These entries are Bandwidth's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Bandwidth's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.