---
title: "Comment by Zahra Hassan on \"Is Your Cloud Server Slow Because of CPU Steal? How to Check\" | Hashnode"
description: "Nice guide. The point that steal only shows up under load is the one people miss, because a 3 a.m. check on an idle box tells you nothing. One addition for the"
url: "https://hashnode.com/posts/cpu-steal-time/6ae05b6b7651a675141b2424/comment/6afc18e24203073b5bfad514"
---

[Discussion](https://hashnode.com/posts/cpu-steal-time/6ae05b6b7651a675141b2424)

Comment [Is Your Cloud Server Slow Because of CPU Steal? How to Check](https://hashnode.com/posts/cpu-steal-time/6ae05b6b7651a675141b2424)

[Zahra Hassan](https://hashnode.com/@zahrahassan)

[1d ago](https://hashnode.com/posts/cpu-steal-time/6ae05b6b7651a675141b2424/comment/6afc18e24203073b5bfad514)

Nice guide. The point that steal only shows up under load is the one people miss, because a 3 a.m. check on an idle box tells you nothing.

One addition for the burstable plan case: on AWS T-series instances, steal often spikes when CPU credits run out. In that case CloudWatch’s CPUCreditBalance metric will confirm it faster than any amount of server-side digging. It’s worth looking at before you blame noisy neighbors.

If steal keeps coming back, moving to dedicated or premium CPU plans (most providers offer them, including DigitalOcean, Vultr and AWS) usually fixes it. Managed hosts such as Cloudways let you pick the underlying provider and size, so you can switch without rebuilding your setup. Just compare the CPU terms on any plan before you move.
