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
Error code
Failed checks
http_530
151
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: Asia-Pacific, US East, Europe, US West.
: Failing from Asia-Pacific, US East, Europe, US West.
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
User reports per 15 minutes (peak 1). Times are ET.Report counts per 15 minutes (1 non-zero buckets)
15 minutes from (UTC)
Reports
1
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
154 checks, 151 failed (first , last ).
Failed checks
Failed checks
Check time (UTC)
Probe ran (UTC)
Result
HTTP
Latency
Error code
Trigger
Fail
530
15 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
38 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
30 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
72 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
28 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
54 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
42 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
7 ms
http_530
scheduled
Fail
530
67 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
79 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
23 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
98 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
103 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
47 ms
http_530
scheduled
Fail
530
40 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
90 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
59 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
23 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
20 ms
http_530
scheduled
Fail
530
50 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
24 ms
http_530
scheduled
Fail
530
44 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
97 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
3 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
46 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
24 ms
http_530
scheduled
Fail
530
104 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
63 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
21 ms
http_530
scheduled
Fail
530
121 ms
http_530
scheduled
Fail
530
20 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
151 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
59 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
15 ms
http_530
on demand
Fail
530
19 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
38 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
29 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
7 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
27 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
21 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
73 ms
http_530
scheduled
Fail
530
33 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
All 154 checks, passes included
All checks in the window
Check time (UTC)
Probe ran (UTC)
Result
HTTP
Latency
Error code
Trigger
Fail
530
15 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
38 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
30 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
72 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
28 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
54 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
42 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
7 ms
http_530
scheduled
Fail
530
67 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
79 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
23 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
98 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
103 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
47 ms
http_530
scheduled
Fail
530
40 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
90 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
59 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
23 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
20 ms
http_530
scheduled
Fail
530
50 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
24 ms
http_530
scheduled
Fail
530
44 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
97 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
3 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
46 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
24 ms
http_530
scheduled
Fail
530
104 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
8 ms
http_530
scheduled
Fail
530
63 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
21 ms
http_530
scheduled
Fail
530
121 ms
http_530
scheduled
Fail
530
20 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
151 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
59 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
9 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
10 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
17 ms
http_530
scheduled
Fail
530
6 ms
http_530
scheduled
Fail
530
14 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
15 ms
http_530
on demand
Fail
530
19 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
15 ms
http_530
scheduled
Fail
530
38 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
29 ms
http_530
scheduled
Fail
530
19 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
7 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
27 ms
http_530
scheduled
Fail
530
13 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
21 ms
http_530
scheduled
Fail
530
11 ms
http_530
scheduled
Fail
530
18 ms
http_530
scheduled
Fail
530
16 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Fail
530
73 ms
http_530
scheduled
Fail
530
33 ms
http_530
scheduled
Fail
530
12 ms
http_530
scheduled
Pass
200
165 ms
—
scheduled
Pass
200
175 ms
—
scheduled
Pass
200
297 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=1411
No personal data: no reporter identities, IP addresses, emails, report text or reporter locations. User reports are aggregate 15-minute counts.
We use Microsoft Clarity (session recording: clicks, scrolls and page content) and Google Analytics to understand how the site is used. Clarity only runs if you allow it. No ads, and we never sell your data.