User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 1 hr ago. Last stored result reached it in 2238 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 15 | 0 | 0.0 | 2245 ms | 0 |
| Mon 17 | 0 | 0.0 | 2028 ms | 0 |
| Mon 19 | 0 | 0.0 | 1560 ms | 0 |
| Mon 21 | 0 | 0.0 | 1678 ms | 0 |
| Mon 23 | 0 | 0.0 | 1348 ms | 0 |
| Tue 01 | 0 | 0.0 | 1393 ms | 0 |
| Tue 03 | 0 | 0.0 | 1750 ms | 0 |
| Tue 05 | 0 | 0.0 | 1578 ms | 0 |
| Tue 07 | 0 | 0.0 | 2372 ms | 0 |
| Tue 09 | 0 | 0.0 | 1651 ms | 0 |
| Tue 12 | 0 | 0.0 | 1660 ms | 0 |
| Tue 14 | 0 | 0.0 | 1534 ms | 0 |
| Tue 16 | 0 | 0.0 | 2120 ms | 0 |
| Tue 18 | 0 | 0.0 | 1399 ms | 0 |
| Tue 21 | 0 | 0.0 | 2410 ms | 0 |
| Tue 23 | 0 | 0.0 | 2294 ms | 0 |
| Wed 01 | 0 | 0.0 | 1528 ms | 0 |
| Wed 03 | 0 | 0.0 | 2487 ms | 0 |
| Wed 06 | 0 | 0.0 | 1368 ms | 0 |
| Wed 08 | 0 | 0.0 | 2054 ms | 0 |
| Wed 10 | 0 | 0.0 | 2022 ms | 0 |
| Wed 12 | 0 | 0.0 | 2086 ms | 0 |
| Wed 14 | 0 | 0.0 | 1171 ms | 0 |
| Wed 16 | 0 | 0.0 | 1151 ms | 0 |
| Wed 18 | 0 | 0.0 | 2191 ms | 0 |
| Wed 21 | 0 | 0.0 | 2196 ms | 0 |
| Wed 23 | 0 | 0.0 | 1173 ms | 0 |
| Thu 01 | 0 | 0.0 | 2285 ms | 0 |
| Thu 03 | 0 | 0.0 | 2093 ms | 0 |
| Thu 05 | 0 | 0.0 | 2372 ms | 0 |
| Thu 07 | 0 | 0.0 | 1732 ms | 0 |
| Thu 09 | 0 | 0.0 | 2330 ms | 0 |
| Thu 11 | 0 | 0.0 | 1543 ms | 0 |
| Thu 13 | 0 | 0.0 | 1385 ms | 0 |
| Thu 15 | 0 | 0.0 | 1369 ms | 0 |
| Thu 17 | 0 | 0.0 | 1513 ms | 0 |
| Thu 19 | 0 | 0.0 | 1991 ms | 0 |
| Thu 21 | 0 | 0.0 | 1989 ms | 0 |
| Thu 23 | 0 | 0.0 | 1254 ms | 0 |
| Fri 01 | 0 | 0.0 | 2168 ms | 0 |
| Fri 03 | 0 | 0.0 | 2243 ms | 0 |
| Fri 05 | 0 | 0.0 | 1642 ms | 0 |
| Fri 07 | 0 | 0.0 | 2143 ms | 0 |
| Fri 09 | 0 | 0.0 | 2312 ms | 0 |
| Fri 11 | 0 | 0.0 | 1566 ms | 0 |
| Fri 13 | 0 | 0.0 | 1407 ms | 0 |
| Fri 15 | 0 | 0.0 | 1415 ms | 0 |
| Fri 16 | 0 | 0.0 | 2238 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Chessweb yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Chessweb goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Chessweb alerts to Slack, Discord or a webhook — free.
Chessweb is listed in our Productivity category and checked at chessweb.eu. Nederlandse webhosting met persoonlijk contact, SSL, back-ups en support van mensen die je website kennen. Bekijk de pakketten.
Chessweb publishes an official status page at status.chessweb.eu; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1874 ms average, 1254–2437 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Chessweb incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1874 ms on average over the last 24 hours (1254–2437 ms).
Yes, at https://status.chessweb.eu.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Chessweb here at once, the problem is on Chessweb's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Chessweb. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.