System status
Is everything running?
A live, plain-language view of the systems behind Chessco and how the 24-ply launch fill is tracking. Each subsystem shows a status, not its internals. Deeper operational detail stays in the private ops dashboard.
Some systems need review.
checked
Subsystems
What the colors mean
- Operating normally
- Healthy and inside every threshold. Nothing to do.
- Working / informational
- A job is actively running or a routine note. Nothing is wrong.
- Needs review
- A soft limit was crossed. It usually clears on its own; worth a glance.
- Needs immediate attention
- A hard limit was crossed and a person may need to step in.
24-ply launch readiness
On trackWith acceleration: Beta Jul 13, 2026 to Jul 13, 2026; Public Aug 21, 2026 to Sep 29, 2026.
Beta · fast retrieval layer
FillingPublic · adaptive reliability layer
Pre-gateBeta and Public with acceleration
Acceleration is the operating assumption, not a fallback scenario.
Use this as the real expectation for Beta and Public readiness. The raw current-cadence projection is folded below only as a warning line for what would happen if we stopped accelerating.
Real ETA: Beta Jul 13, 2026 to Jul 13, 2026; Public Aug 21, 2026 to Sep 29, 2026.
Beta with acceleration
Jul 13, 2026 to Jul 13, 2026
Acceleration stays on. Remaining: 0 accounts.
Public with acceleration
Aug 21, 2026 to Sep 29, 2026
Acceleration stays on. Remaining: 232,667 accounts.
Accelerated launch timeline
Open by default because this is the plan we are actually running.
Today
Jul 13, 2026
reached
Beta with acceleration
Jul 7, 2026
reached
Public with acceleration
Aug 21, 2026
~39 days out
Real expectation: Beta Jul 13, 2026 to Jul 13, 2026; Public Aug 21, 2026 to Sep 29, 2026. This is based on the recovery speeds we have actually seen from manual Lichess sweeps, safe Chess.com canaries, and repeated graph catch-up.
Beta operating window
Expected range: Jul 13, 2026 to Jul 13, 2026
Internal target: Jul 7, 2026
Remaining: 0 accounts.
Realistic operating pace: 8,000-15,000/day. Target pace needed: 0/day.
Operator forecast from proven manual Lichess sweep yield, safe Chess.com API canaries, and planned fast-layer acceleration.
Why this is the real estimate
- Manual Lichess month sweeps proved that tens of thousands of fast-layer accounts can be recovered in bounded runs when a fresh month has yield.
- The Chess.com API lane has run with zero 429s in canaries; current recurring batches are safe but intentionally throttled.
- The graph writer is not the main limiter for Beta once source rows exist; bounded catch-up has repeatedly cleared the source-ready tail.
Main risk: If no new high-yield Lichess month or Chess.com ramp is opened, the raw current-cadence diagnostic is the fallback path and Beta slips.
Public operating window
Expected range: Aug 21, 2026 to Sep 29, 2026
Internal target: Aug 21, 2026
Remaining: 232,667 accounts.
Realistic operating pace: 3,000-6,000/day. Target pace needed: 5,974.27/day.
Operator forecast for the stronger adaptive/final reliability claim after Beta, assuming cache reuse and final certification lanes continue improving.
Why this is the real estimate
- The fast layer preserves the map and cache needed to prioritize adaptive certification instead of starting the Public layer cold.
- The final layer is deliberately stricter: it counts fixed 36-month or 5,000-game evidence plus adaptive-certified rows with matching source and graph checksums.
- High-demand and top-ranked uncertified accounts can be promoted from Beta cache into deeper certification lanes after Beta opens.
Main risk: Public readiness depends on sustained adaptive certification after Beta; it is not the same thing as the fast 120-game retrieval fill.
Operating ETAs are the real expectation based on recovery speeds we have already proven and acceleration lanes we are actively operating. Raw current-cadence ETAs remain a diagnostic for what happens if acceleration stops.
Current bottleneck
Source refresh throughput is the current Beta bottleneck.
Graph: Graph catch-up is productive, but larger local all-platform passes can run long; use smaller bounded passes or the Cloud Run graph lane for tails.
Source: Recent movement is mostly chess.com API recovery plus small graph tails; stored-only probes found very little new source inventory and Lichess stayed flat.
Next speed-up: Continue the safer Chess.com API ramp with runtime-budget cooldowns, and prepare a reviewed Lichess month sweep. More graph tuning or stored-only probing alone will not hit the Beta pace.
Caution: Keep Public reliability separate from Beta: final certification still needs adaptive 36-month or 5,000-game evidence.
Show stop-acceleration diagnostic
Raw current-cadence diagnostic only
Raw projection from +-7 Beta / day, +0 Public / day over the last 0.3 days if acceleration stopped. We are not planning to stop acceleration, so this stays collapsed as a diagnostic, not the real ETA.
Today
Jul 13, 2026
reached
Beta only if acceleration stopped
Pending
measuring fill rate
Public only if acceleration stopped
Pending
sustained fill cadence not yet established
Full fill detail and methodology is on the benchmarks page.
Deep search (24-ply) rollout
Scout currently matches openings to 12 plies. Deeper 24-ply matching ships in three steps: rebuild the account index month by month, verify accuracy against the 12-ply baseline, then enable the deeper search. Search keeps working throughout; coverage grows as months complete.
Step 1 · Account index: 24 of 24 months
100%
Health snapshot:
Launch fill:
Times shown in your local clock. This page refreshes continuously.