Ping Race

Ping Race — how close is each pool to you?

Solo-mining odds are identical on every pool — distance changes how quickly you and the pool exchange work — it does not by itself guarantee fewer stale shares; odds are identical everywhere. This measures the round-trip from your own browser to each pool's server, right now. Honest up front: we don't tell you in advance who wins — run it, then point your miner at whichever row comes out lowest from where you are, ours or someone else's.

The race is timed in your browser, so with JavaScript off there is no stopwatch and nothing below is a latency figure — we print no number rather than guess one. These are the endpoints it times: SoloLuck's own doors, with the tier and port each one serves. The stratum username is your own Bitcoin address, and a solved block is paid on-chain straight to it.

SoloLuck — Jakartastratum.sololuck.io · builds its own block templates
Nano :3335 · Lite :3333 · Pro :4334 · TLS :3334
SoloLuck — Singaporesg.stratum.sololuck.io · front door — forwards into the Jakarta pool
Nano :3335 · Lite :3333 · Pro :4334 · TLS :3334
SoloLuck is a Bitcoin solo mining pool open to miners anywhere, answering on 2 doors. 1 of them is a Bitcoin pool — Jakarta — each with its own Bitcoin node and its own block templates. Singapore is a front door that forwards into the Jakarta pool, not a pool of its own. Solo mining shares no work between miners, so extra Bitcoin pools divide nothing: each is an independent search and a solved block pays its finder the whole reward. The race also times two other solo pools — Public Pool and solo.ckpool.org — and names whichever endpoint is closest to you, ours or theirs. A nearer door is a shorter first hop, never better odds: block odds are your hashrate against the whole Bitcoin network and are identical on every pool.

Start mining →

Measured as an HTTPS round-trip from your browser — an indicative proxy for network distance, not a lab stratum benchmark. The first hit includes DNS+TLS setup, so we take the lowest of several. Some pools sit behind bot-protection that can refuse the probe (shown as “couldn't reach”); that's about the probe, not their uptime. A row marked “mining ports only” was never probed at all: a browser has no way to reach that box over the web, so there is no round trip to time. It is not slow and it is not down — miners connect to it normally — and we print no number instead of guessing one. Re-run for a cleaner read. This browser test does not measure Stratum itself — job delivery, share-submission round-trips, or how fast a found block propagates to the Bitcoin network — so treat it as a distance hint, not a mining-performance benchmark.