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

Manager #2273 · compute baseline

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

76.1% healthy·30d↓3.0pp

LiveUpdated just now·use cached

134 devices

102Healthy

5Watch

27Investigate

0Low confidence

28Regressions

31Improving

0Stale heartbeat

27Failures

3.9ACU/day at risk

Non-Green 32 Investigate 27 Watch 5 Healthy 102 Improving 31▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare

▥ Investigate in Compare (27) ▾

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

Model	Devices	Healthy	Watch	Investigate	% Healthy	Improving
Untagged	20	0	2	18	0.0%	0
Samsung Z Flip 3	2	0	0	2	0.0%	0
BLU View 4

ModelBuildSortShowing 32 of 32

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

—

5E64Cs4aB76px6...ZDk3eHrFEYCOREFlagged 26h

Single CPU -6.1% · Risk 77 · 16m lag · 2 failures

BLU View 4

-6.1%

-2.1%

-0.0%

-6.1%

▸

—

5EuDm3zEsuasja...65K8bnxtswCOREFlagged 7h

Single CPU -8.3% · Risk 77 · 30m lag · 2 failures

—

-8.3%

+11.5%

-0.0%

-8.3%

▸

—

5Fx6K5fHidaS14...VzXfGy7hakCOREFlagged 28h+

Multi CPU -5.3% · Risk 77 · 6m lag · 2 failures

—

-0.1%

-5.3%

+0.0%

-5.3%

▸

—

5GLJkU19HBm42n...LGwNixJ9d3COREFlagged 27h

Multi CPU -7.0% · Risk 77 · 12m lag · 2 failures

Samsung Fold 2 5G

+0.0%

-7.0%

-0.0%

-7.0%

▸

—

5HD6CH2s777v6Q...io5cJXPdnMCOREFlagged 7h

Multi CPU -8.2% · Risk 77 · 31m lag · 1 failure

Google Pixel 5

-0.3%

-8.2%

-0.0%

-8.2%

▸

—

5HEtdU9UrrRS52...KCe4ms4rnVCOREFlagged 28h+

Multi CPU -8.3% · Risk 77 · 25m lag · 1 failure

—

-2.6%

-8.3%

+0.0%

-8.3%

▸

—

5HJTzChDahwKuq...PzY2BLh9jRCOREFlagged 13h

Single CPU -7.5% · Risk 77 · 11m lag · 1 failure

BLU View 4

-7.5%

-3.8%

-0.0%

-7.5%

▸

—

5EH8Rhonj2Gq6B...YBvLc3EvaoCOREFlagged 22h

Multi CPU -6.1% · Risk 87 · 20m lag · 3 failures

—

+0.1%

-6.1%

-0.0%

-6.1%

▸

—

5FZqSn58mJZXHE...MEU6dZz6iPCOREFlagged 28h+

Multi CPU -8.0% · Risk 87 · 29m lag · 3 failures

—

+15.7%

-8.0%

+0.0%

-8.0%

▸

—

5HfhsX36YPYYKg...amGbK7qZAMCOREFlagged 8h

Multi CPU -6.5% · Risk 87 · 10m lag · 3 failures

—

-0.9%

-6.5%

+0.0%

-6.5%

▸

—

5HHzet6bbT8eQj...RbKVLKPGGhLITEFlagged 18h

Multi CPU -6.3% · Risk 87 · 12m lag · 3 failures

—

+0.1%

-6.3%

+0.0%

-6.3%

▸

—

5CnMge8bGaTAEy...FnkBeRD3zCCOREFlagged 24h

Multi CPU -9.1% · Risk 94 · 15m lag · 6 failures

—

-0.7%

-9.1%

+0.0%

-9.1%

▸

—

5Cu5d4hAZvPesv...H7wJvUeaVUCOREFlagged 22h

Multi CPU -14.7% · Risk 95 · 31m lag

—

+0.1%

-14.7%

-0.0%

-14.7%

▸

—

5CCswAWG9yJxfg...ipsU1HgqYTCOREFlagged 8h

Multi CPU -23.6% · Risk 100 · 8m lag · 1 failure

Samsung Galaxy A71

-3.6%

-23.6%

-0.0%

-23.6%

▸

—

5CD7zdpPemTGyx...Lo7LtNskorCOREFlagged 28h+

Multi CPU -67.8% · Single CPU -34.1% · Risk 100 · 26m lag · 1 failure

Samsung Flip 5

-34.1%

-67.8%

-0.0%

-67.8%

▸

—

5CETiUji1kcef8...MQkWupZohyCOREFlagged 28h+

Multi CPU -25.0% · Risk 100 · 8m lag · 3 failures

—

-0.4%

-25.0%

+0.0%

-25.0%

▸

—

5De7JS1j1rznBY...bowPT769s6LITEFlagged 13h

Multi CPU -64.5% · Single CPU -51.7% · Risk 100 · 9m lag · 2 failures

—

-51.7%

-64.5%

-0.0%

-64.5%

▸

—

5Dovzvx8SYexpv...kGvPw7jCA1COREFlagged 1h

Multi CPU -22.6% · Risk 100 · 29m lag · 3 failures

—

-3.4%

-22.6%

+0.0%

-22.6%

▸

—

5DZihMiRPabguM...WNQCkuaA5TCOREFlagged 8h

Multi CPU -21.2% · Risk 100 · 14m lag · 2 failures

—

-1.2%

-21.2%

-0.0%

-21.2%

▸

—

5EbNRypByP8387...4vLhg4wgPMCOREFlagged 28h+

Multi CPU -27.1% · Risk 100 · 14m lag · 2 failures

—

-1.3%

-27.1%

+0.0%

-27.1%

▸

—

5Erkyz5wMfQVaZ...XTXiqTns9cCOREFlagged 21h

Multi CPU -11.8% · Risk 100 · 14m lag · 1 failure

—

-0.1%

-11.8%

+0.0%

-11.8%

▸

—

5GJB6AJ7dfps4e...oRQpHML9GzLITEFlagged 13h

Single CPU -83.7% · Multi CPU -71.8% · Risk 100 · 26m lag

Samsung Z Flip 3

-83.7%

-71.8%

+0.0%

-83.7%

▸

—

5GmoEdmvT6UDUF...XxTAMvFT7SCOREFlagged 13h

Single CPU -24.5% · Risk 100 · 26m lag · 2 failures

—

-24.5%

+19.9%

-0.0%

-24.5%

▸

—

5GpgQdvShjnJke...ezvnbwt1A9COREFlagged 24h

Multi CPU -13.5% · Risk 100 · 12m lag · 1 failure

Google Pixel 6

+0.1%

-13.5%

-0.0%

-13.5%

▸

—

5GpSJreMby1U1J...dg643MtbRsLITEFlagged 27h

Single CPU -83.9% · Multi CPU -70.7% · Risk 100 · 14m lag

Samsung Z Flip 3

-83.9%

-70.7%

-0.0%

-83.9%

▸

—

5GRpuU8HWya8Um...DLTjPtJwqrLITEFlagged 13h

Multi CPU -66.4% · Single CPU -51.7% · Risk 100 · 4m lag · 1 failure

—

-51.7%

-66.4%

-0.0%

-66.4%

▸

—

5HTMGEPCPvWznS...wPuYcLLE5XLITEFlagged 24h

Multi CPU -61.1% · Single CPU -47.0% · Risk 100 · 14m lag · 2 failures

—

-47.0%

-61.1%

-0.0%

-61.1%

▸

—

5GcpxExeBXmmnb...T6AaTkrLviCORE

17m lag · 7 failures

Google Pixel 6a

-1.1%

-2.0%

0.0%

-2.0%

▸

—

5GnMiQL96SGZvp...Tr23fp8p7XCORE

18m lag · 5 failures

—

+0.3%

-0.9%

+0.0%

-0.9%

▸

—

5GLMhzYRhxxFFi...LczXkfCJWZCOREFlagged 1h

Multi CPU -9.4% · 14m lag

Samsung Z Fold 3

+0.4%

-9.4%

-0.0%

-9.4%

▸

—

5DoTBTLFUxSwsQ...uYR6JgBdbNCOREFlagged 2h

Single CPU -5.5% · 7m lag

Xiaomi 11T Pro

-5.5%

-3.8%

-0.0%

-5.5%

▸

—

5Efv6zBcsVWcfi...vJ57JZBrWiCOREFlagged 13h

Multi CPU -7.5% · 6m lag

—

-0.1%

-7.5%

+0.0%

-7.5%

▸

5E64Cs4aB76px6...ZDk3eHrFEYCORESingle CPU -6.1% · Risk 77 · 16m lag · 2 failuresBLU View 4

-6.1%▸

CPU 1c-6.1%

CPU Mc-2.1%

RAM-0.0%

Worst-6.1%

5EuDm3zEsuasja...65K8bnxtswCORESingle CPU -8.3% · Risk 77 · 30m lag · 2 failures

-8.3%▸

CPU 1c-8.3%

CPU Mc+11.5%

RAM-0.0%

Worst-8.3%

5Fx6K5fHidaS14...VzXfGy7hakCOREMulti CPU -5.3% · Risk 77 · 6m lag · 2 failures

-5.3%▸

CPU 1c-0.1%

CPU Mc-5.3%

RAM+0.0%

Worst-5.3%

5GLJkU19HBm42n...LGwNixJ9d3COREMulti CPU -7.0% · Risk 77 · 12m lag · 2 failuresSamsung Fold 2 5G

-7.0%▸

CPU 1c+0.0%

CPU Mc-7.0%

RAM-0.0%

Worst-7.0%

5HD6CH2s777v6Q...io5cJXPdnMCOREMulti CPU -8.2% · Risk 77 · 31m lag · 1 failureGoogle Pixel 5

-8.2%▸

CPU 1c-0.3%

CPU Mc-8.2%

RAM-0.0%

Worst-8.2%

5HEtdU9UrrRS52...KCe4ms4rnVCOREMulti CPU -8.3% · Risk 77 · 25m lag · 1 failure

-8.3%▸

CPU 1c-2.6%

CPU Mc-8.3%

RAM+0.0%

Worst-8.3%

5HJTzChDahwKuq...PzY2BLh9jRCORESingle CPU -7.5% · Risk 77 · 11m lag · 1 failureBLU View 4

-7.5%▸

CPU 1c-7.5%

CPU Mc-3.8%

RAM-0.0%

Worst-7.5%

5EH8Rhonj2Gq6B...YBvLc3EvaoCOREMulti CPU -6.1% · Risk 87 · 20m lag · 3 failures

-6.1%▸

CPU 1c+0.1%

CPU Mc-6.1%

RAM-0.0%

Worst-6.1%

5FZqSn58mJZXHE...MEU6dZz6iPCOREMulti CPU -8.0% · Risk 87 · 29m lag · 3 failures

-8.0%▸

CPU 1c+15.7%

CPU Mc-8.0%

RAM+0.0%

Worst-8.0%

5HfhsX36YPYYKg...amGbK7qZAMCOREMulti CPU -6.5% · Risk 87 · 10m lag · 3 failures

-6.5%▸

CPU 1c-0.9%

CPU Mc-6.5%

RAM+0.0%

Worst-6.5%

5HHzet6bbT8eQj...RbKVLKPGGhLITEMulti CPU -6.3% · Risk 87 · 12m lag · 3 failures

-6.3%▸

CPU 1c+0.1%

CPU Mc-6.3%

RAM+0.0%

Worst-6.3%

5CnMge8bGaTAEy...FnkBeRD3zCCOREMulti CPU -9.1% · Risk 94 · 15m lag · 6 failures

-9.1%▸

CPU 1c-0.7%

CPU Mc-9.1%

RAM+0.0%

Worst-9.1%

5Cu5d4hAZvPesv...H7wJvUeaVUCOREMulti CPU -14.7% · Risk 95 · 31m lag

-14.7%▸

CPU 1c+0.1%

CPU Mc-14.7%

RAM-0.0%

Worst-14.7%

5CCswAWG9yJxfg...ipsU1HgqYTCOREMulti CPU -23.6% · Risk 100 · 8m lag · 1 failureSamsung Galaxy A71

-23.6%▸

CPU 1c-3.6%

CPU Mc-23.6%

RAM-0.0%

Worst-23.6%

5CD7zdpPemTGyx...Lo7LtNskorCOREMulti CPU -67.8% · Single CPU -34.1% · Risk 100 · 26m lag · 1 failureSamsung Flip 5

-67.8%▸

CPU 1c-34.1%

CPU Mc-67.8%

RAM-0.0%

Worst-67.8%

5CETiUji1kcef8...MQkWupZohyCOREMulti CPU -25.0% · Risk 100 · 8m lag · 3 failures

-25.0%▸

CPU 1c-0.4%

CPU Mc-25.0%

RAM+0.0%

Worst-25.0%

5De7JS1j1rznBY...bowPT769s6LITEMulti CPU -64.5% · Single CPU -51.7% · Risk 100 · 9m lag · 2 failures

-64.5%▸

CPU 1c-51.7%

CPU Mc-64.5%

RAM-0.0%

Worst-64.5%

5Dovzvx8SYexpv...kGvPw7jCA1COREMulti CPU -22.6% · Risk 100 · 29m lag · 3 failures

-22.6%▸

CPU 1c-3.4%

CPU Mc-22.6%

RAM+0.0%

Worst-22.6%

5DZihMiRPabguM...WNQCkuaA5TCOREMulti CPU -21.2% · Risk 100 · 14m lag · 2 failures

-21.2%▸

CPU 1c-1.2%

CPU Mc-21.2%

RAM-0.0%

Worst-21.2%

5EbNRypByP8387...4vLhg4wgPMCOREMulti CPU -27.1% · Risk 100 · 14m lag · 2 failures

-27.1%▸

CPU 1c-1.3%

CPU Mc-27.1%

RAM+0.0%

Worst-27.1%

5Erkyz5wMfQVaZ...XTXiqTns9cCOREMulti CPU -11.8% · Risk 100 · 14m lag · 1 failure

-11.8%▸

CPU 1c-0.1%

CPU Mc-11.8%

RAM+0.0%

Worst-11.8%

5GJB6AJ7dfps4e...oRQpHML9GzLITESingle CPU -83.7% · Multi CPU -71.8% · Risk 100 · 26m lagSamsung Z Flip 3

-83.7%▸

CPU 1c-83.7%

CPU Mc-71.8%

RAM+0.0%

Worst-83.7%

5GmoEdmvT6UDUF...XxTAMvFT7SCORESingle CPU -24.5% · Risk 100 · 26m lag · 2 failures

-24.5%▸

CPU 1c-24.5%

CPU Mc+19.9%

RAM-0.0%

Worst-24.5%

5GpgQdvShjnJke...ezvnbwt1A9COREMulti CPU -13.5% · Risk 100 · 12m lag · 1 failureGoogle Pixel 6

-13.5%▸

CPU 1c+0.1%

CPU Mc-13.5%

RAM-0.0%

Worst-13.5%

5GpSJreMby1U1J...dg643MtbRsLITESingle CPU -83.9% · Multi CPU -70.7% · Risk 100 · 14m lagSamsung Z Flip 3

-83.9%▸

CPU 1c-83.9%

CPU Mc-70.7%

RAM-0.0%

Worst-83.9%

5GRpuU8HWya8Um...DLTjPtJwqrLITEMulti CPU -66.4% · Single CPU -51.7% · Risk 100 · 4m lag · 1 failure

-66.4%▸

CPU 1c-51.7%

CPU Mc-66.4%

RAM-0.0%

Worst-66.4%

5HTMGEPCPvWznS...wPuYcLLE5XLITEMulti CPU -61.1% · Single CPU -47.0% · Risk 100 · 14m lag · 2 failures

-61.1%▸

CPU 1c-47.0%

CPU Mc-61.1%

RAM-0.0%

Worst-61.1%

5GcpxExeBXmmnb...T6AaTkrLviCORE17m lag · 7 failuresGoogle Pixel 6a

-2.0%▸

CPU 1c-1.1%

CPU Mc-2.0%

RAM0.0%

Worst-2.0%

5GnMiQL96SGZvp...Tr23fp8p7XCORE18m lag · 5 failures

-0.9%▸

CPU 1c+0.3%

CPU Mc-0.9%

RAM+0.0%

Worst-0.9%

5GLMhzYRhxxFFi...LczXkfCJWZCOREMulti CPU -9.4% · 14m lagSamsung Z Fold 3

-9.4%▸

CPU 1c+0.4%

CPU Mc-9.4%

RAM-0.0%

Worst-9.4%

5DoTBTLFUxSwsQ...uYR6JgBdbNCORESingle CPU -5.5% · 7m lagXiaomi 11T Pro

-5.5%▸

CPU 1c-5.5%

CPU Mc-3.8%

RAM-0.0%

Worst-5.5%

5Efv6zBcsVWcfi...vJ57JZBrWiCOREMulti CPU -7.5% · 6m lag

-7.5%▸

CPU 1c-0.1%

CPU Mc-7.5%

RAM+0.0%

Worst-7.5%