Why does Acurast registration remain when the phone is offline or missed heartbeats?
The result here stays Registered. It does not flip to offline because a heartbeat aged. To see whether the phone is still reporting, use Hub, whether the app is running, and the official 30-minute heartbeat with three chances per epoch.
| What you see | What it more likely means | Next check |
|---|---|---|
| Still Registered here | The mainnet index still lists this processor | Do not treat it as an online lamp |
| Unavailable here | The address is not a mainnet processor, or the index returned nothing this time | Check manager vs Canary, or look again later |
| One heartbeat succeeded in the epoch | Official rule: one of three on chain still assigns benchmark rewards | Missing one or two does not by itself cancel that epoch’s benchmark rewards |
| None of the three arrived | That epoch’s benchmark-reward condition was not met | Check recent heartbeats in Hub or the Telegram monitoring bot; do not clear registration |
| Balance dipped slightly | Report fees, usually about 0.0013 ACU | Not proof the phone is offline |
After the phone is powered off, the system stops the app, or the network drops, the processor row in the mainnet index can remain. The Acurast project page can still show Registered and the same Core/Lite and Android/iOS type. That does not mean the phone is reporting. This page has no separate online or offline lamp.
Official processor docs: heartbeats are about every 30 minutes, and an epoch is about 90 minutes, so there are three heartbeat chances. Benchmark rewards are assigned when at least one of those three is received on chain. Missing some heartbeats does not by itself remove that epoch’s benchmark rewards. If none of the three arrives, that condition is not met. The docs point to the Acurast Monitoring Bot on Telegram for recent performance, rather than scanning the full heartbeat history by hand.
Checks, in order
- Confirm Hub is on Mainnet and you opened this phone’s Processor, not the manager wallet. A manager address that is not a processor shows unavailable here. That is a different problem from the phone being offline.
- On the phone, see whether the Processor app is still running. You can pause Lite. Core is a dedicated phone, but power loss or a dead network still stops heartbeats.
- Compare the last three intervals of about 30 minutes. One success meets the official benchmark-reward condition for that epoch. If none succeeded, check battery, network, and whether the system froze the app.
- A balance change on the order of about 0.0013 ACU fits the report fee described officially. Do not treat that dip alone as proof of downtime.
- Saving an extra device while you debug uses one slot on this project (five on Free, 50 on Pro). Do not save both the SS58 form and the 0x form of the same phone.
Example
Illustration, not a log from a real phone: an epoch runs from 12:00 to about 13:30, with planned heartbeats at 12:00, 12:30, and 13:00. Only 12:30 succeeds. Under the official rule, that epoch’s benchmark-reward condition is met. At 13:20 this site still shows only Registered. It does not print “1/3” or Offline. If all three fail, the registration row can still be there while the reward condition is not met.
Next step and limit
Whether a deployment adds Busy Bonus for that epoch is covered in job status. Do not treat a pool total as a personal credit; see reward scope. This site does not receive phone notifications and cannot restart the app.
Common questions
If Registered is more than a day old, is the phone treated as online?
No. This site does not convert registration age into online status. Registration can remain. Whether heartbeats are still arriving is a recent-report question for Hub or the official monitoring bot.
If two heartbeats were missed, do benchmark rewards for that epoch remain?
The official rule assigns benchmark rewards when one of the three chances in an epoch reaches the chain. Two misses with one success still meet that condition. Three misses do not. Staking rewards and the Busy Bonus still depend on staking terms and whether a deployment was executing that epoch.
The lookup just became unavailable. Is the phone offline?
Not necessarily. Unavailable means this attempt did not get “this address is a mainnet processor,” for example a manager wallet, a Canary account, or no index result. An offline phone can still stay Registered.