Internet for Bitcoin Mining: Latency, Stale Shares, and Why Bandwidth Doesn't Matter

Beyond electricity and hardware processing power, internet performance is one of the most critical aspects of Bitcoin mining. Mining relies on continuous communication between hardware and the Bitcoin network.

For efficient mining operations, low-latency and stable internet connectivity are essential. Because mining traffic is minimal, bandwidth is rarely a limiting factor. A bandwidth of around 1–2 megabits per second (Mbps) per ASIC miner is generally sufficient.

Latency, typically measured using a ping test, should generally remain below 100 milliseconds (ms), with values between 20 and 50 ms preferred for more stable and responsive communication with mining pools. This article breaks down the internet requirements for efficient Bitcoin mining and common network mistakes.

Key takeaways

• In crypto mining, latency refers to how quickly mining hardware communicates with a pool server — the lower the delay, the faster shares are submitted and new work is received.
• When network delays occur, valid mining results can arrive too late and become stale shares, which means no reward is received for that work. Consistent uptime paired with low mining pool latency helps prevent stale shares during network congestion.
• Mining latency is typically measured by running a ping test to the selected pool server. Values below 50 milliseconds indicate a stable connection, while latency above 100 milliseconds increases the risk of stale shares.
• Internet Control Message Protocol (ICMP) ping measures basic network reachability, while Stratum-level latency reflects real mining communication between ASIC hardware and pool servers, providing a more accurate view of operational performance.

How mining pool latency affects mining performance

Most Bitcoin mining today operates through mining pools rather than fully independent (solo) mining. In pool-based mining, miners continuously exchange small data packets to submit shares and receive new work, making network responsiveness an important factor in overall efficiency. In comparison, solo mining involves less frequent communication, so network performance plays a comparatively smaller role in day-to-day operations.

Mining payouts depend on the fast and consistent submission of valid shares. Each time an ASIC miner finds a potential solution to the cryptographic puzzle, it must be transmitted to the pool as quickly as possible. Lower latency improves the likelihood that the share will be accepted and properly credited.

Latency depends on several factors, including the physical distance between the miner and the pool server, the quality of the internet connection, pool server load and architecture, overall network congestion, and routing efficiency between internet service providers.

Why do stale shares reduce profitability?

A stale share occurs when a valid solution is submitted after the mining pool has already issued a new block or updated mining job. Although the computation itself is correct, the share becomes outdated and is rejected due to timing.

• Zero payout for stale shares: Pools distribute mining rewards based on valid contributions toward the current block. Since stale shares arrive too late, they are rejected by the pool and generate no payouts under common reward models such as Full Pay Per Share (FPPS) or Pay Per Last N Shares (PPLNS).
• Wasted electricity costs: ASIC miners consume the same amount of power regardless of whether shares are accepted or stale, meaning energy is spent without generating any return.
• Lower effective hashrate: A higher stale share rate reduces effective mining performance, lowering overall efficiency and the earnings reflected in pool dashboards.

Bandwidth myth: Why gigabit internet isn't needed for Bitcoin mining

One of the most common misconceptions in cryptocurrency mining is that high bandwidth is required for efficient operation. In reality, steady-state mining generates very little network traffic, regardless of hardware power or miner model. A top-tier machine, such as an Antminer S21 XP, produces the same minimal amount of network data as an older model.

Whether operating a single miner or thousands of devices in a mining farm, network traffic does not scale in a way that requires high bandwidth. Major ASIC manufacturer Bitmain states in its documentation that a computing power center running 3,000 servers can operate on a 20 Mbps connection.

Instead, latency and reliable connection have a far greater impact on performance than raw bandwidth. Mining traffic typically consists of small, frequent share submissions, while unstable routing or connection drops are far more likely to reduce efficiency through stale shares and rejected work.

Key network metrics in crypto mining: ping, jitter, and packet loss

Ping, jitter, and packet loss are core metrics that describe how quickly and reliably data travels between mining hardware and external servers such as mining pools or network nodes. These metrics directly affect the number of stale shares and overall profitability.

Ping — a tool used to measure network latency

Ping is a testing method used to measure round-trip time, indicating how long it takes data to travel between an ASIC miner and a mining pool server and back. The concept is closely related to latency, since both describe network delay.

Latency is the time it takes for data to move between two points. Ping is a tool used to measure this delay, and is typically shown in milliseconds. Lower ping means faster communication and more reliable share submission.

The ideal ping is below 50 ms. While anything under 100 ms is functional, crossing the 150 ms threshold typically leads to an increased stale share rate. Ping can be tested on a computer by running a simple command in the terminal or command prompt using the mining pool server address. This command returns the response time in milliseconds.

Jitter — the consistency of connection speed

Jitter refers to the inconsistency of network response times. The metric is calculated by measuring the variation between consecutive ping results.

High jitter introduces unpredictability into the mining process. While one block template may arrive instantly, the next may be delayed due to temporary network congestion, reducing overall efficiency.

A reliable internet service typically helps keep jitter low, while an unstable connection that rapidly fluctuates between low and high response times (e.g., jumping from 30 ms to 200 ms and back) is considered to have high jitter.

Packet loss — the reliability of data delivery

Data travels across the internet in small fragments called “packets.” Packet loss occurs when one or more of these packets fail to reach their destination. If an ASIC solves a cryptographic puzzle and submits a share to the pool, but the packet is lost in transit, the pool server never receives the work.

Even if the data is resent, the delay may mean that the mining pool has already switched to a new block template. In that case, the late submission is rejected as stale due to delivery timing.

Even a small packet loss rate (for example, 1%) can noticeably reduce effective hashrate at the pool level. Packet loss is typically measured using network tools that send a set of test packets to a destination server and measure how many successfully return.

Technical benchmarks for mining connectivity

Efficient mining requires strong performance across ping, jitter, and packet loss. The table below outlines key benchmarks and their impact on ASIC mining performance.

How to test mining pool latency accurately

Mining pool latency differs from other types of internet latency, such as gaming or regular website browsing, because Bitcoin mining relies on continuous machine-to-machine communication.

Mining pool infrastructure communicates over different protocol layers than standard web traffic, which means a regular ping test will deliver incomplete results. To measure latency accurately, it is important to understand how mining network communication works and apply the corresponding measurement methods.

Stratum-level ping: A more accurate way to test mining latency

Standard network testing relies on ICMP. While a standard ICMP ping measures basic network routing, it only confirms whether a server is reachable and responsive to ICMP requests. A mining pool server may respond instantly at this level while still experiencing application-level delays in job delivery or share acceptance.

Because mining efficiency depends heavily on the application layer, measuring communication between the hardware and the pool's mining software is essential. Most pools rely on the Stratum protocol, which operates over Transmission Control Protocol (TCP) to maintain a persistent, bi-directional connection between ASIC miners and pool infrastructure.

Instead of focusing on simple network reachability, Stratum-level ping measures the real round-trip time of an actual mining workload. This includes the time required for the pool’s software to receive, process, and validate a submitted share, offering a more accurate reflection of real-world mining latency.

Mining pool latency tests are performed using specialized tools such as a stratum-ping tool or directly via mining hardware.

Modern ASIC firmware—both factory software and custom platforms such as Braiins OS or Vnish—continuously monitors protocol-level metrics, allowing miners to review performance data directly in the device dashboard.

Wired Ethernet vs Wi-Fi for mining operations

Wired Ethernet and Wi-Fi are two common ways mining hardware connects to the internet. Both allow mining rigs to communicate with mining pools, receive work, and submit completed shares.

Ethernet uses a physical cable connecting mining equipment directly to the network, creating a stable and predictable connection. Wi-Fi transmits data wirelessly, making setup easier and more flexible but also more susceptible to walls, interference, and distance from the router.

In mining operations where consistency matters more than convenience, Ethernet is generally preferred due to its stable performance and fewer interruptions. Wi-Fi is more prone to fluctuations, which can lead to delayed or missed share submissions.

Regional pool endpoints and why geography matters

Mining pools operate multiple regional endpoints to reduce communication delays between ASIC miners and pool servers. Each endpoint represents a different server location, allowing hardware to connect to the nearest available node. Shorter distance reduces latency and improves the speed of job delivery and share submission.

Connecting to distant servers increases routing complexity and network distance, which can raise latency and reduce stability. This may lead to delayed submissions and a higher stale share rate. In contrast, selecting a nearby regional endpoint helps maintain more consistent communication between mining hardware and the pool.

Failover and redundancy: Dual-WAN and LTE Backup

To reduce the risk of downtime, mining operations commonly rely on redundant internet connections rather than a single internet provider.

A dual Wide Area Network (WAN) setup connects mining hardware to two separate internet sources simultaneously. If the primary connection fails, traffic automatically switches to the backup without manual intervention, keeping miners connected to the pool.

Long-Term Evolution (LTE) mobile connections provide a practical backup option, particularly where a second fixed-line provider is unavailable. While mobile connections introduce higher latency compared to wired alternatives, maintaining pool connectivity during an outage is preferable to a complete interruption.

For operations where uptime directly affects profitability, combining a primary wired connection with a secondary LTE backup provides a reliable foundation for consistent mining performance.

How to reduce crypto mining latency

Modern ASIC miners such as the Antminer S19 Pro, Antminer S21, and Whatsminer M30, M50, and M60 series depend on stable network routing to maintain efficient communication with mining pools.

Most latency issues stem from unstable or poorly configured networks. Weak wireless connections, overloaded routers, distant mining pool endpoints, and inconsistent internet service can all introduce small delays that accumulate over time.

A mining-ready network setup helps prevent these problems before deployment. Stable Ethernet connections, properly configured network equipment, and nearby regional pool endpoints create a more direct and reliable communication path. Early latency testing helps identify weak points in advance.

Selecting mining pools with efficient server infrastructure also helps ensure faster share processing and more consistent mining performance over time.

FAQ

What is considered good latency for Bitcoin mining?

Latency under 50 ms is a key factor for smooth operation of pool-based mining — every millisecond of delay increases the risk of shares arriving after the pool has moved to a new block.

Why does latency matter more than bandwidth in mining?

Latency matters more than bandwidth in mining because mining depends on how quickly data moves between ASIC hardware and mining pools, not on how much data can be transferred at once. Even a high speed connection with large bandwidth does not improve performance if there are delays in communication.

What is Stratum-level ping?

Stratum-level ping measures the round-trip response time between mining hardware and a mining pool using the Stratum protocol, compared to ICMP ping which only tests basic network reachability without reflecting real mining communication.

Why do slow connections increase stale shares?

Slow connections delay share submission to the mining pool, increasing the chance that valid results arrive after a new block has already been issued, resulting in stale shares.