Damn, is it down?

All services / Cloudflare / Oct 31, 2026 / Evidence

Evidence

Evidence: Cloudflare, Oct 31, 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/1/evidence. Free to reuse with attribution.

0 of 82Checks 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 Cloudflare 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

82 checks, 0 failed.

All 82 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass20028 ms—scheduled
Pass20039 ms—scheduled
Pass200107 ms—scheduled
Pass20058 ms—scheduled
Pass200120 ms—scheduled
Pass200234 ms—scheduled
Pass200103 ms—scheduled
Pass200150 ms—scheduled
Pass200261 ms—scheduled
Pass200124 ms—scheduled
Pass20025 ms—scheduled
Pass20064 ms—scheduled
Pass20057 ms—scheduled
Pass200230 ms—scheduled
Pass200127 ms—scheduled
Pass200124 ms—scheduled
Pass20038 ms—scheduled
Pass200247 ms—scheduled
Pass200232 ms—scheduled
Pass200125 ms—scheduled
Pass20050 ms—scheduled
Pass20028 ms—scheduled
Pass200153 ms—scheduled
Pass200136 ms—scheduled
Pass20051 ms—scheduled
Pass200331 ms—scheduled
Pass200243 ms—scheduled
Pass200121 ms—scheduled
Pass200243 ms—scheduled
Pass20049 ms—scheduled
Pass200132 ms—scheduled
Pass200162 ms—scheduled
Pass200129 ms—scheduled
Pass200116 ms—scheduled
Pass200225 ms—scheduled
Pass200117 ms—scheduled
Pass200136 ms—scheduled
Pass200125 ms—scheduled
Pass20055 ms—scheduled
Pass200153 ms—scheduled
Pass200140 ms—scheduled
Pass200183 ms—scheduled
Pass200222 ms—scheduled
Pass20044 ms—scheduled
Pass200104 ms—scheduled
Pass200182 ms—scheduled
Pass200240 ms—scheduled
Pass200124 ms—scheduled
Pass200122 ms—scheduled
Pass200107 ms—scheduled
Pass20057 ms—scheduled
Pass20051 ms—scheduled
Pass20050 ms—scheduled
Pass20053 ms—scheduled
Pass200126 ms—scheduled
Pass200114 ms—scheduled
Pass200228 ms—scheduled
Pass200381 ms—scheduled
Pass200123 ms—scheduled
Pass200186 ms—scheduled
Pass200122 ms—scheduled
Pass200175 ms—scheduled
Pass200109 ms—scheduled
Pass20047 ms—scheduled
Pass20061 ms—scheduled
Pass200122 ms—scheduled
Pass200144 ms—scheduled
Pass200235 ms—scheduled
Pass20058 ms—scheduled
Pass20099 ms—scheduled
Pass200256 ms—scheduled
Pass200117 ms—scheduled
Pass200107 ms—scheduled
Pass200148 ms—scheduled
Pass200229 ms—scheduled
Pass200211 ms—scheduled
Pass200124 ms—scheduled
Pass200248 ms—scheduled
Pass20036 ms—scheduled
Pass20030 ms—scheduled
Pass20096 ms—scheduled
Pass200113 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=1

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