SoloLuck

Stratum latency benchmark: solo pools measured from Southeast Asia

SoloLuck Blog · 2026-07-01

What we measured, and why latency matters

When a new Bitcoin block is found, your pool has to push fresh work to your miner. Until that new job arrives, your miner keeps hashing on the old block — effort that can never win. That gap is stale work, and it scales with the round-trip time between you and your pool. Lower latency means less wasted hashing, and — if you ever find a block — faster propagation to the network.

To measure it honestly we timed the TCP handshake (the SYN → SYN-ACK exchange, which is one network round-trip) to each pool's stratum port, taking the median of six connections. We ran it from a normal residential connection in Indonesia (Bandung) — a real SE-Asian home miner's path — and the script is published so anyone can repeat it from their own location.

Results from a home connection in Indonesia

Median stratum round-trip, measured 2026-06-30 from Bandung, Indonesia:

Pool	Type	Latency
SoloLuck	true-solo, non-custodial	5.7 ms
public-pool.io	true-solo	250 ms
solo.ckpool.org	true-solo	260 ms
OCEAN	non-custodial pooled	280 ms
Braiins	custodial FPPS	5.1 ms*

From SE Asia, SoloLuck answers in about 6 milliseconds; the US-hosted solo pools sit at 250–280 ms — roughly 45× farther away.

The honest caveats

We would rather you trust the method than the marketing, so here is the fine print:

*Braiins also reads ~5 ms — but only because it sits behind Cloudflare's global anycast network, which has edges in Asia. Braiins is a custodial FPPS pool, not solo and not non-custodial, so it is a different product. Among true-solo, non-custodial pools, SoloLuck is the one that is physically close to Southeast Asia.
SoloLuck is hosted in the Singapore / Jakarta region, so a probe run on our own server would read ~0 ms — meaningless. That is why we report the residential-Indonesia vantage, not our own host.
This is two vantage points (Indonesia and a Singapore VPS), not a global CDN test. Your exact numbers depend on your ISP and route — which is the whole point of publishing the script.

What this means for your mining

Be clear about what latency does and does not do. It does not change your odds of finding a block — in solo mining those depend only on your hashrate versus the network. What it does is stop you wasting the hashrate you already have: every new block, you switch to fresh work sooner, so less of your machine's effort is spent on a block that is already gone.

For a single small miner the difference is modest, but it is free and it compounds over months of hashing. And on the day you do find a block, being a few hundred milliseconds closer to the network helps your block propagate before anyone else's. For a SE-Asian home miner, a pool down the street beats a pool across the Pacific.

Reproduce it yourself

Don't trust, verify. The measurement is a tiny Python script that opens a few TCP connections and times them — no mining required. Run it from your own home, point it at SoloLuck and any pool you like, and compare. If your numbers differ from ours, your route differs from ours, and that is exactly the information you want before you pick a pool.

SoloLuck stratum: stratum.sololuck.io — ports :3333 (Lite), :8081 (Standard), :4334 (Pro), :3335 (Nano), :3334 (TLS).

FAQ

Is SoloLuck really faster, or is this just marketing?

From a home connection in Southeast Asia, yes: ~6 ms to SoloLuck versus 250-280 ms to the US-hosted solo pools, measured by TCP handshake. The script is published so you can verify it from your own location.

Braiins showed ~5 ms too — isn't that the same?

Braiins is fast in Asia because it uses Cloudflare's anycast edge, but it is a custodial FPPS pool, not solo and not non-custodial. Among true-solo, non-custodial pools, SoloLuck is the one physically close to SE Asia.

Does lower latency improve my chance of finding a block?

No. In solo mining your odds depend only on your hashrate versus the network difficulty. Latency reduces wasted 'stale' work after each new block and helps your own block propagate — it stops you wasting hashrate, it doesn't add luck.

How was latency measured?

Median of six TCP-handshake round-trips (SYN to SYN-ACK) to each pool's stratum port, from a residential connection in Bandung, Indonesia, on 2026-06-30. Raw numbers and the script are public.

← All blog posts · Mining guides · Start solo mining

Ready to take a ticket?

Paste your address and copy the config from /setup, watch the pool on /status, and check every claim on /verify. Mine to your own address — that is what makes it truly solo.

Get the setup config →

Not ready to point a miner yet? Run your gear through the odds calculator, or join Telegram for block & record alerts — no rig required.

More guides

Browse all guides →