Damn, is it down?

All services / CARE / Nov 6, 2026 / Evidence

Evidence

Evidence: CARE, Nov 6, 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/991/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 CARE 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
Pass2001727 ms—scheduled
Pass2001481 ms—scheduled
Pass200987 ms—scheduled
Pass2001401 ms—scheduled
Pass2001492 ms—scheduled
Pass2002441 ms—scheduled
Pass2001250 ms—on demand
Pass2001769 ms—scheduled
Pass2001152 ms—scheduled
Pass2001614 ms—scheduled
Pass2001162 ms—scheduled
Pass2001631 ms—scheduled
Pass2001584 ms—scheduled
Pass2001461 ms—on demand
Pass2001493 ms—scheduled
Pass2001650 ms—scheduled
Pass2001091 ms—scheduled
Pass2001363 ms—scheduled
Pass2001934 ms—scheduled
Pass2001263 ms—scheduled
Pass2002038 ms—scheduled
Pass2001682 ms—scheduled
Pass2001305 ms—scheduled
Pass2001282 ms—on demand
Pass2001069 ms—on demand
Pass2001308 ms—scheduled
Pass2001553 ms—scheduled
Pass2001523 ms—scheduled
Pass2001481 ms—scheduled
Pass2001904 ms—scheduled
Pass2001459 ms—scheduled
Pass2001916 ms—scheduled
Pass2001883 ms—scheduled
Pass2001412 ms—scheduled
Pass2001472 ms—scheduled
Pass2001350 ms—scheduled
Pass2001230 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=991

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