Mining Academy

Connect to the pool

Why Pool Hashrate Drops: Causes and Diagnosis

Pool hashrate drops for two different reasons. Either the device really is hashing slower (overheating, a board fault, power, firmware), or it hashes as usual but the pool sees less because of the network, wrong settings or rejected shares. Start by separating "hashrate on the miner screen" from "hashrate on the pool": if the first is normal and the second is low, the problem is the connection or settings; if both are low, it is the hardware.

Calculated versus real hashrate: why the numbers differ

A pool cannot measure hashrate directly. It only sees submitted shares and estimates power from their count and difficulty over a chosen window, from a few minutes to a day. So pool and device numbers are never identical, and small differences are normal.

  • Short windows fluctuate. Shares arrive randomly, so a five-minute hashrate can deviate from the average by tens of percent, especially on low-power devices. Use one-hour and daily windows.
  • The miner screen shows "Real-time" and "Average". If the device average is close to spec while the pool shows noticeably less for many hours, look at rejected shares and connectivity.
  • Rated power is a maximum under ideal conditions. In heat, in a low-power mode or with one weak board, real hashrate is below the rating, and that is not a pool error.

In practice, compare averages over an hour or more, not second to second. A sustained drop of 10 to 20 percent or more deserves investigation.

Step-by-step diagnosis

  1. Open the miner web interface and Miner Status. How many boards are working, what is each board's hashrate, are there zero values?
  2. Check the pool status on the status page: the active pool should be Alive, not Dead, and the Rejected counter should not climb quickly.
  3. Open the Kernel Log and look for messages about temperature, fans, power and lost boards (see the article on Antminer errors).
  4. Compare with the pool dashboard: when exactly the drop began, and whether it affects one worker or all of them.

The last point matters most. If all workers fell at once, suspect a common cause: internet, power at the site, heat, a routing problem to the pool. If only one fell, the problem lies in that device.

Temperature and cooling

Overheating is the most common cause of a gradual decline. As temperature rises the firmware lowers chip frequency, and at a critical level it stops hashing. Hashrate drifts down without obvious error messages.

  • Match the drop to the time of day: if it coincides with the hottest hours, the cause is room cooling.
  • Check fan speeds and heatsink cleanliness.
  • Make sure hot exhaust air is not drawn back into the intake.
  • If a high-performance mode is on, return to stock; it gives temperature headroom.

Seasonality is obvious here: hashrate drops more often in summer. For cooling at home, read the article on mining at home.

Hardware causes: boards, chips, power

If one hash board drops out, hashrate falls in a step: by a third on a three-board unit. Another typical case is individual chips failing; the board keeps running but with fewer active ASICs. In Miner Status this shows as a difference in hashrate between boards.

Unstable power also lowers hashrate: during voltage sags chips make more errors and the unit may reboot. Make sure the power line is rated for the load and connectors do not heat up. If the problem stays after checking cooling and power, show the board to a technician: there is an ASIC repair section on our site too.

Rejected and stale shares

Every share a device submits can be accepted or rejected by the pool. Rejected shares do not count, so their proportion directly reduces visible hashrate.

  • Stale. The share arrived after the pool had issued new work. The cause is network latency: the farther the stratum and the worse the link, the more stale shares.
  • Invalid / duplicate. Usually a sign of firmware problems, unstable overclocking or chip errors.
  • Low difficulty. A "share above target" or low-difficulty message points to wrong settings on the device or in the firmware.

A small share of rejects, a few percent or less, is normal. If it is consistently higher, check the network first: choose the geographically closest stratum. RuPool has regional addresses: msk2-ru.enter.rupool.pro (Moscow), nsk-ru.enter.rupool.pro (Novosibirsk), hel-fi.enter.rupool.pro (Helsinki), ala-kz.enter.rupool.pro (Almaty), while enter.rupool.pro picks the nearest one automatically.

Network and stratum settings

If the device hashes normally but pool hashrate is low or unstable, check the connection.

  • Packet loss and latency spikes. Wi-Fi, an overloaded router or an unstable ISP cause disconnects. Connect miners by cable.
  • Reconnects. Frequent switching of the active pool in the settings shows an unstable connection.
  • A blocked port. If the main port is filtered, use a backup one (BTC: 8888, 443, 25; LTC and DOGE: 8889, 444, 26) or SSL (999 and 998 respectively).
  • Worker errors. A wrong subaccount.worker format means hashrate is credited to the wrong place or not at all.

Configure three pools: a main one and two backups (for example, different regional stratums). Then a break toward one region does not stop mining. Step-by-step setup is in the article on how to connect an ASIC to a pool.

Network difficulty and other external causes

Sometimes it is income that falls, not hashrate. If pool hashrate is steady but earnings decreased, the usual cause is a change in network difficulty or the coin price, not the device. An FPPS pool pays for your shares based on expected block reward, so your hashrate and earnings are linked through difficulty. The profit calculator helps estimate the effect.

Reading the chart: the shape of the drop points to the cause

The shape of the curve on the hashrate chart often suggests a diagnosis before you open the unit.

  • A step down followed by a flat shelf. A board dropped out or the operating mode changed. Check Miner Status and the log.
  • A gradual decline during the day. Building heat or clogged heatsinks; hashrate recovers at night.
  • A sawtooth with drops to zero and recoveries. Reboots caused by power problems, or lost connections to the pool.
  • A simultaneous drop across all workers. A shared cause: internet, electricity, the route to the stratum.
  • A noisy but flat-on-average line. Normal statistical variance of shares; nothing to fix.

Write down the date and time of each drop and what you did about it. After a couple of weeks such a log reveals patterns better than any guesswork.

Monitoring: noticing a drop in time

A problem is easier and cheaper to fix when you catch it right away. A few practices:

  • Give every device its own worker name so you can see which one sagged. The site has a name generator among its tools.
  • Check statistics regularly in your dashboard or in the RuPool mobile apps for iOS and Android.
  • To give a farm manager or hosting provider access to statistics, use a watcher link: it opens statistics without a password.
  • For a large farm, run your own monitoring of temperature, power and device state, independent of the pool.

Always remember that mining carries risk, and temporary drops in hashrate and earnings happen to every participant.

FAQ

Why is pool hashrate lower than on the miner screen?

The pool estimates hashrate from accepted shares. A small difference is normal because shares are random; a noticeable and lasting one points to rejected shares, network delay or wrong settings. Look at one-hour and daily values rather than five minutes.

Only one worker dropped. What should I do?

Check that device's Miner Status: number of working boards, temperature and fans, pool status. A drop on one worker almost always points to faulty hardware or its connection.

Should I change pools if there are many rejected shares?

First switch to the nearest stratum region and connect the device by cable. A consistently high reject share is more often caused by network delay or hardware condition than by the pool itself.

Can firmware cause a hashrate drop?

Yes. An incompatible version, a failed update or unstable overclocking lowers hashrate or raises errors. Return to a proven firmware version and the stock mode.

Why did income fall while hashrate stayed the same?

Income depends not only on hashrate but also on network difficulty and the coin price. Rising difficulty reduces your share of the work. Recalculate the expected result in the profit calculator.