Checked 5 minutes ago
Nothing wrong in the last 48 hours.
Last problem before that: 8 days ago, lasting 5 min.
These are our numbers, not Chess.com's. They record whether Chess.com answered us promptly from a Cloudflare edge — which is a fact about the path between us and them as much as about them. Read it as reachability, not availability.
This longer record is here so the 48-hour picture above can mean something — without it we could tell you a problem happened, but not whether that is normal for Chess.com.
Corrected 2026-08-03. Earlier entries for Chess.com — 66 recorded problems across 18 days — were judged against a fixed response-time threshold that our own route out of Cloudflare crosses routinely. They described our path to Chess.com, not Chess.com being unavailable, and nothing stored alongside them could tell the two apart afterwards. They have been withdrawn rather than deleted, and the record here restarts from that date.
The longest outage we have on record ran 1h 5m.
The last 30 days of Chess.com, one row each.
| Day | Prompt | Reached | Checks | Started | Longest ended |
|---|---|---|---|---|---|
| 2026-09-15 so far today | 100% | 100% | 53 | none | — |
| 2026-09-14 | 100% | 100% | 287 | none | — |
| 2026-09-13 | 100% | 100% | 287 | none | — |
| 2026-09-12 | 100% | 100% | 287 | none | — |
| 2026-09-11 | 100% | 100% | 287 | none | — |
| 2026-09-10 | 100% | 100% | 287 | none | — |
| 2026-09-09 | 100% | 100% | 288 | none | — |
| 2026-09-08 | 100% | 100% | 287 | none | — |
| 2026-09-07 | 100% | 100% | 287 | none | — |
| 2026-09-06 | 99.3% | 100% | 287 | 2 | 5 min |
| 2026-09-05 | 100% | 100% | 287 | none | — |
| 2026-09-04 | 100% | 100% | 287 | none | — |
| 2026-09-03 | 100% | 100% | 287 | none | — |
| 2026-09-02 | 100% | 100% | 287 | none | — |
| 2026-09-01 | 100% | 100% | 287 | none | — |
| 2026-08-31 | 95.82% | 100% | 287 | 7 | 15 min |
| 2026-08-30 | 100% | 100% | 287 | none | — |
| 2026-08-29 | 100% | 100% | 287 | none | — |
| 2026-08-28 | 100% | 100% | 287 | none | — |
| 2026-08-27 | 96.86% | 100% | 287 | 2 | 40 min |
| 2026-08-26 | 100% | 100% | 287 | none | — |
| 2026-08-25 | 100% | 100% | 287 | none | — |
| 2026-08-24 | 100% | 100% | 287 | none | — |
| 2026-08-23 | 100% | 100% | 287 | none | — |
| 2026-08-22 | 100% | 100% | 287 | none | — |
| 2026-08-21 | 100% | 100% | 287 | none | — |
| 2026-08-20 | 100% | 100% | 288 | none | — |
| 2026-08-19 | 100% | 100% | 287 | none | — |
| 2026-08-18 | 100% | 100% | 287 | none | — |
| 2026-08-17 | 100% | 100% | 287 | none | — |
Prompt is the share of our checks Chess.com answered quickly; Reached is the share it answered at all. Both describe the path between a Cloudflare edge and them as much as they describe them. Started counts outages that began that day and Longest ended the longest that finished on it, so a problem running across midnight is counted once, on the day it began, and measured on the day it stopped.
Rows recorded before 8 August 2026 do not carry a check count — the figure was kept and the denominator was not — so their percentages are shown without one rather than with a number borrowed from somewhere else. Rows before 9 August 2026 have no Up figure either: until then we recorded only whether something was wrong, not whether it was down, and the two are different questions.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-09-06 17:05 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-09-06 16:50 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 19:45 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 19:25 UTC | 10 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 18:10 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 17:35 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 17:05 UTC | 15 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 16:05 UTC | 15 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-31 15:40 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-27 16:35 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-27 15:45 UTC | 40 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 18:50 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 18:25 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 17:50 UTC | 20 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 17:05 UTC | 10 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 16:35 UTC | 5 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 16:00 UTC | 10 min | having problems | We could not reach Chess.com promptly from our edge |
| 2026-08-05 14:35 UTC | 1h 5m | having problems | We could not reach Chess.com promptly from our edge |
Chess.com publishes no public status feed, so this entry is our own reachability probe from Cloudflare's edge rather than the vendor's view.
A green light here means we could reach chess.com, nothing more. For a turn-based site that's a reasonable proxy; for live blitz it isn't.
Status pages report the vendor's view of their own service, and they lag real
outages — often by many minutes, sometimes by hours, because a human usually has to
confirm before anything is posted. They also can't see the two things most likely to
be wrong at your end.
The first is your own connection under load. A line that idles at 20 ms can
jump to 300 ms the moment something starts uploading, which drops you from sessions
and looks exactly like a server fault. Your plan speed says nothing about this; it's
called bufferbloat and almost nobody measures it.
The second is where everyone else in your group is. A service can be healthy in your
region and unwell in theirs, and if one person is hosting, their problem is everyone's
problem.
Chess.com being fine where you are does not mean it is fine for everyone in your group. The live dashboard resolves status against each person's own region, and will tell you which of your friends is in an affected area — plus who has the connection to host, which is usually a different question from who has the fastest plan.
Worth a look when more than one thing feels broken at once: if several are genuinely down together, the fault is usually something they share rather than anything at your end. We are not claiming these particular services fail together — the live dashboard says when they actually do.