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

Manager #4548 · compute baseline

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

50.0% healthy·30d↓29.4pp

LiveUpdated just now·use cached

136 devices

97Healthy

23Watch

16Investigate

0Low confidence

16Regressions

51Improving

9Stale heartbeat

16Failures

0.8ACU/day at risk

Non-Green 39 Investigate 16 Watch 23 Healthy 97 Improving 51▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Improving in Compare (5)

▥ Investigate in Compare (16) ▾

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	30	0	17	13	0.0%	4
Samsung Galaxy A03s	7	0	4	3	0.0%	1
Motorola G Play 2024

ModelBuildSortShowing 39 of 39

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

—

5CWummeF45n3La...CGCFppdnz8iOS

down · 9d lag

—

-0.0%

▸

—

5GsVn27B96Ue2B...T9je2QTkstiOS

down · 31d lag

—

-0.0%

+0.0%

-0.0%

▸

—

5DbJ8ZHXTSqw1i...s8KvZbtesSCORE

down · 1d lag · 3 failures

—

+0.1%

+5.3%

+0.0%

▸

—

5EAYtwr646ah3A...NDaDgpiXHkiOS↑ 11 streak

down · 6h lag · 1 failure

—

+0.2%

-0.5%

-0.0%

-0.5%

▸

—

5GnMRHXiQvXr6a...bL4coJpkQJCORE↑ 11 streak

down · 11h lag · 2 failures

—

+1.0%

-4.2%

0.0%

-4.2%

▸

—

5GnBhXwGQfYW11...ha6SXoBHRwCORE

down · Risk 75 · 11h lag · 12 failures

—

+0.3%

-1.2%

+0.0%

-1.2%

▸

—

5D3BzExHPjF3Tk...2hzZdcP1FxiOSFlagged 9h

down · Single CPU -7.3% · Risk 100 · 10h lag

—

-7.3%

-1.5%

+0.0%

-7.3%

▸

—

5FtUGnE3GDBxW6...J3NoK7cEFsiOSFlagged 9h

down · Multi CPU -25.6% · Risk 100 · 10h lag · 1 failure

—

-3.4%

-25.6%

+0.0%

-25.6%

▸

—

5G2Z58yBK8rC3e...zd5tgtKooEiOSFlagged 10h

down · Multi CPU -20.3% · Risk 100 · 11h lag · 1 failure

—

-0.3%

-20.3%

+0.0%

-20.3%

▸

—

5G6JZDpjpbRjLe...hyZ3f3Cv5fCOREFlagged 10h

Multi CPU -5.6% · Risk 77 · 7m lag · 1 failure

—

+11.0%

-5.6%

-0.0%

-5.6%

▸

—

5EFpEnVdDXKc3f...ZgDJak6qCnCOREFlagged 1h

Multi CPU -7.2% · Risk 78 · 26m lag · 565 failures

—

-0.1%

-7.2%

-0.0%

-7.2%

▸

—

5E7YUXhJfYGM1a...5X7LXuJ7tpCOREFlagged 10h

Single CPU -8.1% · Risk 87 · 24m lag · 4 failures

Samsung Galaxy A03s

-8.1%

+9.0%

+0.0%

-8.1%

▸

—

5DJUN1onkSn9ai...QtLHwiGVSTCOREFlagged 27h+

Multi CPU -6.4% · Risk 94 · 4m lag · 5 failures

—

+1.5%

-6.4%

-0.0%

-6.4%

▸

—

5DMwU8243fosAY...Pgz4v3TzUWCOREFlagged 9h

Single CPU -6.3% · Risk 94 · 46m lag · 762 failures

Samsung Galaxy A03s

-6.3%

+0.7%

-0.0%

-6.3%

▸

—

5C8MbSLo7ozTi7...rUaCmCzxFHLITEFlagged 9h

Multi CPU -32.1% · Risk 100 · 13m lag · 1 failure

Samsung Galaxy A03s

+11.3%

-32.1%

-0.0%

-32.1%

▸

—

5CEbh7tA17FXEJ...HbN4V62WoNCOREFlagged 10h

Multi CPU -13.8% · Risk 100 · 18m lag · 4 failures

—

+2.9%

-13.8%

-0.0%

-13.8%

▸

—

5Cv7XR5qpqUKh1...ESaj3xCtBrCOREFlagged 27h+

Multi CPU -16.8% · Risk 100 · 28m lag · 3 failures

—

+0.4%

-16.8%

-0.0%

-16.8%

▸

—

5DAgxwhrzkVi1A...VN7k221j72COREFlagged 9h

Multi CPU -11.3% · Risk 100 · 23m lag · 5 failures

—

-0.4%

-11.3%

-0.0%

-11.3%

▸

—

5DbpyNBJ1R5WT2...d1F8f8YwMPCOREFlagged 10h

Multi CPU -33.0% · Single CPU -8.9% · Risk 100 · 6m lag · 2 failures

—

-8.9%

-33.0%

+0.0%

-33.0%

▸

—

5EWzHsvzvax6ji...daZrgvKvYjCOREFlagged 3h

Multi CPU -15.2% · Risk 100 · 19m lag · 73 failures

—

+0.1%

-15.2%

-0.0%

-15.2%

▸

—

5F8TPUrvdhYEQ5...zoSiFgFhwoCOREFlagged 9h

Multi CPU -34.6% · Single CPU -12.8% · Risk 100 · 12m lag · 1 failure

—

-12.8%

-34.6%

-0.0%

-34.6%

▸

—

5CKgb9bYZ2wSLW...FuLJwMEVhkCORE

2m lag · 603 failures

—

-0.0%

-1.3%

-0.0%

-1.3%

▸

—

5CMTnGE5Bg5BEM...5FXw8P4E5iCORE

4m lag · 693 failures

—

-0.2%

+4.0%

-0.0%

-0.2%

▸

—

5DMN6uFeDH6Qc2...kkT81wWNvRCORE

9m lag · 5 failures

Samsung Galaxy A03s

-0.5%

+5.0%

-0.0%

-0.5%

▸

—

5EYgfbPyeqWk9W...BydnWVgmSZCORE

37m lag · 659 failures

—

-0.0%

+2.8%

-0.0%

▸

—

5F6UdJ1CDaLiqz...WF4E7Kg7fdCORE

4m lag · 572 failures

—

+0.0%

+17.9%

-0.0%

▸

—

5F8M7ovthhWEeG...QjtFieVzifCORE

4m lag · 577 failures

—

-0.2%

+8.2%

+0.0%

-0.2%

▸

—

5FDJaCPvd8nzUQ...Ft5ohLRnmxCORE

15m lag · 406 failures

—

-1.2%

+41.6%

+0.0%

-1.2%

▸

—

5FF1Mvn9q6333d...THAaGrVMDxCORE

15m lag · 23 failures

Samsung Galaxy A03s

+3.7%

+17.8%

-0.0%

▸

—

5GGYMuSP5nfFo6...7e9fXigCHDCORE↑ 19 streak

34m lag · 653 failures

—

-1.2%

+60.7%

+0.0%

-1.2%

▸

—

5GUychBz7aRKFu...4wdNojumHiCORE↑ 22 streak

16m lag · 5 failures

—

+0.0%

-3.5%

-0.0%

-3.5%

▸

—

5H3aKhsbPgPCq8...vzLWDhVJWrCORE

7m lag · 5 failures

Samsung Galaxy A03s

+0.3%

-0.6%

+0.0%

-0.6%

▸

—

5H7W8sNEWVvfyC...psRawXfXH6CORE

12m lag · 9 failures

Motorola G Play 2024

+1.2%

-1.1%

-0.0%

-1.1%

▸

—

5HDkXTNtHguEHs...UHdKCNxgD4CORE↑ 10 streak

8m lag · 5 failures

Samsung Galaxy A03s

-4.3%

+3.7%

+0.0%

-4.3%

▸

—

5HJHz9vHHd8yN1...DFKeTcbvYqiOSFlagged 1h

Multi CPU -6.7% · 25m lag · 1 failure

—

-2.6%

-6.7%

+0.0%

-6.7%

▸

—

5FtNqaxQNz8gri...bHengnahP3COREFlagged 11h

Multi CPU -5.8% · 9m lag

Motorola G Play 2024

+0.3%

-5.8%

+0.0%

-5.8%

▸

—

5GygCeJ9GVxoxn...uZ6Ksf7uvHCOREFlagged 11h

Multi CPU -7.0% · 22m lag

—

-0.2%

-7.0%

0.0%

-7.0%

▸

—

5G2CKAUbUYfszF...rjChP3J8W9COREFlagged 24m

Multi CPU -7.4% · 31m lag · 485 failures

—

+0.0%

-7.4%

-0.0%

-7.4%

▸

—

5HMGZi25FUt41U...dNWmkdpAcGiOSFlagged 24m

Multi CPU -11.4% · 4m lag

—

+2.7%

-11.4%

+0.0%

-11.4%

▸

5CWummeF45n3La...CGCFppdnz8iOSdown · 9d lag

-0.0%▸

CPU 1c-0.0%

CPU Mc-0.0%

RAM-0.0%

Worst-0.0%

5GsVn27B96Ue2B...T9je2QTkstiOSdown · 31d lag

-0.0%▸

CPU 1c-0.0%

CPU Mc-0.0%

RAM+0.0%

Worst-0.0%

5DbJ8ZHXTSqw1i...s8KvZbtesSCOREdown · 1d lag · 3 failures

+0.0%▸

CPU 1c+0.1%

CPU Mc+5.3%

RAM+0.0%

Worst+0.0%

5EAYtwr646ah3A...NDaDgpiXHkiOSdown · 6h lag · 1 failure

-0.5%▸

CPU 1c+0.2%

CPU Mc-0.5%

RAM-0.0%

Worst-0.5%

5GnMRHXiQvXr6a...bL4coJpkQJCOREdown · 11h lag · 2 failures

-4.2%▸

CPU 1c+1.0%

CPU Mc-4.2%

RAM0.0%

Worst-4.2%

5GnBhXwGQfYW11...ha6SXoBHRwCOREdown · Risk 75 · 11h lag · 12 failures

-1.2%▸

CPU 1c+0.3%

CPU Mc-1.2%

RAM+0.0%

Worst-1.2%

5D3BzExHPjF3Tk...2hzZdcP1FxiOSdown · Single CPU -7.3% · Risk 100 · 10h lag

-7.3%▸

CPU 1c-7.3%

CPU Mc-1.5%

RAM+0.0%

Worst-7.3%

5FtUGnE3GDBxW6...J3NoK7cEFsiOSdown · Multi CPU -25.6% · Risk 100 · 10h lag · 1 failure

-25.6%▸

CPU 1c-3.4%

CPU Mc-25.6%

RAM+0.0%

Worst-25.6%

5G2Z58yBK8rC3e...zd5tgtKooEiOSdown · Multi CPU -20.3% · Risk 100 · 11h lag · 1 failure

-20.3%▸

CPU 1c-0.3%

CPU Mc-20.3%

RAM+0.0%

Worst-20.3%

5G6JZDpjpbRjLe...hyZ3f3Cv5fCOREMulti CPU -5.6% · Risk 77 · 7m lag · 1 failure

-5.6%▸

CPU 1c+11.0%

CPU Mc-5.6%

RAM-0.0%

Worst-5.6%

5EFpEnVdDXKc3f...ZgDJak6qCnCOREMulti CPU -7.2% · Risk 78 · 26m lag · 565 failures

-7.2%▸

CPU 1c-0.1%

CPU Mc-7.2%

RAM-0.0%

Worst-7.2%

5E7YUXhJfYGM1a...5X7LXuJ7tpCORESingle CPU -8.1% · Risk 87 · 24m lag · 4 failuresSamsung Galaxy A03s

-8.1%▸

CPU 1c-8.1%

CPU Mc+9.0%

RAM+0.0%

Worst-8.1%

5DJUN1onkSn9ai...QtLHwiGVSTCOREMulti CPU -6.4% · Risk 94 · 4m lag · 5 failures

-6.4%▸

CPU 1c+1.5%

CPU Mc-6.4%

RAM-0.0%

Worst-6.4%

5DMwU8243fosAY...Pgz4v3TzUWCORESingle CPU -6.3% · Risk 94 · 46m lag · 762 failuresSamsung Galaxy A03s

-6.3%▸

CPU 1c-6.3%

CPU Mc+0.7%

RAM-0.0%

Worst-6.3%

5C8MbSLo7ozTi7...rUaCmCzxFHLITEMulti CPU -32.1% · Risk 100 · 13m lag · 1 failureSamsung Galaxy A03s

-32.1%▸

CPU 1c+11.3%

CPU Mc-32.1%

RAM-0.0%

Worst-32.1%

5CEbh7tA17FXEJ...HbN4V62WoNCOREMulti CPU -13.8% · Risk 100 · 18m lag · 4 failures

-13.8%▸

CPU 1c+2.9%

CPU Mc-13.8%

RAM-0.0%

Worst-13.8%

5Cv7XR5qpqUKh1...ESaj3xCtBrCOREMulti CPU -16.8% · Risk 100 · 28m lag · 3 failures

-16.8%▸

CPU 1c+0.4%

CPU Mc-16.8%

RAM-0.0%

Worst-16.8%

5DAgxwhrzkVi1A...VN7k221j72COREMulti CPU -11.3% · Risk 100 · 23m lag · 5 failures

-11.3%▸

CPU 1c-0.4%

CPU Mc-11.3%

RAM-0.0%

Worst-11.3%

5DbpyNBJ1R5WT2...d1F8f8YwMPCOREMulti CPU -33.0% · Single CPU -8.9% · Risk 100 · 6m lag · 2 failures

-33.0%▸

CPU 1c-8.9%

CPU Mc-33.0%

RAM+0.0%

Worst-33.0%

5EWzHsvzvax6ji...daZrgvKvYjCOREMulti CPU -15.2% · Risk 100 · 19m lag · 73 failures

-15.2%▸

CPU 1c+0.1%

CPU Mc-15.2%

RAM-0.0%

Worst-15.2%

5F8TPUrvdhYEQ5...zoSiFgFhwoCOREMulti CPU -34.6% · Single CPU -12.8% · Risk 100 · 12m lag · 1 failure

-34.6%▸

CPU 1c-12.8%

CPU Mc-34.6%

RAM-0.0%

Worst-34.6%

5CKgb9bYZ2wSLW...FuLJwMEVhkCORE2m lag · 603 failures

-1.3%▸

CPU 1c-0.0%

CPU Mc-1.3%

RAM-0.0%

Worst-1.3%

5CMTnGE5Bg5BEM...5FXw8P4E5iCORE4m lag · 693 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+4.0%

RAM-0.0%

Worst-0.2%

5DMN6uFeDH6Qc2...kkT81wWNvRCORE9m lag · 5 failuresSamsung Galaxy A03s

-0.5%▸

CPU 1c-0.5%

CPU Mc+5.0%

RAM-0.0%

Worst-0.5%

5EYgfbPyeqWk9W...BydnWVgmSZCORE37m lag · 659 failures

-0.0%▸

CPU 1c-0.0%

CPU Mc+2.8%

RAM-0.0%

Worst-0.0%

5F6UdJ1CDaLiqz...WF4E7Kg7fdCORE4m lag · 572 failures

-0.0%▸

CPU 1c+0.0%

CPU Mc+17.9%

RAM-0.0%

Worst-0.0%

5F8M7ovthhWEeG...QjtFieVzifCORE4m lag · 577 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+8.2%

RAM+0.0%

Worst-0.2%

5FDJaCPvd8nzUQ...Ft5ohLRnmxCORE15m lag · 406 failures

-1.2%▸

CPU 1c-1.2%

CPU Mc+41.6%

RAM+0.0%

Worst-1.2%

5FF1Mvn9q6333d...THAaGrVMDxCORE15m lag · 23 failuresSamsung Galaxy A03s

-0.0%▸

CPU 1c+3.7%

CPU Mc+17.8%

RAM-0.0%

Worst-0.0%

5GGYMuSP5nfFo6...7e9fXigCHDCORE34m lag · 653 failures

-1.2%▸

CPU 1c-1.2%

CPU Mc+60.7%

RAM+0.0%

Worst-1.2%

5GUychBz7aRKFu...4wdNojumHiCORE16m lag · 5 failures

-3.5%▸

CPU 1c+0.0%

CPU Mc-3.5%

RAM-0.0%

Worst-3.5%

5H3aKhsbPgPCq8...vzLWDhVJWrCORE7m lag · 5 failuresSamsung Galaxy A03s

-0.6%▸

CPU 1c+0.3%

CPU Mc-0.6%

RAM+0.0%

Worst-0.6%

5H7W8sNEWVvfyC...psRawXfXH6CORE12m lag · 9 failuresMotorola G Play 2024

-1.1%▸

CPU 1c+1.2%

CPU Mc-1.1%

RAM-0.0%

Worst-1.1%

5HDkXTNtHguEHs...UHdKCNxgD4CORE8m lag · 5 failuresSamsung Galaxy A03s

-4.3%▸

CPU 1c-4.3%

CPU Mc+3.7%

RAM+0.0%

Worst-4.3%

5HJHz9vHHd8yN1...DFKeTcbvYqiOSMulti CPU -6.7% · 25m lag · 1 failure

-6.7%▸

CPU 1c-2.6%

CPU Mc-6.7%

RAM+0.0%

Worst-6.7%

5FtNqaxQNz8gri...bHengnahP3COREMulti CPU -5.8% · 9m lagMotorola G Play 2024

-5.8%▸

CPU 1c+0.3%

CPU Mc-5.8%

RAM+0.0%

Worst-5.8%

5GygCeJ9GVxoxn...uZ6Ksf7uvHCOREMulti CPU -7.0% · 22m lag

-7.0%▸

CPU 1c-0.2%

CPU Mc-7.0%

RAM0.0%

Worst-7.0%

5G2CKAUbUYfszF...rjChP3J8W9COREMulti CPU -7.4% · 31m lag · 485 failures

-7.4%▸

CPU 1c+0.0%

CPU Mc-7.4%

RAM-0.0%

Worst-7.4%

5HMGZi25FUt41U...dNWmkdpAcGiOSMulti CPU -11.4% · 4m lag

-11.4%▸

CPU 1c+2.7%

CPU Mc-11.4%

RAM+0.0%

Worst-11.4%