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

Manager #3472 · compute baseline

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

42.9% healthy·30d↓12.7pp

SnapshotUpdated 24 min ago·Refresh now ↻

28 devices

12Healthy

9Watch

7Investigate

0Low confidence

7Regressions

3Improving

7Stale heartbeat

7Failures

0.7ACU/day at risk

Non-Green 16 Investigate 7 Watch 9 Healthy 12 Improving 3▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Investigate in Compare (7)

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

Model	Devices	Healthy	Watch	Investigate	% Healthy	Improving
Untagged	14	0	8	6	0.0%	0
Samsung Galaxy A71	1	0	0	1	0.0%	0
Xiaomi Redmi Note 11

ModelBuildSortShowing 16 of 16

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

—

5DkDpDac7ifDoh...TofmEp2b1ALITE

down · 10d lag · 2 failures

—

+0.0%

▸

—

5Gwq1Qh1QR7En8...mJknB5gqgRLITE

down · 8d lag

—

-0.0%

+0.0%

-0.0%

▸

—

5EuCjjdhVHh9J8...2zJ4SBcFJSCORE

down · 22d lag · 1 failure

—

+0.0%

-0.0%

+0.0%

-0.0%

▸

—

5Hk96qWhRdvpvM...H5xeN3PDomCORE

down · 6d lag · 2 failures

—

-0.0%

+0.0%

-0.0%

▸

—

5DioLy1CXTxMZr...MwZUxqCR8YCORE

down · 2d lag · 3 failures

—

+0.0%

-0.1%

+0.0%

-0.1%

▸

—

5GuNpkMqm66WKf...3JtdbmY4qQCORE

down · 2d lag · 3 failures

—

+0.0%

-0.0%

▸

—

5CdLZuzeznPcPJ...6b1xng3j88COREFlagged 18h+

Single CPU -8.8% · Multi CPU -5.3% · Risk 77 · 22m lag · 2 failures

—

-8.8%

-5.3%

+0.0%

-8.8%

▸

—

5EqMa3X3UhuntL...bv9SxkjdMhCOREFlagged 14h

Multi CPU -7.3% · Risk 87 · 5m lag · 4 failures

—

+0.2%

-7.3%

+0.0%

-7.3%

▸

—

5FkR2gsfMDL54Z...v5VUh2SQ4xCOREFlagged 13h

Multi CPU -8.8% · Risk 87 · 22m lag · 3 failures

Samsung Galaxy A71

+0.4%

-8.8%

-0.0%

-8.8%

▸

—

5CcJgw2LKdr8ZX...bCbw4txYFWiOSFlagged 4h

Multi CPU -15.1% · Risk 100 · 3h lag · 4 failures · stale

—

-0.6%

-15.1%

-0.0%

-15.1%

▸

—

5Co65eug96U9RN...TW53FPrRFBLITEFlagged 2h

Single CPU -60.3% · Multi CPU -28.1% · Risk 100 · 4m lag · 9 failures

—

-60.3%

-28.1%

+0.0%

-60.3%

▸

—

5EqMdzmiwi1sBp...wNJf2Qz3TDCOREFlagged 18h+

Single CPU -82.6% · Multi CPU -37.4% · Risk 100 · 24m lag · 1 failure

—

-82.6%

-37.4%

-0.0%

-82.6%

▸

—

5GLd6qLu7V3bh1...dUyPF8sjLoCOREFlagged 18h+

Multi CPU -10.6% · Risk 100 · 18m lag · 2 failures

—

+0.3%

-10.6%

+0.0%

-10.6%

▸

—

5EQyNnXaWirTDT...pion7H9fZHCORE

10m lag · 7 failures

—

+3.3%

+2.2%

-0.0%

▸

—

5FAFbWdysGBFdR...nhP242jc1rCORE

5m lag · 5 failures

—

-0.2%

+0.2%

+0.0%

-0.2%

▸

—

5H9KSrArbCruuP...grNrRHJ2wHCORE

25m lag · 5 failures

Xiaomi Redmi Note 11

+0.3%

-3.4%

-0.0%

-3.4%

▸

5DkDpDac7ifDoh...TofmEp2b1ALITEdown · 10d lag · 2 failures

+0.0%▸

CPU 1c+0.0%

CPU Mc+0.0%

RAM+0.0%

Worst+0.0%

5Gwq1Qh1QR7En8...mJknB5gqgRLITEdown · 8d lag

-0.0%▸

CPU 1c-0.0%

CPU Mc-0.0%

RAM+0.0%

Worst-0.0%

5EuCjjdhVHh9J8...2zJ4SBcFJSCOREdown · 22d lag · 1 failure

-0.0%▸

CPU 1c+0.0%

CPU Mc-0.0%

RAM+0.0%

Worst-0.0%

5Hk96qWhRdvpvM...H5xeN3PDomCOREdown · 6d lag · 2 failures

-0.0%▸

CPU 1c-0.0%

CPU Mc+0.0%

RAM+0.0%

Worst-0.0%

5DioLy1CXTxMZr...MwZUxqCR8YCOREdown · 2d lag · 3 failures

-0.1%▸

CPU 1c+0.0%

CPU Mc-0.1%

RAM+0.0%

Worst-0.1%

5GuNpkMqm66WKf...3JtdbmY4qQCOREdown · 2d lag · 3 failures

-0.0%▸

CPU 1c+0.0%

CPU Mc-0.0%

RAM-0.0%

Worst-0.0%

5CdLZuzeznPcPJ...6b1xng3j88CORESingle CPU -8.8% · Multi CPU -5.3% · Risk 77 · 22m lag · 2 failures

-8.8%▸

CPU 1c-8.8%

CPU Mc-5.3%

RAM+0.0%

Worst-8.8%

5EqMa3X3UhuntL...bv9SxkjdMhCOREMulti CPU -7.3% · Risk 87 · 5m lag · 4 failures

-7.3%▸

CPU 1c+0.2%

CPU Mc-7.3%

RAM+0.0%

Worst-7.3%

5FkR2gsfMDL54Z...v5VUh2SQ4xCOREMulti CPU -8.8% · Risk 87 · 22m lag · 3 failuresSamsung Galaxy A71

-8.8%▸

CPU 1c+0.4%

CPU Mc-8.8%

RAM-0.0%

Worst-8.8%

5CcJgw2LKdr8ZX...bCbw4txYFWiOSMulti CPU -15.1% · Risk 100 · 3h lag · 4 failures · stale

-15.1%▸

CPU 1c-0.6%

CPU Mc-15.1%

RAM-0.0%

Worst-15.1%

5Co65eug96U9RN...TW53FPrRFBLITESingle CPU -60.3% · Multi CPU -28.1% · Risk 100 · 4m lag · 9 failures

-60.3%▸

CPU 1c-60.3%

CPU Mc-28.1%

RAM+0.0%

Worst-60.3%

5EqMdzmiwi1sBp...wNJf2Qz3TDCORESingle CPU -82.6% · Multi CPU -37.4% · Risk 100 · 24m lag · 1 failure

-82.6%▸

CPU 1c-82.6%

CPU Mc-37.4%

RAM-0.0%

Worst-82.6%

5GLd6qLu7V3bh1...dUyPF8sjLoCOREMulti CPU -10.6% · Risk 100 · 18m lag · 2 failures

-10.6%▸

CPU 1c+0.3%

CPU Mc-10.6%

RAM+0.0%

Worst-10.6%

5EQyNnXaWirTDT...pion7H9fZHCORE10m lag · 7 failures

-0.0%▸

CPU 1c+3.3%

CPU Mc+2.2%

RAM-0.0%

Worst-0.0%

5FAFbWdysGBFdR...nhP242jc1rCORE5m lag · 5 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+0.2%

RAM+0.0%

Worst-0.2%

5H9KSrArbCruuP...grNrRHJ2wHCORE25m lag · 5 failuresXiaomi Redmi Note 11

-3.4%▸

CPU 1c+0.3%

CPU Mc-3.4%

RAM-0.0%

Worst-3.4%