What should I check first when a KAS Worker shows offline?
The pool can mark each Worker offline or not and send a last-seen time. This page shows that as given. If the mark or the time is absent, it stays unknown and is not written as 0. An empty list only means no name came back. Check the regular pool, the kaspa: wallet, and the machine-class share difficulty on the help page before the miner's own log. Share stats from 5 minutes to 6 hours can be compared on the pool side. This page does not turn offline into coins you failed to mine.
| What you see | Next check |
|---|---|
| The row is marked offline and has a last-seen time | Compare that time with the miner log. It does not name the failed part |
| No offline mark, or no time | Leave it unknown. Do not call it online, and do not write rate 0 |
| The list is empty | The pool returned no name. Check the kaspa: address and the regular pool before opening the case |
| The share-difficulty port does not match the machine class | Move back to the help page's step for that class. 2Miners says difficulty does not change rewards, but submits may not match |
A row marked offline only means the regular pool currently marks that Worker as not online. The Kaspa monitor does not tell you whether the cause is power, a fan, a cable, or the pool port. Compare the share-difficulty class in ASIC and Worker rate first, then read unpaid and paid before treating a missing amount as 0.
What is on the row
The pool can return a name, that Worker's rate, whether it is offline, and a last-seen time. When a mark exists, the page shows it. When the mark or the time is absent, that cell stays unknown. Do not fill it in as online, and do not write the rate as 0. The account's current rate is a different row. One machine being offline does not rewrite that row as 0.
An empty list is not a whole-farm shutdown. It means this regular-pool account came back with no name. A machine on SOLO was never going to appear in this kas.2miners.com account.
Check in this order
First confirm the wallet in the miner is the full kaspa: address and the host is the regular pool, not a BTC or TON address from the help page and not SOLO. Then check that share difficulty matches the help page for the class: GPU and KS0 use the lower step, and KS1/KS2 and KS3-class use higher steps. If you are unsure, the help page says to choose the lower step. Share difficulty does not change miner rewards, but the wrong port for the class can mean submits never entered this wallet. Regional hosts stay on the help page. This guide does not list them.
Only then read accepted shares and errors on the miner. The API notes offer share stats for 5 minutes, 30 minutes, and 6 hours, which you can compare on the pool side for recent shares. This page does not convert “offline for two hours” into KAS you missed, and it does not promise the gap will be filled after the machine returns.
Limits
Crash interpretation cannot read an ASIC log and does not use a KAS device slot. The Mac Agent cannot reboot a Kaspa miner. Several offline rows under one wallet are still one unpaid balance. Do not subtract balance by the offline count. Extra saved devices count toward five per project on Free, or 50 on Pro, only when you save them. When a new read does not arrive, do not rewrite the blank as 0.
An illustrative case
This is a diagnostic order, not a failure report. Suppose Worker A is not marked offline and has a rate, Worker B is marked offline and was last seen two hours before A, and unpaid is still 12.5 KAS. You can say the pool's mark for B differs from A, and B's last-seen time is earlier. You cannot say the fan must have failed, you cannot change 12.5 to 0, and you cannot estimate lost coins from those two hours. If B has no last-seen time, the time stays unknown.
Common questions
Does offline mean the hashrate is already 0?
No. Offline is the pool's mark on that Worker. If the rate is missing, leave it unknown and do not write 0. The account rate is not rewritten to 0 because one row is offline.
Is last-seen the same as the last 24 hours?
No. Last-seen is the time on that Worker row. The last 24 hours is the wallet's rolling books. Fetch time is when this response arrived. Do not substitute one for another. If a time is absent, it stays unknown.
Can this page restart the miner after it goes offline?
No. This page only reads the regular-pool account. Crash interpretation does not control an ASIC and does not use a device slot. The Agent on a Mac is for Train at Home only. Restoring the connection is done in the miner and the pool config.