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

Manager #577 · compute baseline

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

36.3% healthy·30d↓19.0pp

LiveUpdated just now·Refresh now ↻

864 devices

354Healthy

296Watch

211Investigate

3Low confidence

217Regressions

167Improving

2Stale heartbeat

211Failures

0ACU/day at risk

Non-Green 510 Investigate 211 Watch 296 Healthy 354 Improving 167▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Improving in Compare (5)

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
Samsung Galaxy Z Fold4	5	0	4	0	0.0%	2
Untagged	5	0	3	0	0.0%	3

ModelBuildSortShowing 10 of 10

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

—

5FXjEQjBpsK8HJ...smV739eNyXCORE

Missing recent benchmark

—

No baseline

▸

—

5Fyns5ng3zHmAK...7ha1D5XXqTCORE

Missing recent benchmark

—

No baseline

▸

—

5CURNx2VknswgM...cWJ4doLzXoCORE↑ 10 streak

27m lag · 6 failures

Samsung Galaxy Z Fold4

+10.4%

+4.1%

-0.0%

▸

—

5DmMssVEHkLSt6...nNgebGfjP1CORE↑ 5 streak

20m lag · 6 failures

—

+2.7%

+2.4%

-0.0%

▸

—

5DrBaMmUYMeyn3...GRQvEv7TNSCORE

24m lag · 7 failures

Samsung Galaxy Z Fold4

+0.5%

+1.0%

-0.0%

▸

—

5GUYXjW5gq6uqe...rLkk5EbFchCORE↑ 10 streak

27m lag · 7 failures

Samsung Galaxy Z Fold4

+0.1%

-1.4%

-0.0%

-1.4%

▸

—

5GXQnWZjaD75zQ...WSKPY9Q9MLCORE

9m lag · 5 failures

Samsung Galaxy Z Fold4

-0.3%

+2.0%

-0.0%

-0.3%

▸

—

5HDeX5pA8uiZLQ...k9fQEsbs3GCORE↑ 6 streak

12m lag · 6 failures

—

+19.6%

+7.5%

-0.0%

▸

—

5HVxV9B9C51XCf...bgyQ3tNSLkCORE↑ 21 streak

2m lag · 9 failures

—

+0.7%

-0.8%

-0.0%

-0.8%

▸

—

5FAQLk3hgqDwxF...ZiVyF8Bs1CCORE

Missing recent benchmark

Samsung Galaxy Z Fold4

No baseline

▸

5FXjEQjBpsK8HJ...smV739eNyXCOREMissing recent benchmark

No baseline▸

CPU 1cNo baseline

CPU McNo baseline

RAMNo baseline

WorstNo baseline

5Fyns5ng3zHmAK...7ha1D5XXqTCOREMissing recent benchmark

No baseline▸

CPU 1cNo baseline

CPU McNo baseline

RAMNo baseline

WorstNo baseline

5CURNx2VknswgM...cWJ4doLzXoCORE27m lag · 6 failuresSamsung Galaxy Z Fold4

-0.0%▸

CPU 1c+10.4%

CPU Mc+4.1%

RAM-0.0%

Worst-0.0%

5DmMssVEHkLSt6...nNgebGfjP1CORE20m lag · 6 failures

-0.0%▸

CPU 1c+2.7%

CPU Mc+2.4%

RAM-0.0%

Worst-0.0%

5DrBaMmUYMeyn3...GRQvEv7TNSCORE24m lag · 7 failuresSamsung Galaxy Z Fold4

-0.0%▸

CPU 1c+0.5%

CPU Mc+1.0%

RAM-0.0%

Worst-0.0%

5GUYXjW5gq6uqe...rLkk5EbFchCORE27m lag · 7 failuresSamsung Galaxy Z Fold4

-1.4%▸

CPU 1c+0.1%

CPU Mc-1.4%

RAM-0.0%

Worst-1.4%

5GXQnWZjaD75zQ...WSKPY9Q9MLCORE9m lag · 5 failuresSamsung Galaxy Z Fold4

-0.3%▸

CPU 1c-0.3%

CPU Mc+2.0%

RAM-0.0%

Worst-0.3%

5HDeX5pA8uiZLQ...k9fQEsbs3GCORE12m lag · 6 failures

-0.0%▸

CPU 1c+19.6%

CPU Mc+7.5%

RAM-0.0%

Worst-0.0%

5HVxV9B9C51XCf...bgyQ3tNSLkCORE2m lag · 9 failures

-0.8%▸

CPU 1c+0.7%

CPU Mc-0.8%

RAM-0.0%

Worst-0.8%

5FAQLk3hgqDwxF...ZiVyF8Bs1CCOREMissing recent benchmarkSamsung Galaxy Z Fold4

No baseline▸

CPU 1cNo baseline

CPU McNo baseline

RAMNo baseline

WorstNo baseline