Checked 1 minutes ago
2 separate problems in the last 48 hours, most recently 8 hours ago.
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.
The longest outage we have on record ran 3h 45m. We have only been recording Chess.com for 3 days, so treat these figures as provisional.
| Started | Lasted | Severity | What happened |
|---|---|---|---|
| 2026-08-01 20:30 UTC | 1h 35m | having problems | We measured HTTP 200 in 3085 ms from the edge |
| 2026-08-01 16:40 UTC | 3h 45m | having problems | We measured HTTP 200 in 3304 ms from the 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.