The primary purpose of this tool is to help you decide which Stratum endpoints to put into your miner's configuration. Network conditions fluctuate, so we recommend the following professional strategy:
For advanced users managing large farms, we also recommend using Smart Stratum Proxies to handle failover and aggregation automatically.
Stratum Pool Pinger is a browser-based latency measurement tool for Bitcoin miners. It helps you identify the fastest Stratum endpoints for your mining hardware by measuring real-time network proximity from your location. Unlike pool selection based on geographic guesswork, this tool provides actual RTT measurements to make data-driven configuration decisions.
Most miners choose pools based on advertised server locations or general advice like "use the closest region." However, actual network latency depends on ISP routing, peering agreements, and real-time congestion—not just physical distance.
Testing latency manually via command-line tools requires technical expertise and doesn't reflect the exact path your browser (or farm router) will take. This tool bridges that gap by measuring latency directly from your browser environment, giving you actionable data for configuring your ASICs.
The Stratum Pool Pinger uses a technique called "Cross-Origin Latency Measurement." Since browsers cannot open raw TCP sockets to port 3333, we initiate high-frequency network requests and measure the time it takes for the connection to fail or timeout. Read more in our Methodology Guide.
The tool initiates CORS-preflight requests (OPTIONS) and measures the time-to-fail for TCP connection attempts on Stratum ports (3333, 443, 25, etc.). While browsers block raw socket access, the connection setup timing accurately reflects network RTT up to the pool's gateway.
A 10-sample moving average filters out transient jitter, and endpoints with sub-9ms responses are flagged as likely "Connection Refused" (indicating closed ports or local network responses).
In Bitcoin mining, latency is everything. Every millisecond of delay between your miner and the pool increases the probability of submitting a stale share — a valid solution that arrives after the pool has already started a new block. See our Latency Optimization Guide for details.
A reduction of 50ms in latency can often result in a 0.5% - 1.0% increase in effective hashrate and revenue.
Real-world example: A 100 TH/s farm mining at $0.08/kWh with 50ms average latency to the pool might see 0.5-1.0% stale share rate. Reducing latency to 20ms can cut stales to 0.2-0.3%, recovering approximately $15-30 per month per 100 TH/s—enough to cover operational expenses or reinvest in expansion.
If latency is below 9ms, it's usually a "Connection Refused" error happening too fast, indicating the port is closed or blocked.
Generally, pick the one with the lowest stable latency (colored green). Consistency is as important as speed.
Browser-based measurements reflect the actual network path from your current location. While they cannot perform full Stratum handshakes (due to browser security), the RTT correlates strongly (>95%) with actual mining latency, as both use the same ISP routing.
Ideally, test from the same network as your mining hardware. If your farm is in a data center, use a browser on that network or a VPN to that location for the most accurate results.
Under 100ms is excellent, 100-200ms is acceptable for most pools, and above 300ms should be avoided if better options exist.