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

Manager #5053 · compute baseline

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

47.0% healthy·30d↓16.4pp

LiveUpdated just now·use cached

83 devices

37Healthy

6Watch

40Investigate

0Low confidence

41Regressions

8Improving

2Stale heartbeat

40Failures

5.4ACU/day at risk

Non-Green 46 Investigate 40 Watch 6 Healthy 37 Improving 8▥ Down in Compare ▥ Stale in Compare ▥ CPU variance in Compare

▥ Investigate in Compare (40) ▾

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

Model	Devices	Healthy	Watch	Investigate	% Healthy	Improving
Untagged	42	0	4	38	0.0%	0
Samsung Galaxy S10+	1	0	0	1	0.0%	0
Samsung Galaxy S10

ModelBuildSortShowing 46 of 46

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

—

5EZoMBZthFg2Pv...1MAA31Dn2DCORE

down · 3d lag · 1 failure

Google Pixel 6a

0.0%

+0.0%

0.0%

▸

—

5DrkuCPx9yuXJ1...14VagtKvkPiOS

down · 10h lag · 3 failures

—

+2.5%

+4.0%

+0.0%

▸

—

5CpzUup5Zk7Mgs...5exRrRMxGnCOREFlagged 2h

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

—

-0.4%

-9.6%

0.0%

-9.6%

▸

—

5CyZFByWk8C4YG...oa4mVLNZiWCOREFlagged 27h+

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

—

-3.1%

-8.5%

+0.0%

-8.5%

▸

—

5D1RKUfpRrfctz...kinvSbzJNWCOREFlagged 27h+

Multi CPU -5.7% · Risk 77 · 19m lag · 2 failures

—

-0.2%

-5.7%

+0.0%

-5.7%

▸

—

5DGWRkxHPnj2GQ...5s2cFpNYS3COREFlagged 27h+

Multi CPU -5.0% · Risk 77 · 21m lag · 2 failures

—

+2.4%

-5.0%

+0.0%

-5.0%

▸

—

5GTnQZiLK6Myfp...ZdvTrtWVTVCOREFlagged 13h

Single CPU -5.0% · Risk 77 · 21m lag · 1 failure

—

-5.0%

-2.0%

+0.0%

-5.0%

▸

—

5Gvk7zeBLB1K4i...rWUTvigzY9COREFlagged 13h

Multi CPU -8.1% · Risk 77 · 17m lag · 1 failure

—

-0.8%

-8.1%

-0.0%

-8.1%

▸

—

5H2qy96VDAHbWy...VhY5CYZouCCOREFlagged 27h+

Multi CPU -7.3% · Risk 77 · 22m lag · 2 failures

—

-1.2%

-7.3%

+0.0%

-7.3%

▸

—

5HDDCaDyUhnNqk...MAZYTHFeb9COREFlagged 13h

Single CPU -7.2% · Risk 87 · 20m lag · 3 failures

—

-7.2%

-4.5%

0.0%

-7.2%

▸

—

5EeHtMg13GKeXW...kYCAptMwPoCOREFlagged 27h+

Single CPU -19.9% · Risk 95 · 19m lag

—

-19.9%

+36.4%

+0.0%

-19.9%

▸

—

5CAeWwA4MWLFHx...57jHXqsFwxCOREFlagged 21h

Multi CPU -25.6% · Single CPU -11.0% · Risk 100 · 20m lag · 1 failure

Samsung Galaxy S10

-11.0%

-25.6%

0.0%

-25.6%

▸

—

5CaJMqpy3ufNWj...oxf4hnanFtCOREFlagged 24h

Single CPU -32.3% · Multi CPU -14.3% · Risk 100 · 18m lag · 1 failure

Samsung Galaxy S10+

-32.3%

-14.3%

+0.0%

-32.3%

▸

—

5CaTFKH8uYjFWq...o73Eac9STRCOREFlagged 17h

Multi CPU -46.4% · Single CPU -16.4% · Risk 100 · 21m lag · 1 failure

—

-16.4%

-46.4%

-0.0%

-46.4%

▸

—

5CF8yX9SHnjP1i...r6PXY5c6mFCOREFlagged 27h+

Multi CPU -11.7% · Risk 100 · 19m lag · 2 failures

—

-1.6%

-11.7%

+0.0%

-11.7%

▸

—

5Che3dmHqQM7ED...LFia2hKiaHLITEFlagged 27h+

Multi CPU -13.4% · Single CPU -9.1% · Risk 100 · 2m lag · 2 failures

—

-9.1%

-13.4%

-0.0%

-13.4%

▸

—

5CtytipaTbyUQo...rnKwNbSYf5COREFlagged 27h+

Single CPU -17.1% · Multi CPU -11.9% · Risk 100 · 2m lag · 3 failures

—

-17.1%

-11.9%

+0.0%

-17.1%

▸

—

5D3rSysUKTVVgM...1a9YM6YdY4COREFlagged 27h+

Multi CPU -13.2% · Risk 100 · 21m lag · 2 failures

—

+5.0%

-13.2%

0.0%

-13.2%

▸

—

5D6NtwYwfcPPCT...7GahdcMqRGCOREFlagged 27h+

Single CPU -42.2% · Multi CPU -20.5% · Risk 100 · 1m lag · 2 failures

—

-42.2%

-20.5%

+0.0%

-42.2%

▸

—

5DFKNDkMAzNQ6K...JwDVjBWU3uCOREFlagged 27h+

Single CPU -25.9% · Multi CPU -15.8% · Risk 100 · 17m lag · 2 failures

—

-25.9%

-15.8%

0.0%

-25.9%

▸

—

5DGuFF3Xb389pd...HRhM3BRBLfCOREFlagged 27h+

Single CPU -44.2% · Multi CPU -27.3% · Risk 100 · 21m lag · 1 failure

—

-44.2%

-27.3%

+0.0%

-44.2%

▸

—

5DQEeq8GsXNX2R...psinDtAffpCOREFlagged 27h+

Single CPU -37.3% · Multi CPU -21.8% · Risk 100 · 19m lag · 3 failures

—

-37.3%

-21.8%

+0.0%

-37.3%

▸

—

5Dqus3AWQXb1zP...CEJKRPybGECOREFlagged 27h+

Multi CPU -55.1% · Single CPU -45.1% · Risk 100 · 18m lag · 4 failures

—

-45.1%

-55.1%

0.0%

-55.1%

▸

—

5DrrbUAgx5odfT...ZqorFU95DDCOREFlagged 27h+

Multi CPU -50.9% · Single CPU -34.7% · Risk 100 · 2m lag · 3 failures

—

-34.7%

-50.9%

+0.0%

-50.9%

▸

—

5DRUhykg1cHC2L...FLrcK8tp7ACOREFlagged 27h+

Single CPU -24.1% · Risk 100 · 1m lag · 4 failures

—

-24.1%

+21.0%

+0.0%

-24.1%

▸

—

5DvTeBQHPMUhdJ...HxvUSeHDWBCOREFlagged 9h

Multi CPU -14.3% · Risk 100 · 22m lag · 2 failures

—

+0.5%

-14.3%

-0.0%

-14.3%

▸

—

5EHJF9mhUY5kkv...8pnaZkNMwFCOREFlagged 27h+

Multi CPU -12.6% · Risk 100 · 1m lag · 3 failures

—

-0.1%

-12.6%

0.0%

-12.6%

▸

—

5Ej3httasxs6in...br86HxXXNjCOREFlagged 27h+

Single CPU -44.2% · Multi CPU -36.3% · Risk 100 · 19m lag

—

-44.2%

-36.3%

0.0%

-44.2%

▸

—

5EM8WjSYpC2oZn...gHbegZLWMRCOREFlagged 27h+

Single CPU -34.5% · Multi CPU -22.2% · Risk 100 · 12m lag

—

-34.5%

-22.2%

+0.0%

-34.5%

▸

—

5EmcaLRi9vxFwJ...mxNxgnjAbWCOREFlagged 27h+

Multi CPU -33.9% · Single CPU -10.3% · Risk 100 · 21m lag · 2 failures

—

-10.3%

-33.9%

0.0%

-33.9%

▸

—

5EWTFuoihzSevK...bK2jutcQFJCOREFlagged 27h+

Multi CPU -52.8% · Single CPU -36.5% · Risk 100 · 29m lag

—

-36.5%

-52.8%

+0.0%

-52.8%

▸

—

5FAxm8YMiN43hM...jFpjaUsG7aCOREFlagged 22h

Single CPU -20.3% · Risk 100 · 19m lag

—

-20.3%

-3.6%

+0.0%

-20.3%

▸

—

5FFVnA3nFXYegZ...4ksgMfKCRACOREFlagged 27h+

Multi CPU -43.4% · Risk 100 · 1m lag · 1 failure

—

+29.9%

-43.4%

+0.0%

-43.4%

▸

—

5FkLhPoJSfdrm3...nPaRhBjBkSCOREFlagged 27h+

Single CPU -15.6% · Multi CPU -7.9% · Risk 100 · 21m lag · 1 failure

—

-15.6%

-7.9%

0.0%

-15.6%

▸

—

5FVMWZHs5Ttuce...UETiRrLmWmCOREFlagged 2h

Multi CPU -20.7% · Risk 100 · 12m lag

—

+13.9%

-20.7%

+0.0%

-20.7%

▸

—

5FvTSGVrNXbg9H...GHHq28BexKCOREFlagged 27h+

Multi CPU -48.6% · Risk 100 · 1m lag · 2 failures

—

+8.3%

-48.6%

-0.0%

-48.6%

▸

—

5Fy9pTnzsKKpBr...5EqwopPQjjCOREFlagged 19h

Multi CPU -12.1% · Single CPU -5.5% · Risk 100 · 17m lag · 1 failure

—

-5.5%

-12.1%

-0.0%

-12.1%

▸

—

5GWSdDHHBRmhTa...wfCg3ExTa7COREFlagged 2h

Multi CPU -20.1% · Risk 100 · 4m lag · 3 failures

—

+6.6%

-20.1%

+0.0%

-20.1%

▸

—

5GxUfYym4WzEFU...zEMVHKMqNwCOREFlagged 27h+

Multi CPU -30.2% · Risk 100 · 2m lag · 1 failure

—

-1.9%

-30.2%

-0.0%

-30.2%

▸

—

5GYdvWKKiVzMmw...jPEAqcYzbECOREFlagged 27h+

Single CPU -34.8% · Multi CPU -16.7% · Risk 100 · 1m lag

—

-34.8%

-16.7%

+0.0%

-34.8%

▸

—

5HC84jDhuwhNgH...Ve2EWxoQ1NCOREFlagged 27h+

Single CPU -30.9% · Multi CPU -11.3% · Risk 100 · 20m lag

—

-30.9%

-11.3%

0.0%

-30.9%

▸

—

5HLaA68WAywFos...UAMmYiCNXjCOREFlagged 27h+

Single CPU -32.9% · Multi CPU -29.6% · Risk 100 · 1m lag

—

-32.9%

-29.6%

0.0%

-32.9%

▸

—

5DqxbU88GVAqFU...Dunx8xUykMCORE

20m lag · 11 failures

—

+0.7%

-0.8%

+0.0%

-0.8%

▸

—

5Gyjfa7fgtqok5...B4pgrDrWGCCOREFlagged 5h

Multi CPU -6.0% · 18m lag

Google Pixel 6

-1.5%

-6.0%

+0.0%

-6.0%

▸

—

5DkMY8gbBJMN15...qRPyi9wyrsCOREFlagged 57m

Multi CPU -12.9% · 13m lag

—

+6.0%

-12.9%

+0.0%

-12.9%

▸

—

5Epo9rkaW9rLBf...iTAG6AfTRmCOREFlagged 57m

Multi CPU -12.2% · 19m lag

—

-0.0%

-12.2%

+0.0%

-12.2%

▸

5EZoMBZthFg2Pv...1MAA31Dn2DCOREdown · 3d lag · 1 failureGoogle Pixel 6a

0.0%▸

CPU 1c0.0%

CPU Mc0.0%

RAM+0.0%

Worst0.0%

5DrkuCPx9yuXJ1...14VagtKvkPiOSdown · 10h lag · 3 failures

+0.0%▸

CPU 1c+2.5%

CPU Mc+4.0%

RAM+0.0%

Worst+0.0%

5CpzUup5Zk7Mgs...5exRrRMxGnCOREMulti CPU -9.6% · Risk 77 · 19m lag · 1 failure

-9.6%▸

CPU 1c-0.4%

CPU Mc-9.6%

RAM0.0%

Worst-9.6%

5CyZFByWk8C4YG...oa4mVLNZiWCOREMulti CPU -8.5% · Risk 77 · 30m lag · 1 failure

-8.5%▸

CPU 1c-3.1%

CPU Mc-8.5%

RAM+0.0%

Worst-8.5%

5D1RKUfpRrfctz...kinvSbzJNWCOREMulti CPU -5.7% · Risk 77 · 19m lag · 2 failures

-5.7%▸

CPU 1c-0.2%

CPU Mc-5.7%

RAM+0.0%

Worst-5.7%

5DGWRkxHPnj2GQ...5s2cFpNYS3COREMulti CPU -5.0% · Risk 77 · 21m lag · 2 failures

-5.0%▸

CPU 1c+2.4%

CPU Mc-5.0%

RAM+0.0%

Worst-5.0%

5GTnQZiLK6Myfp...ZdvTrtWVTVCORESingle CPU -5.0% · Risk 77 · 21m lag · 1 failure

-5.0%▸

CPU 1c-5.0%

CPU Mc-2.0%

RAM+0.0%

Worst-5.0%

5Gvk7zeBLB1K4i...rWUTvigzY9COREMulti CPU -8.1% · Risk 77 · 17m lag · 1 failure

-8.1%▸

CPU 1c-0.8%

CPU Mc-8.1%

RAM-0.0%

Worst-8.1%

5H2qy96VDAHbWy...VhY5CYZouCCOREMulti CPU -7.3% · Risk 77 · 22m lag · 2 failures

-7.3%▸

CPU 1c-1.2%

CPU Mc-7.3%

RAM+0.0%

Worst-7.3%

5HDDCaDyUhnNqk...MAZYTHFeb9CORESingle CPU -7.2% · Risk 87 · 20m lag · 3 failures

-7.2%▸

CPU 1c-7.2%

CPU Mc-4.5%

RAM0.0%

Worst-7.2%

5EeHtMg13GKeXW...kYCAptMwPoCORESingle CPU -19.9% · Risk 95 · 19m lag

-19.9%▸

CPU 1c-19.9%

CPU Mc+36.4%

RAM+0.0%

Worst-19.9%

5CAeWwA4MWLFHx...57jHXqsFwxCOREMulti CPU -25.6% · Single CPU -11.0% · Risk 100 · 20m lag · 1 failureSamsung Galaxy S10

-25.6%▸

CPU 1c-11.0%

CPU Mc-25.6%

RAM0.0%

Worst-25.6%

5CaJMqpy3ufNWj...oxf4hnanFtCORESingle CPU -32.3% · Multi CPU -14.3% · Risk 100 · 18m lag · 1 failureSamsung Galaxy S10+

-32.3%▸

CPU 1c-32.3%

CPU Mc-14.3%

RAM+0.0%

Worst-32.3%

5CaTFKH8uYjFWq...o73Eac9STRCOREMulti CPU -46.4% · Single CPU -16.4% · Risk 100 · 21m lag · 1 failure

-46.4%▸

CPU 1c-16.4%

CPU Mc-46.4%

RAM-0.0%

Worst-46.4%

5CF8yX9SHnjP1i...r6PXY5c6mFCOREMulti CPU -11.7% · Risk 100 · 19m lag · 2 failures

-11.7%▸

CPU 1c-1.6%

CPU Mc-11.7%

RAM+0.0%

Worst-11.7%

5Che3dmHqQM7ED...LFia2hKiaHLITEMulti CPU -13.4% · Single CPU -9.1% · Risk 100 · 2m lag · 2 failures

-13.4%▸

CPU 1c-9.1%

CPU Mc-13.4%

RAM-0.0%

Worst-13.4%

5CtytipaTbyUQo...rnKwNbSYf5CORESingle CPU -17.1% · Multi CPU -11.9% · Risk 100 · 2m lag · 3 failures

-17.1%▸

CPU 1c-17.1%

CPU Mc-11.9%

RAM+0.0%

Worst-17.1%

5D3rSysUKTVVgM...1a9YM6YdY4COREMulti CPU -13.2% · Risk 100 · 21m lag · 2 failures

-13.2%▸

CPU 1c+5.0%

CPU Mc-13.2%

RAM0.0%

Worst-13.2%

5D6NtwYwfcPPCT...7GahdcMqRGCORESingle CPU -42.2% · Multi CPU -20.5% · Risk 100 · 1m lag · 2 failures

-42.2%▸

CPU 1c-42.2%

CPU Mc-20.5%

RAM+0.0%

Worst-42.2%

5DFKNDkMAzNQ6K...JwDVjBWU3uCORESingle CPU -25.9% · Multi CPU -15.8% · Risk 100 · 17m lag · 2 failures

-25.9%▸

CPU 1c-25.9%

CPU Mc-15.8%

RAM0.0%

Worst-25.9%

5DGuFF3Xb389pd...HRhM3BRBLfCORESingle CPU -44.2% · Multi CPU -27.3% · Risk 100 · 21m lag · 1 failure

-44.2%▸

CPU 1c-44.2%

CPU Mc-27.3%

RAM+0.0%

Worst-44.2%

5DQEeq8GsXNX2R...psinDtAffpCORESingle CPU -37.3% · Multi CPU -21.8% · Risk 100 · 19m lag · 3 failures

-37.3%▸

CPU 1c-37.3%

CPU Mc-21.8%

RAM+0.0%

Worst-37.3%

5Dqus3AWQXb1zP...CEJKRPybGECOREMulti CPU -55.1% · Single CPU -45.1% · Risk 100 · 18m lag · 4 failures

-55.1%▸

CPU 1c-45.1%

CPU Mc-55.1%

RAM0.0%

Worst-55.1%

5DrrbUAgx5odfT...ZqorFU95DDCOREMulti CPU -50.9% · Single CPU -34.7% · Risk 100 · 2m lag · 3 failures

-50.9%▸

CPU 1c-34.7%

CPU Mc-50.9%

RAM+0.0%

Worst-50.9%

5DRUhykg1cHC2L...FLrcK8tp7ACORESingle CPU -24.1% · Risk 100 · 1m lag · 4 failures

-24.1%▸

CPU 1c-24.1%

CPU Mc+21.0%

RAM+0.0%

Worst-24.1%

5DvTeBQHPMUhdJ...HxvUSeHDWBCOREMulti CPU -14.3% · Risk 100 · 22m lag · 2 failures

-14.3%▸

CPU 1c+0.5%

CPU Mc-14.3%

RAM-0.0%

Worst-14.3%

5EHJF9mhUY5kkv...8pnaZkNMwFCOREMulti CPU -12.6% · Risk 100 · 1m lag · 3 failures

-12.6%▸

CPU 1c-0.1%

CPU Mc-12.6%

RAM0.0%

Worst-12.6%

5Ej3httasxs6in...br86HxXXNjCORESingle CPU -44.2% · Multi CPU -36.3% · Risk 100 · 19m lag

-44.2%▸

CPU 1c-44.2%

CPU Mc-36.3%

RAM0.0%

Worst-44.2%

5EM8WjSYpC2oZn...gHbegZLWMRCORESingle CPU -34.5% · Multi CPU -22.2% · Risk 100 · 12m lag

-34.5%▸

CPU 1c-34.5%

CPU Mc-22.2%

RAM+0.0%

Worst-34.5%

5EmcaLRi9vxFwJ...mxNxgnjAbWCOREMulti CPU -33.9% · Single CPU -10.3% · Risk 100 · 21m lag · 2 failures

-33.9%▸

CPU 1c-10.3%

CPU Mc-33.9%

RAM0.0%

Worst-33.9%

5EWTFuoihzSevK...bK2jutcQFJCOREMulti CPU -52.8% · Single CPU -36.5% · Risk 100 · 29m lag

-52.8%▸

CPU 1c-36.5%

CPU Mc-52.8%

RAM+0.0%

Worst-52.8%

5FAxm8YMiN43hM...jFpjaUsG7aCORESingle CPU -20.3% · Risk 100 · 19m lag

-20.3%▸

CPU 1c-20.3%

CPU Mc-3.6%

RAM+0.0%

Worst-20.3%

5FFVnA3nFXYegZ...4ksgMfKCRACOREMulti CPU -43.4% · Risk 100 · 1m lag · 1 failure

-43.4%▸

CPU 1c+29.9%

CPU Mc-43.4%

RAM+0.0%

Worst-43.4%

5FkLhPoJSfdrm3...nPaRhBjBkSCORESingle CPU -15.6% · Multi CPU -7.9% · Risk 100 · 21m lag · 1 failure

-15.6%▸

CPU 1c-15.6%

CPU Mc-7.9%

RAM0.0%

Worst-15.6%

5FVMWZHs5Ttuce...UETiRrLmWmCOREMulti CPU -20.7% · Risk 100 · 12m lag

-20.7%▸

CPU 1c+13.9%

CPU Mc-20.7%

RAM+0.0%

Worst-20.7%

5FvTSGVrNXbg9H...GHHq28BexKCOREMulti CPU -48.6% · Risk 100 · 1m lag · 2 failures

-48.6%▸

CPU 1c+8.3%

CPU Mc-48.6%

RAM-0.0%

Worst-48.6%

5Fy9pTnzsKKpBr...5EqwopPQjjCOREMulti CPU -12.1% · Single CPU -5.5% · Risk 100 · 17m lag · 1 failure

-12.1%▸

CPU 1c-5.5%

CPU Mc-12.1%

RAM-0.0%

Worst-12.1%

5GWSdDHHBRmhTa...wfCg3ExTa7COREMulti CPU -20.1% · Risk 100 · 4m lag · 3 failures

-20.1%▸

CPU 1c+6.6%

CPU Mc-20.1%

RAM+0.0%

Worst-20.1%

5GxUfYym4WzEFU...zEMVHKMqNwCOREMulti CPU -30.2% · Risk 100 · 2m lag · 1 failure

-30.2%▸

CPU 1c-1.9%

CPU Mc-30.2%

RAM-0.0%

Worst-30.2%

5GYdvWKKiVzMmw...jPEAqcYzbECORESingle CPU -34.8% · Multi CPU -16.7% · Risk 100 · 1m lag

-34.8%▸

CPU 1c-34.8%

CPU Mc-16.7%

RAM+0.0%

Worst-34.8%

5HC84jDhuwhNgH...Ve2EWxoQ1NCORESingle CPU -30.9% · Multi CPU -11.3% · Risk 100 · 20m lag

-30.9%▸

CPU 1c-30.9%

CPU Mc-11.3%

RAM0.0%

Worst-30.9%

5HLaA68WAywFos...UAMmYiCNXjCORESingle CPU -32.9% · Multi CPU -29.6% · Risk 100 · 1m lag

-32.9%▸

CPU 1c-32.9%

CPU Mc-29.6%

RAM0.0%

Worst-32.9%

5DqxbU88GVAqFU...Dunx8xUykMCORE20m lag · 11 failures

-0.8%▸

CPU 1c+0.7%

CPU Mc-0.8%

RAM+0.0%

Worst-0.8%

5Gyjfa7fgtqok5...B4pgrDrWGCCOREMulti CPU -6.0% · 18m lagGoogle Pixel 6

-6.0%▸

CPU 1c-1.5%

CPU Mc-6.0%

RAM+0.0%

Worst-6.0%

5DkMY8gbBJMN15...qRPyi9wyrsCOREMulti CPU -12.9% · 13m lag

-12.9%▸

CPU 1c+6.0%

CPU Mc-12.9%

RAM+0.0%

Worst-12.9%

5Epo9rkaW9rLBf...iTAG6AfTRmCOREMulti CPU -12.2% · 19m lag

-12.2%▸

CPU 1c-0.0%

CPU Mc-12.2%

RAM+0.0%

Worst-12.2%