Damn, is it down?

All services / CDQ Cloud Services / Nov 7, 2026 / Evidence

Evidence

Evidence: CDQ Cloud Services, Nov 7, 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/1045/evidence. Free to reuse with attribution.

0 of 42Checks 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 CDQ Cloud Services 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

42 checks, 0 failed.

All 42 checks, passes included
All checks in the window
Check time (UTC)Probe ran (UTC)ResultHTTPLatencyError codeTrigger
Pass200210 ms—scheduled
Pass200277 ms—scheduled
Pass200227 ms—scheduled
Pass200191 ms—scheduled
Pass200229 ms—on demand
Pass200274 ms—scheduled
Pass200232 ms—scheduled
Pass200272 ms—scheduled
Pass200247 ms—scheduled
Pass200238 ms—scheduled
Pass200232 ms—scheduled
Pass200287 ms—scheduled
Pass200242 ms—scheduled
Pass200292 ms—scheduled
Pass200227 ms—scheduled
Pass200180 ms—scheduled
Pass200231 ms—scheduled
Pass200289 ms—on demand
Pass200328 ms—scheduled
Pass200206 ms—scheduled
Pass200217 ms—on demand
Pass200238 ms—scheduled
Pass200223 ms—scheduled
Pass200258 ms—scheduled
Pass200250 ms—on demand
Pass200192 ms—on demand
Pass200296 ms—scheduled
Pass200245 ms—scheduled
Pass200269 ms—scheduled
Pass200287 ms—scheduled
Pass200267 ms—on demand
Pass200275 ms—on demand
Pass200279 ms—scheduled
Pass200307 ms—scheduled
Pass200299 ms—scheduled
Pass200219 ms—scheduled
Pass200228 ms—scheduled
Pass200305 ms—scheduled
Pass200228 ms—scheduled
Pass200214 ms—scheduled
Pass200249 ms—scheduled
Pass200188 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=1045

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