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

Manager #432 · compute baseline

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

69.2% healthy·30d↓3.9pp

LiveUpdated just now·use cached

26 devices

21Healthy

2Watch

3Investigate

0Low confidence

3Regressions

20Improving

1Stale heartbeat

3Failures

0.4ACU/day at risk

Non-Green 5 Investigate 3 Watch 2 Healthy 21 Improving 20▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Improving in Compare (1)▥ Investigate in Compare (3)

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.

ModelBuildSortShowing 5 of 5

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

—

5FahD2EQGAwgW6...DoHD2gUkkHLITEFlagged 29h

down · Multi CPU -15.9% · Risk 100 · 1d lag · 10 failures

+0.3%

-15.9%

-0.0%

-15.9%

▸

—

5E2VtXpN73xJqx...QxUNFAjdSLCOREFlagged 29h

Multi CPU -11.5% · Risk 100 · 9m lag · 1 failure

-1.5%

-11.5%

0.0%

-11.5%

▸

—

5HmBqXxRgdgnzz...St8s8iyg5gLITEFlagged 40h

Single CPU -46.7% · Multi CPU -32.1% · Risk 100 · 4m lag · 7 failures

-46.7%

-32.1%

-0.0%

-46.7%

▸

—

5E2Sy4C2eGMTk7...k2pTFceqMdCORE↑ 23 streak

1m lag · 6 failures

-0.3%

-3.2%

-0.0%

-3.2%

▸

—

5GzijKbTvXBRjK...BmengMnoptCORE

16m lag · 7 failures

+0.7%

-5.0%

-0.0%

-5.0%

▸

5FahD2EQGAwgW6...DoHD2gUkkHLITEdown · Multi CPU -15.9% · Risk 100 · 1d lag · 10 failures

-15.9%▸

CPU 1c+0.3%

CPU Mc-15.9%

RAM-0.0%

Worst-15.9%

5E2VtXpN73xJqx...QxUNFAjdSLCOREMulti CPU -11.5% · Risk 100 · 9m lag · 1 failure

-11.5%▸

CPU 1c-1.5%

CPU Mc-11.5%

RAM0.0%

Worst-11.5%

5HmBqXxRgdgnzz...St8s8iyg5gLITESingle CPU -46.7% · Multi CPU -32.1% · Risk 100 · 4m lag · 7 failures

-46.7%▸

CPU 1c-46.7%

CPU Mc-32.1%

RAM-0.0%

Worst-46.7%

5E2Sy4C2eGMTk7...k2pTFceqMdCORE1m lag · 6 failures

-3.2%▸

CPU 1c-0.3%

CPU Mc-3.2%

RAM-0.0%

Worst-3.2%

5GzijKbTvXBRjK...BmengMnoptCORE16m lag · 7 failures

-5.0%▸

CPU 1c+0.7%

CPU Mc-5.0%

RAM-0.0%

Worst-5.0%