Diagnostic: Hashrate drop alerts

The hashrate drop alerts audit is available under the activity tab in the diagnostic and shows the current grade from the data obtained yesterday and a small historical chart for the performance of the last week. The grade is determined depending on how many hashrate drops alerts you got. The more alerts per worker, the lower the grade.

Alerts are one of the mechanisms that are helping you to keep your mining operation in good health. However, receiving too many alerts just isn't efficient. You probably won't even read them since there are too many of them and it will be very hard to examine your 24h activity log. This is why it is OK to receive some alerts, but not too many of them.

Hashrate drops are compared through the worker's statistics data and checked every 10 minutes. The most recent detected hashrate is compared with the median value of the last hour (so last 6 entries in the worker's statistics, since the data is saved every 10 minutes). We decided to compare recent hashrate with median hashrate as median value isn't as sensitive to outliers as the average value.

If you are getting too many hashrate drop alerts, this could be because of the following reasons:

  • You are mining the algorithm with frequent hashrate changing (for example X16R, X16Rv2). Try setting the hashrate drop % setting to a higher value.
  • One or more of your GPUs or ASIC boards are getting frequent interruptions, which makes the total hashrate lower. Examine your hardware.
  • Your rig or ASIC is having connectivity issues with the pool and is hashing with 0 H/s. Examine the status of your worker on the pool.