Phone Farm

Loading compute health board

Scoring retained benchmark history, confidence thresholds, and device compute regressions.

Resolving route12%

Acurast Pulse

Loading live view

Syncing chain state, reward ledgers, and fleet telemetry.

Resolving route12%

Manager Health #8180 | Acurast Pulse

Manager #8180 · compute baseline

Latest benchmark vs last 200 retained metric samples · ≥30 samples required to score

67.7% healthy·30d↑0.4pp

LiveUpdated 1 hrs ago·Refresh now ↻

99 devices

66Healthy

21Watch

11Investigate

1Low confidence

9Regressions

86Improving

1Stale heartbeat

11Failures

0.7ACU/day at risk

Non-Green 33 Investigate 11 Watch 21 Healthy 66 Improving 86▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Improving in Compare (4)

How are these conditions scored?Quick FAQ

● Healthy: All monitored pools (CPU 1c, CPU Mc, RAM) score within 5 % of this phone model's median. Treated as a good baseline — nothing to act on.
● Watch: At least one pool is 5–10 % below the model median on the latest run. A nudge, not yet an actionable problem.
● Investigate: At least one pool is 10 % or more below the model median. Persistent gaps that warrant a closer look — usually thermal throttling, background load, or a bad firmware release.
● Low confidence: The device hasn't reported enough benchmark runs to score it reliably. One of: brand-new device (first seen < 72 h ago), too few samples (< 30 baseline observations), or no benchmark history at all.
● Regressions: Devices with 3 or more consecutive non-healthy benchmark runs. A single bad run is noise; three in a row is a pattern. The streak resets the moment a healthy run lands.
● Improving: Devices with 3 or more trailing healthy runs immediately after at least one non-healthy run in recent history. The mirror of Regressions — recoveries worth celebrating, and a signal that whatever you changed is working.
● ACU/day at risk: Estimated daily ACU lost vs a healthy baseline, not the total earnings of flagged devices. Each non-healthy device's ACU/day is weighted by how far below its model median it scored — a device 12% below contributes ~12% of its earnings, not 100%. Watch and Investigate items without a measured delta fall back to status floors (5–10%).
● Stale heartbeat: Last heartbeat was over 50 minutes ago (stale) or over 6 hours ago (down). Healthy heartbeats land every ~50 minutes; anything past that suggests the device is offline or unreachable.
● Failures: Devices with a composite risk score ≥ 75. The score blends benchmark drop, heartbeat lag, and on-chain execution failures; the threshold marks devices that need attention soon.

Per-model rollup5 modelsClick to expand

Model	Devices	Healthy	Watch	Investigate	% Healthy	Improving
Untagged	12	0	4	7	0.0%	4
Boost Summit 5G	7	0	3	4	0.0%	4
BLU View 5

ModelBuildSortShowing 5 of 33

Alias▽Processor▽Device▽CPU 1c▽CPU Mc▽RAM▽Worst▽Trend

—

5EdJArAfQjz7vz...WozQoxPNxYCORE↑ 26 streak

down · 55d lag

BLU View 5

-0.0%

+0.0%

-0.0%

▸

—

5Dw6XiPwjvxz4c...ENSnaAGdkkCORE↑ 14 streak

6m lag · 16 failures

BLU View 5

+0.3%

+1.1%

-0.0%

▸

—

5F96vynh1FBdFa...8rmYvzzajJCORE

6m lag · 15 failures

BLU View 5

+4.0%

-1.9%

+0.0%

-1.9%

▸

—

5FZXGuYT4yLGP1...moLxP5xrsPCORE↑ 26 streak

30m lag · 15 failures

BLU View 5

-0.2%

-1.6%

+0.0%

-1.6%

▸

—

5Hb7Yf11GgBr2B...9Lu3LXDfKACORE↑ 26 streak

6m lag · 16 failures

BLU View 5

-0.2%

+7.2%

+0.0%

-0.2%

▸

5EdJArAfQjz7vz...WozQoxPNxYCOREdown · 55d lagBLU View 5

-0.0%▸

CPU 1c-0.0%

CPU Mc-0.0%

RAM+0.0%

Worst-0.0%

5Dw6XiPwjvxz4c...ENSnaAGdkkCORE6m lag · 16 failuresBLU View 5

-0.0%▸

CPU 1c+0.3%

CPU Mc+1.1%

RAM-0.0%

Worst-0.0%

5F96vynh1FBdFa...8rmYvzzajJCORE6m lag · 15 failuresBLU View 5

-1.9%▸

CPU 1c+4.0%

CPU Mc-1.9%

RAM+0.0%

Worst-1.9%

5FZXGuYT4yLGP1...moLxP5xrsPCORE30m lag · 15 failuresBLU View 5

-1.6%▸

CPU 1c-0.2%

CPU Mc-1.6%

RAM+0.0%

Worst-1.6%

5Hb7Yf11GgBr2B...9Lu3LXDfKACORE6m lag · 16 failuresBLU View 5

-0.2%▸

CPU 1c-0.2%

CPU Mc+7.2%

RAM+0.0%

Worst-0.2%