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

Manager #2311 · compute baseline

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

57.6% healthy·30d↓9.8pp

LiveUpdated just now·use cached

92 devices

49Healthy

17Watch

26Investigate

0Low confidence

25Regressions

20Improving

7Stale heartbeat

26Failures

0.8ACU/day at risk

Non-Green 43 Investigate 26 Watch 17 Healthy 49 Improving 20▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare ▥ Improving in Compare (8)

▥ Investigate in Compare (26) ▾

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	37	0	17	20	0.0%	8
Motorola G Play 2024	5	0	0	5	0.0%	0
Samsung Galaxy A15 5G

ModelBuildSortShowing 43 of 43

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

—

5Cfei3SNkZB8AH...ABM3DHLDxTCORE

down · 9h lag

—

-0.1%

+16.3%

+0.0%

-0.1%

▸

—

5CuAWLqiZXR3uB...gSQcyhsycpCORE

down · 14h lag · 4 failures

—

+0.0%

-4.9%

-0.0%

-4.9%

▸

—

5EN8wYdCjudPMa...4NYdDkHNvGCORE

down · 9h lag · 4 failures

—

+0.3%

-1.9%

-0.0%

-1.9%

▸

—

5ER2os2tcATqyV...3qNDiA4w9tCORE

down · 9h lag · 3 failures

—

-0.4%

+0.4%

-0.0%

-0.4%

▸

—

5Gf2XPZJxfv9Df...L3xtVXSYqNCORE

down · Risk 75 · 9h lag · 8 failures

—

-0.2%

+12.8%

-0.0%

-0.2%

▸

—

5FDumv5ewzamhg...f3TdXGY4L8COREFlagged 22h

down · Multi CPU -35.5% · Risk 100 · 9h lag · 3 failures

—

-0.6%

-35.5%

+0.0%

-35.5%

▸

—

5GB3ieB1hWTYc4...dDKXMbQy2UCOREFlagged 21h

down · Single CPU -5.4% · Risk 100 · 9h lag · 5 failures

—

-5.4%

+24.3%

+0.0%

-5.4%

▸

—

5D7GwLc1uBXgFx...gEWu3xfdQkCOREFlagged 5h

Multi CPU -9.9% · Risk 77 · 4m lag · 1 failure

Motorola G Play 2024

-3.0%

-9.9%

-0.0%

-9.9%

▸

—

5DdQF4dfuUZPN7...ySfwYvLCN4COREFlagged 5h

Multi CPU -9.7% · Risk 77 · 30m lag · 1 failure

Motorola G Play 2024

+0.6%

-9.7%

-0.0%

-9.7%

▸

—

5DRvdwBwgHoZhV...pi26kkve3PCOREFlagged 26h

Multi CPU -6.9% · Risk 77 · 4m lag · 1 failure

—

+0.3%

-6.9%

+0.0%

-6.9%

▸

—

5EuZUUK1sySQKS...KrUgCcpiuiCOREFlagged 36h+

Multi CPU -9.7% · Risk 77 · 24m lag · 1 failure

—

-0.9%

-9.7%

0.0%

-9.7%

▸

—

5ExbPX6q6EbfUS...xSz76Q3g6RCOREFlagged 15h

Multi CPU -8.6% · Risk 77 · 8m lag · 1 failure

Motorola G Play 2024

-0.1%

-8.6%

+0.0%

-8.6%

▸

—

5Fx7uH22YtLMrD...LRH1UpWL5RCOREFlagged 6h

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

—

-3.2%

-5.9%

0.0%

-5.9%

▸

—

5G4RhLL84TYNvi...B2kDc5Afz1COREFlagged 8h

Multi CPU -6.6% · Risk 77 · 7m lag · 2 failures

—

-1.8%

-6.6%

+0.0%

-6.6%

▸

—

5GGEvZ5W5iega7...QKyAU1RjS5COREFlagged 29h

Multi CPU -7.8% · Risk 77 · 24m lag · 2 failures

—

-0.4%

-7.8%

0.0%

-7.8%

▸

—

5GWUo6vi9ggRwa...UMAoyXHC8sCOREFlagged 17h

Multi CPU -7.7% · Risk 77 · 19m lag · 1 failure

—

-0.0%

-7.7%

+0.0%

-7.7%

▸

—

5HQUhmZZqGdQMJ...2BCwsjSxdfCOREFlagged 36h+

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

—

+0.2%

-8.3%

-0.0%

-8.3%

▸

—

5DGs2G6mGHxHJY...c3TXZF7e7sCOREFlagged 6h

Multi CPU -5.8% · Risk 87 · 8m lag · 3 failures

—

-3.2%

-5.8%

0.0%

-5.8%

▸

—

5DwgLEkGHZMkWy...FnDpUE7Q2rCOREFlagged 32h

Multi CPU -8.2% · Single CPU -7.6% · Risk 87 · 5m lag · 4 failures

—

-7.6%

-8.2%

0.0%

-8.2%

▸

—

5GcvL3vbdzAvjh...1Mk2zZxAaxCOREFlagged 11h

Multi CPU -9.8% · Risk 87 · 4m lag · 3 failures

Motorola G Play 2024

+1.3%

-9.8%

+0.0%

-9.8%

▸

—

5GGtd4iGHCewJw...3asSui3yvzCOREFlagged 9h

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

—

-3.1%

-8.0%

-0.0%

-8.0%

▸

—

5G7gMpbAPVexbM...8NZ9xzt2MjCOREFlagged 2h

Multi CPU -8.5% · Risk 88 · 9m lag · 9 failures

Samsung Galaxy A15 5G

+0.0%

-8.5%

+0.0%

-8.5%

▸

—

5GUbCQkYnKYfJX...YLKJirxqzSCOREFlagged 2h

Multi CPU -15.0% · Risk 89 · 7m lag

—

-0.6%

-15.0%

+0.0%

-15.0%

▸

—

5GhoS2g8uJZQ5h...CqHKzmNkRcCOREFlagged 11h

Multi CPU -8.0% · Risk 94 · 9m lag · 5 failures

—

-4.5%

-8.0%

0.0%

-8.0%

▸

—

5CNuFTnLMqSpvv...tXaqFrC9hDCOREFlagged 36h+

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

—

-2.2%

-19.8%

+0.0%

-19.8%

▸

—

5CSfSj68QfmxXz...5PMxqdL62FCOREFlagged 21h

Multi CPU -13.3% · Risk 100 · 11m lag · 7 failures

—

-0.9%

-13.3%

+0.0%

-13.3%

▸

—

5D7Kr1VPGCW8jr...vofMRhuzPQCOREFlagged 36h+

Multi CPU -21.8% · Risk 100 · 4m lag · 12 failures

—

-0.4%

-21.8%

0.0%

-21.8%

▸

—

5DudAJr7Y9KFve...DnM9tCDiwXCOREFlagged 32h

Multi CPU -12.4% · Risk 100 · 6m lag · 7 failures

—

-3.1%

-12.4%

0.0%

-12.4%

▸

—

5F2AJ91NXYstwn...YjvWbqPESCCOREFlagged 3h

Multi CPU -10.6% · Risk 100 · 28m lag · 1 failure

Motorola G Play 2024

+0.4%

-10.6%

0.0%

-10.6%

▸

—

5FTohYhW9JbgfQ...Kek15iAk18COREFlagged 21h

Multi CPU -43.4% · Single CPU -5.8% · Risk 100 · 8m lag · 4 failures

—

-5.8%

-43.4%

+0.0%

-43.4%

▸

—

5Cfedb7KkkHbNm...g9nt8XyX5XCORE↑ 3 streak

3m lag · 9 failures

—

-0.3%

-4.0%

+0.0%

-4.0%

▸

—

5CFwcwT8njCpfp...942nXW986fCORE↑ 4 streak

4m lag · 6 failures

—

-1.7%

+4.5%

+0.0%

-1.7%

▸

—

5CgLrFGx8K6h6V...eBiDWah9DDCORE

7m lag · 7 failures

—

-0.3%

-2.8%

0.0%

-2.8%

▸

—

5DgKHxQQzurxR5...F588ws4E8dCORE

8m lag · 5 failures

—

-2.6%

-0.7%

0.0%

-2.6%

▸

—

5Dt99waJXeGH6P...KQ3JeMSPstCORE

24m lag · 8 failures

—

-0.3%

-2.8%

0.0%

-2.8%

▸

—

5DTU9aZBN6uDaP...5obZME8yN1CORE↑ 6 streak

7m lag · 5 failures

—

-1.2%

+3.5%

0.0%

-1.2%

▸

—

5E7Zg8B7mfibru...6xazwt8Gz4CORE↑ 4 streak

7m lag · 7 failures

—

-4.7%

-4.6%

0.0%

-4.7%

▸

—

5ETL19rZnbdhSn...CSJSd9wfq2CORE

4m lag · 5 failures

—

-0.2%

+0.9%

+0.0%

-0.2%

▸

—

5EvBEAPYzKvdZS...fG2s94ZZZTCORE↑ 22 streak

5m lag · 8 failures

—

+0.5%

-3.9%

+0.0%

-3.9%

▸

—

5ExVUBVBrhwfkp...Vh7qaUVq2CCORE↑ 3 streak

23m lag · 7 failures

—

-4.8%

+8.8%

0.0%

-4.8%

▸

—

5FGx7XSbKtD9F1...5knqw9MzqiCORE↑ 19 streak

20m lag · 6 failures

—

-0.2%

+2.9%

+0.0%

-0.2%

▸

—

5FXRCFeLa4gidD...cKsEkyqHVTCORE

26m lag · 5 failures

—

+0.3%

+6.2%

-0.0%

▸

—

5Gf2NwQp7cvDGu...bbKwZDVrscCORE↑ 26 streak

26m lag · 5 failures

—

-2.6%

-0.1%

0.0%

-2.6%

▸

5Cfei3SNkZB8AH...ABM3DHLDxTCOREdown · 9h lag

-0.1%▸

CPU 1c-0.1%

CPU Mc+16.3%

RAM+0.0%

Worst-0.1%

5CuAWLqiZXR3uB...gSQcyhsycpCOREdown · 14h lag · 4 failures

-4.9%▸

CPU 1c+0.0%

CPU Mc-4.9%

RAM-0.0%

Worst-4.9%

5EN8wYdCjudPMa...4NYdDkHNvGCOREdown · 9h lag · 4 failures

-1.9%▸

CPU 1c+0.3%

CPU Mc-1.9%

RAM-0.0%

Worst-1.9%

5ER2os2tcATqyV...3qNDiA4w9tCOREdown · 9h lag · 3 failures

-0.4%▸

CPU 1c-0.4%

CPU Mc+0.4%

RAM-0.0%

Worst-0.4%

5Gf2XPZJxfv9Df...L3xtVXSYqNCOREdown · Risk 75 · 9h lag · 8 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+12.8%

RAM-0.0%

Worst-0.2%

5FDumv5ewzamhg...f3TdXGY4L8COREdown · Multi CPU -35.5% · Risk 100 · 9h lag · 3 failures

-35.5%▸

CPU 1c-0.6%

CPU Mc-35.5%

RAM+0.0%

Worst-35.5%

5GB3ieB1hWTYc4...dDKXMbQy2UCOREdown · Single CPU -5.4% · Risk 100 · 9h lag · 5 failures

-5.4%▸

CPU 1c-5.4%

CPU Mc+24.3%

RAM+0.0%

Worst-5.4%

5D7GwLc1uBXgFx...gEWu3xfdQkCOREMulti CPU -9.9% · Risk 77 · 4m lag · 1 failureMotorola G Play 2024

-9.9%▸

CPU 1c-3.0%

CPU Mc-9.9%

RAM-0.0%

Worst-9.9%

5DdQF4dfuUZPN7...ySfwYvLCN4COREMulti CPU -9.7% · Risk 77 · 30m lag · 1 failureMotorola G Play 2024

-9.7%▸

CPU 1c+0.6%

CPU Mc-9.7%

RAM-0.0%

Worst-9.7%

5DRvdwBwgHoZhV...pi26kkve3PCOREMulti CPU -6.9% · Risk 77 · 4m lag · 1 failure

-6.9%▸

CPU 1c+0.3%

CPU Mc-6.9%

RAM+0.0%

Worst-6.9%

5EuZUUK1sySQKS...KrUgCcpiuiCOREMulti CPU -9.7% · Risk 77 · 24m lag · 1 failure

-9.7%▸

CPU 1c-0.9%

CPU Mc-9.7%

RAM0.0%

Worst-9.7%

5ExbPX6q6EbfUS...xSz76Q3g6RCOREMulti CPU -8.6% · Risk 77 · 8m lag · 1 failureMotorola G Play 2024

-8.6%▸

CPU 1c-0.1%

CPU Mc-8.6%

RAM+0.0%

Worst-8.6%

5Fx7uH22YtLMrD...LRH1UpWL5RCOREMulti CPU -5.9% · Risk 77 · 12m lag · 2 failures

-5.9%▸

CPU 1c-3.2%

CPU Mc-5.9%

RAM0.0%

Worst-5.9%

5G4RhLL84TYNvi...B2kDc5Afz1COREMulti CPU -6.6% · Risk 77 · 7m lag · 2 failures

-6.6%▸

CPU 1c-1.8%

CPU Mc-6.6%

RAM+0.0%

Worst-6.6%

5GGEvZ5W5iega7...QKyAU1RjS5COREMulti CPU -7.8% · Risk 77 · 24m lag · 2 failures

-7.8%▸

CPU 1c-0.4%

CPU Mc-7.8%

RAM0.0%

Worst-7.8%

5GWUo6vi9ggRwa...UMAoyXHC8sCOREMulti CPU -7.7% · Risk 77 · 19m lag · 1 failure

-7.7%▸

CPU 1c-0.0%

CPU Mc-7.7%

RAM+0.0%

Worst-7.7%

5HQUhmZZqGdQMJ...2BCwsjSxdfCOREMulti CPU -8.3% · Risk 77 · 21m lag · 1 failure

-8.3%▸

CPU 1c+0.2%

CPU Mc-8.3%

RAM-0.0%

Worst-8.3%

5DGs2G6mGHxHJY...c3TXZF7e7sCOREMulti CPU -5.8% · Risk 87 · 8m lag · 3 failures

-5.8%▸

CPU 1c-3.2%

CPU Mc-5.8%

RAM0.0%

Worst-5.8%

5DwgLEkGHZMkWy...FnDpUE7Q2rCOREMulti CPU -8.2% · Single CPU -7.6% · Risk 87 · 5m lag · 4 failures

-8.2%▸

CPU 1c-7.6%

CPU Mc-8.2%

RAM0.0%

Worst-8.2%

5GcvL3vbdzAvjh...1Mk2zZxAaxCOREMulti CPU -9.8% · Risk 87 · 4m lag · 3 failuresMotorola G Play 2024

-9.8%▸

CPU 1c+1.3%

CPU Mc-9.8%

RAM+0.0%

Worst-9.8%

5GGtd4iGHCewJw...3asSui3yvzCOREMulti CPU -8.0% · Risk 87 · 6m lag · 3 failures

-8.0%▸

CPU 1c-3.1%

CPU Mc-8.0%

RAM-0.0%

Worst-8.0%

5G7gMpbAPVexbM...8NZ9xzt2MjCOREMulti CPU -8.5% · Risk 88 · 9m lag · 9 failuresSamsung Galaxy A15 5G

-8.5%▸

CPU 1c+0.0%

CPU Mc-8.5%

RAM+0.0%

Worst-8.5%

5GUbCQkYnKYfJX...YLKJirxqzSCOREMulti CPU -15.0% · Risk 89 · 7m lag

-15.0%▸

CPU 1c-0.6%

CPU Mc-15.0%

RAM+0.0%

Worst-15.0%

5GhoS2g8uJZQ5h...CqHKzmNkRcCOREMulti CPU -8.0% · Risk 94 · 9m lag · 5 failures

-8.0%▸

CPU 1c-4.5%

CPU Mc-8.0%

RAM0.0%

Worst-8.0%

5CNuFTnLMqSpvv...tXaqFrC9hDCOREMulti CPU -19.8% · Risk 100 · 9m lag · 1 failure

-19.8%▸

CPU 1c-2.2%

CPU Mc-19.8%

RAM+0.0%

Worst-19.8%

5CSfSj68QfmxXz...5PMxqdL62FCOREMulti CPU -13.3% · Risk 100 · 11m lag · 7 failures

-13.3%▸

CPU 1c-0.9%

CPU Mc-13.3%

RAM+0.0%

Worst-13.3%

5D7Kr1VPGCW8jr...vofMRhuzPQCOREMulti CPU -21.8% · Risk 100 · 4m lag · 12 failures

-21.8%▸

CPU 1c-0.4%

CPU Mc-21.8%

RAM0.0%

Worst-21.8%

5DudAJr7Y9KFve...DnM9tCDiwXCOREMulti CPU -12.4% · Risk 100 · 6m lag · 7 failures

-12.4%▸

CPU 1c-3.1%

CPU Mc-12.4%

RAM0.0%

Worst-12.4%

5F2AJ91NXYstwn...YjvWbqPESCCOREMulti CPU -10.6% · Risk 100 · 28m lag · 1 failureMotorola G Play 2024

-10.6%▸

CPU 1c+0.4%

CPU Mc-10.6%

RAM0.0%

Worst-10.6%

5FTohYhW9JbgfQ...Kek15iAk18COREMulti CPU -43.4% · Single CPU -5.8% · Risk 100 · 8m lag · 4 failures

-43.4%▸

CPU 1c-5.8%

CPU Mc-43.4%

RAM+0.0%

Worst-43.4%

5Cfedb7KkkHbNm...g9nt8XyX5XCORE3m lag · 9 failures

-4.0%▸

CPU 1c-0.3%

CPU Mc-4.0%

RAM+0.0%

Worst-4.0%

5CFwcwT8njCpfp...942nXW986fCORE4m lag · 6 failures

-1.7%▸

CPU 1c-1.7%

CPU Mc+4.5%

RAM+0.0%

Worst-1.7%

5CgLrFGx8K6h6V...eBiDWah9DDCORE7m lag · 7 failures

-2.8%▸

CPU 1c-0.3%

CPU Mc-2.8%

RAM0.0%

Worst-2.8%

5DgKHxQQzurxR5...F588ws4E8dCORE8m lag · 5 failures

-2.6%▸

CPU 1c-2.6%

CPU Mc-0.7%

RAM0.0%

Worst-2.6%

5Dt99waJXeGH6P...KQ3JeMSPstCORE24m lag · 8 failures

-2.8%▸

CPU 1c-0.3%

CPU Mc-2.8%

RAM0.0%

Worst-2.8%

5DTU9aZBN6uDaP...5obZME8yN1CORE7m lag · 5 failures

-1.2%▸

CPU 1c-1.2%

CPU Mc+3.5%

RAM0.0%

Worst-1.2%

5E7Zg8B7mfibru...6xazwt8Gz4CORE7m lag · 7 failures

-4.7%▸

CPU 1c-4.7%

CPU Mc-4.6%

RAM0.0%

Worst-4.7%

5ETL19rZnbdhSn...CSJSd9wfq2CORE4m lag · 5 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+0.9%

RAM+0.0%

Worst-0.2%

5EvBEAPYzKvdZS...fG2s94ZZZTCORE5m lag · 8 failures

-3.9%▸

CPU 1c+0.5%

CPU Mc-3.9%

RAM+0.0%

Worst-3.9%

5ExVUBVBrhwfkp...Vh7qaUVq2CCORE23m lag · 7 failures

-4.8%▸

CPU 1c-4.8%

CPU Mc+8.8%

RAM0.0%

Worst-4.8%

5FGx7XSbKtD9F1...5knqw9MzqiCORE20m lag · 6 failures

-0.2%▸

CPU 1c-0.2%

CPU Mc+2.9%

RAM+0.0%

Worst-0.2%

5FXRCFeLa4gidD...cKsEkyqHVTCORE26m lag · 5 failures

-0.0%▸

CPU 1c+0.3%

CPU Mc+6.2%

RAM-0.0%

Worst-0.0%

5Gf2NwQp7cvDGu...bbKwZDVrscCORE26m lag · 5 failures

-2.6%▸

CPU 1c-2.6%

CPU Mc-0.1%

RAM0.0%

Worst-2.6%