Damn, is it down?

All services / Bandwidth / Nov 9, 2026 / Evidence

Evidence

Evidence: Bandwidth, Nov 9, 2026

The raw data behind this incident page: every check we ran, the regions that failed, the error codes and the user report curve. Check our work.

Our verdict: Retracted: we published this in error. The evidence is kept here so you can see why. How we verify outages

Download JSON Download CSV Also at /api/v1/outages/1122/evidence. Free to reuse with attribution.

0 of 37Checks failed in the window
0 of 4Regions failing
—Most common error code
0Peak user reports in 15 min

Window: to . Checks from 15 minutes before the start to 15 minutes after recovery (or now). Report curve: one hour either side. Tables are in UTC.

Error codes

No failed checks with an error code in this window.

http_5xx = the site answered with that server error; timeout = no answer in time; network = the connection failed; origin_reset = the connection to the site's server was reset (HTTP 520–527) and a second fetch path got no answer either; no_status = no usable answer. Bot walls (bot_*), certificate problems on a server that answers (cert_*) and maintenance pages count as up.

Regions

  • We check from: US East, US West, Europe, Asia-Pacific.
  • Failing during this incident: none recorded.

Regional probes run from Cloudflare data centers in each region. We keep the latest regional result per region, plus a timestamped timeline entry when a region starts failing during an incident, so older incidents show the failing regions and when each was first seen, not every regional probe.

Report curve

No user reports for Bandwidth in this window.

User reports per 15-minute bucket. Counts only: no reporter identity, IP address, location or text is published. We call reports a spike at 5 or more in 15 minutes.

Raw checks

37 checks, 0 failed.

All 37 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200415 ms—scheduled
Pass200408 ms—scheduled
Pass200400 ms—scheduled
Pass200494 ms—scheduled
Pass200414 ms—scheduled
Pass200376 ms—scheduled
Pass200368 ms—scheduled
Pass200441 ms—scheduled
Pass200215 ms—scheduled
Pass200424 ms—scheduled
Pass200233 ms—scheduled
Pass200452 ms—scheduled
Pass200353 ms—scheduled
Pass200205 ms—scheduled
Pass200431 ms—scheduled
Pass200266 ms—scheduled
Pass200388 ms—scheduled
Pass200214 ms—scheduled
Pass200344 ms—scheduled
Pass200413 ms—scheduled
Pass200395 ms—scheduled
Pass200502 ms—scheduled
Pass200204 ms—scheduled
Pass200346 ms—scheduled
Pass200413 ms—scheduled
Pass200265 ms—scheduled
Pass200420 ms—scheduled
Pass200182 ms—scheduled
Pass200154 ms—scheduled
Pass200435 ms—scheduled
Pass200214 ms—scheduled
Pass200180 ms—scheduled
Pass200461 ms—scheduled
Pass200345 ms—scheduled
Pass200311 ms—scheduled
Pass200380 ms—scheduled
Pass200488 ms—scheduled

Every main HTTP check of this service in the window, oldest first: the scheduled check time, when the probe actually ran, the result, HTTP status, latency and the stored error code. A failed check is a 5xx or 408 answer, a timeout or a failed connection; bot walls and maintenance pages count as passing and are noted in passing_notes.

How to check this

  • Compare checks.rows with the outage page: the first and last failed checks bound the incident times we published.
  • error_codes counts every failed check by its stored code; recount it from checks.rows.
  • report_curve.points sum to summary.reports_in_curve; the peak is summary.peak_reports_15m.
  • Disagree? Dispute it at https://damnisitdown.com/support?dispute=1122

No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.

← Back to the incident · Methodology · Dispute this report