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 #6816 | Acurast Pulse

Manager #6816 · compute baseline

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

85.7% healthy·30d↓6.6pp

LiveUpdated just now·Refresh now ↻

14 devices

12Healthy

0Watch

2Investigate

0Low confidence

1Regressions

4Improving

0Stale heartbeat

2Failures

0.9ACU/day at risk

Non-Green 2 Investigate 2 Watch 0 Healthy 12 Improving 4▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Investigate in Compare (1)

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 rollup2 modelsClick to expand

Model	Devices	Healthy	Watch	Investigate	% Healthy	Improving
Untagged	1	0	0	1	0.0%	0
Google Pixel 3a	1	0	0	1	0.0%	0

ModelBuildSortShowing 1 of 2

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

—

5DaHVwSxrvHFxV...gZfZvvRjGwCOREFlagged 26h+

Multi CPU -14.3% · Risk 100 · 3m lag · 2 failures

Google Pixel 3a

-2.9%

-14.3%

-0.0%

-14.3%

▸

5DaHVwSxrvHFxV...gZfZvvRjGwCOREMulti CPU -14.3% · Risk 100 · 3m lag · 2 failuresGoogle Pixel 3a

-14.3%▸

CPU 1c-2.9%

CPU Mc-14.3%

RAM-0.0%

Worst-14.3%