All services / Fahrrad XXL / Nov 6, 2026 / Evidence
Evidence: Fahrrad XXL, 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/998/evidence. Free to reuse with attribution.
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 Fahrrad XXL 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
38 checks, 0 failed.
All 38 checks, passes included
| Check time (UTC) | Probe ran (UTC) | Result | HTTP | Latency | Error code | Trigger |
|---|---|---|---|---|---|---|
| Pass | 200 | 1447 ms | — | scheduled | ||
| Pass | 200 | 1253 ms | — | scheduled | ||
| Pass | 200 | 1278 ms | — | scheduled | ||
| Pass | 200 | 1411 ms | — | scheduled | ||
| Pass | 200 | 1544 ms | — | scheduled | ||
| Pass | 200 | 754 ms | — | scheduled | ||
| Pass | 200 | 665 ms | — | scheduled | ||
| Pass | 200 | 1497 ms | — | scheduled | ||
| Pass | 200 | 1225 ms | — | on demand | ||
| Pass | 200 | 1432 ms | — | scheduled | ||
| Pass | 200 | 1019 ms | — | scheduled | ||
| Pass | 200 | 838 ms | — | scheduled | ||
| Pass | 200 | 1112 ms | — | scheduled | ||
| Pass | 200 | 1286 ms | — | scheduled | ||
| Pass | 200 | 895 ms | — | scheduled | ||
| Pass | 200 | 1380 ms | — | scheduled | ||
| Pass | 200 | 1195 ms | — | scheduled | ||
| Pass | 200 | 864 ms | — | scheduled | ||
| Pass | 200 | 1287 ms | — | scheduled | ||
| Pass | 200 | 751 ms | — | on demand | ||
| Pass | 200 | 1115 ms | — | on demand | ||
| Pass | 200 | 833 ms | — | scheduled | ||
| Pass | 200 | 1334 ms | — | scheduled | ||
| Pass | 200 | 1020 ms | — | scheduled | ||
| Pass | 200 | 775 ms | — | scheduled | ||
| Pass | 200 | 1362 ms | — | scheduled | ||
| Pass | 200 | 792 ms | — | scheduled | ||
| Pass | 200 | 882 ms | — | scheduled | ||
| Pass | 200 | 902 ms | — | on demand | ||
| Pass | 200 | 1432 ms | — | scheduled | ||
| Pass | 200 | 893 ms | — | on demand | ||
| Pass | 200 | 769 ms | — | on demand | ||
| Pass | 200 | 1442 ms | — | scheduled | ||
| Pass | 200 | 381 ms | — | scheduled | ||
| Pass | 200 | 1328 ms | — | scheduled | ||
| Pass | 200 | 849 ms | — | scheduled | ||
| Pass | 200 | 692 ms | — | scheduled | ||
| Pass | 200 | 730 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=998
No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.