Rejected and Stale Shares, Worker Offline and Low Pool Hashrate
.hflmc-article{color:#102033;font-size:18px;line-height:1.65}.hflmc-article p{font-size:18px;line-height:1.65;margin:0 0 16px}.hflmc-article h2{font-size:32px!important;line-height:1.2!important;margin:34px 0 14px!important}.hflmc-article ul,.hflmc-article ol{font-size:17px;line-height:1.65;margin:0 0 22px 1.3em;padding-left:1em}.hflmc-article li{margin:8px 0}.hflmc-intro,.hflmc-next{border:1px solid #cfe1ff;background:#f7fbff;border-radius:12px;margin:18px 0 26px;padding:18px 20px}.hflmc-intro p:last-child,.hflmc-next p:last-child{margin-bottom:0}.hflmc-steps{counter-reset:hflmc-step;list-style:none!important;margin-left:0!important;padding-left:0!important}.hflmc-steps li{border-bottom:1px solid #dfe9f8;margin:0!important;padding:13px 10px 13px 48px;position:relative}.hflmc-steps li:before{align-items:center;background:#3867ff;border-radius:50%;color:#fff;content:counter(hflmc-step);counter-increment:hflmc-step;display:flex;font-size:14px;font-weight:800;height:28px;justify-content:center;left:8px;position:absolute;top:13px;width:28px}.hflmc-table-wrap{border:1px solid #cfe1ff;border-radius:12px;margin:18px 0 26px;overflow:auto}.hflmc-table-wrap table{border-collapse:collapse!important;margin:0!important;min-width:650px;width:100%}.hflmc-table-wrap th,.hflmc-table-wrap td{border:0!important;border-bottom:1px solid #e4edfb!important;font-size:16px;line-height:1.45;padding:13px 14px!important;text-align:left;vertical-align:top}.hflmc-table-wrap th{background:#eef5ff;color:#52627a;font-weight:800}.hflmc-faq{border:1px solid #cfe1ff;background:#f8fbff;border-radius:12px;margin:30px 0;padding:18px}.hflmc-faq h2{margin-top:3px!important}.hflmc-faq details{background:#fff;border:1px solid #d8e7ff;border-radius:9px;margin:10px 0}.hflmc-faq summary{cursor:pointer;font-size:18px;font-weight:800;padding:14px 16px}.hflmc-faq details p{padding:0 16px 15px}[dir=”rtl”] .hflmc-table-wrap th,[dir=”rtl”] .hflmc-table-wrap td{text-align:right}[dir=”rtl”] .hflmc-article ul,[dir=”rtl”] .hflmc-article ol{margin-left:0;margin-right:1.3em;padding-left:0;padding-right:1em}[dir=”rtl”] .hflmc-steps{margin-right:0!important;padding-right:0!important}[dir=”rtl”] .hflmc-steps li{padding-left:10px;padding-right:48px}[dir=”rtl”] .hflmc-steps li:before{left:auto;right:8px}@media(max-width:767px){.hflmc-article,.hflmc-article p{font-size:16px}.hflmc-article h2{font-size:26px!important}.hflmc-intro,.hflmc-next,.hflmc-faq{padding:14px}.hflmc-table-wrap table{min-width:580px}}
Updated: August 7, 2026 A pool can show an offline worker, rejected shares or a lower hashrate even while the ASIC dashboard looks normal. These symptoms do not have one universal cause: they can come from the pool URL, the local network, unstable hardware or simply the averaging window used by the dashboard. Start with accepted shares and connection logs. Then change one variable at a time. This prevents a normal 10-minute fluctuation from turning into an unnecessary firmware, frequency or pool change. There is no percentage that is safe for every pool and every measurement method. Lower is better. A sustained increase above your own baseline deserves attention; as a practical trigger, many operators investigate when rejects remain around 1–2% or higher, but the reason code and time window matter more than a single rounded number. Do not mix invalid hardware results with stale network results. Invalid work points more often to frequency, voltage, firmware, chips or power. Stale work points more often to latency, packet loss or unstable routing. The pool may not have received a valid share recently, the worker name may differ, or the status may lag. Verify accepted shares and the connection log. Most pools use a simple worker password, but an incorrect authorization format can prevent the worker from connecting at all. Copy the values shown in your account. Reboot only after recording the log and settings. Otherwise you may erase the evidence that identifies DNS, network, temperature or hashboard errors. Next step: after the worker is stable for a full day, compare credited BTC and pool behavior with the same ASIC settings in the calculator and pool ranking. What each symptom actually means
Symptom Meaning First check Worker offline The pool has not credited a recent valid share to that worker. Pool URL and port, worker format, Internet access and the ASIC log. Rejected share The server received work it could not credit. Reason code, pool-side rejection rate, firmware and hardware errors. Stale share A valid-looking result arrived after the mining job had changed. Latency, packet loss, Wi-Fi or overloaded network equipment. Low pool hashrate The share-based estimate is below the ASIC local reading. Compare equivalent 6-hour or 24-hour windows, not instantaneous values. Diagnostic order that avoids false conclusions
How much rejection is too much?
When pool-side hashrate looks low
Frequently asked questions
Why is my worker offline although the ASIC is hashing?
Can a bad password reduce hashrate?
Should I reboot immediately?
