Hostinger High CPU Steal

[GuruDev1736]

Error Message and Logs

root@coolify-server:# ps -eo pid,ppid,cmd,%cpu,%mem --sort=-%cpu | head PID PPID CMD %CPU %MEM 11775 5556 ps -eo pid,ppid,cmd,%cpu,%m 295 0.0 820 1 /usr/bin/containerd 69.0 0.4 11715 9606 /usr/local/bin/php artisan 46.6 0.2 11383 10430 /usr/local/bin/php artisan 39.1 0.3 11327 9606 /usr/local/bin/php artisan 38.8 0.3 11768 6363 runc --root /var/run/docker 38.0 0.0 11763 6349 runc --root /var/run/docker 36.2 0.0 11680 11675 docker container ls -aq 22.2 0.1 10430 9347 /usr/local/bin/php artisan 20.0 0.4 root@coolify-server:#

Steps to Reproduce

1. install it on the VPS
2. check for the cpu usage

Example Repository URL

No response

Coolify Version

v4.0.0-beta.460

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

No response

Additional Information

Server specs: 4 Cores, 16GB, 200GB

[coderabbitai[bot]]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• [Bug]: Coolify Container High CPU & Memory Usage #5676

Related Issues

• [Bug]: High CPU from Coolify Redis Container #5768
• [Bug]: Running 'htop' on Coolify terminal will cause a massive CPU leak #6125
• [Bug]: CPU usage spike every minute from php Laravel Horizon #5651

👤 Suggested Assignees

• SyahmiRafsan
• RealFascinated
• arxkdev
• kelvinthh

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[ShadowArcanist]

Is the hosting provider is Hostinger?

Also can you send output of running the command mpstat -P ALL 1

[GuruDev1736]

Yes hosting provider is hostinger

[GuruDev1736]

[GuruDev1736]

[Cinzya]

@GuruDev1736 that is a very high steal amount. That means your hosting provider is over-provisioning their servers, giving you less power then you actually paid for. You should get in touch with them to get this resolved.

[GuruDev1736]

@Cinzya i firstly get the sever coolify is working amazing but after 3,4 updates it causing me this problem i think this should be the priority to fix and should release in next version soon

[Cinzya]

This is not a uncommon issue with Hostinger btw. And not really specific to Coolify.

https://www.reddit.com/r/Hostinger/comments/1etkohv/hostinger_vps_cpu_is_always_high/

https://www.reddit.com/r/Hostinger/comments/1pzgbwk/vps_extremely_high_cpu_steal/

https://www.reddit.com/r/VPS/comments/1pzfio4/hostinger_vps_high_cpu_steal/

[andrecrjr]

I'm having the same problem in Hostinger! Identified since in the last 3 or 4 updates (since 12/25/25)

It was working fine in Hostinger before, then blow up...

[GuruDev1736]

@andrecrjr did you got any solution on this

[ShadowArcanist]

@Cinzya i firstly get the sever coolify is working amazing but after 3,4 updates it causing me this problem i think this should be the priority to fix and should release in next version soon

There is nothing to fix from our end here, your host server is running out of CPU so all the VMs running on the host server are fighting for CPU so you have to contact Hostinger about this

[ShadowArcanist]

I'm having the same problem in Hostinger! Identified since in the last 3 or 4 updates (since 12/25/25)

It was working fine in Hostinger before, then blow up...

can you send output of running the command mpstat -P ALL 1 ?

[ao-Barbosa]

@GuruDev1736
I have ran into a similar issue with Coolify + Hostinger recently.
The issue is that hostinger might have put in place a hard limitation for your VPS CPU usage.
If that is the case for you as well, the "solution" is to go into your hpanel and check for CPU limitations, getting them to disable if any are present.

From what i've gathered, during coolify's automatic updates an 'abnormally high' CPU spike happens, leading to Hostinger to throttling the VPS temporarily.

Note that this doesn't seem to be related to the VPS capacity at all. In fact it happened to both of mine (staging env in KVM 2 and prod env KVM 8). I have since escalated this issue with their support but still waiting on a satisfactory response.

[GuruDev1736]

@ao-Barbosa i will check for the cpu limitation

[knotsyncc23]

I am having the same issue with hostinger and Did a complete OS rebuild Ubuntu with coolify panel and gettign the 100% spike iwht full rebuild and complete erase and this processer /eZUYmXOE is on 89% and sound like some Cryptomining Malware. Unable to get rid of it and hostinger is of no help and they are saying its my issue if my VPS is gettign effected and sendign me articals for the server proctection but even fresh install having 100% utlisation.

[GuruDev1736]

1. See first of all reinstall the operating system just operating system no prebuild coolify should there
2. Add security to your vps , activate firewall , install failtoban , and docker security packages make sure your all vps is secure
3. Before installing the coolify from the official website remove limitations If any have from the hostinger then only install the coolify
4. After installing just add your private key , public key and all and your coolify will work again with more security
5. Enjoy 😉

[palashu]

I ran into something very similar recently and wanted to share in case it helps.

What looks like “high load / slow apps with moderate CPU usage” can absolutely be caused by CPU steal time at the hypervisor level, and this is not something Coolify (or Docker / Kubernetes / app tuning) can fix inside the VM.

In my case:

• Apps and server were properly optimized.
• Taken care of security with firewall rules, WAF, cloudflare.
• Containers were not CPU-bound.
• RAM, disk, and network were healthy.
• Load average was high, but no single process was pegging CPU.

However, checking from inside, the VM showed the real issue:

• user and system take low cpu %
• "top" consistently reported 50–90% CPU steal (st)
• "vmstat 1 10" confirmed sustained steal across samples
• This persisted across different times of day, including low-traffic hours

That means the VM was ready to run but denied CPU by the host, due to node-level contention or oversubscription on same physical server. No amount of app tuning, container limits, or scaling inside Coolify or any other panel helped — because the problem was outside the guest.

Important observations from my case:

• The same workload ran fine on another provider with fewer resources.
• Upgrading their KVM plan with higher resources for my VPS temporarily fixed it (likely landed on a healthier node), then the issue returned aftera day or two.
• Migration to a less loaded node was the only real solution, so i emailed of high CPU steal to hostinger support.

So if anyone here is seeing:

• High load averages.
• Slow apps.
• Moderate in-guest CPU usage.
• Everything “looks fine” inside containers.

…it’s worth checking CPU steal before assuming your Coolify or Docker is the bottleneck.

For anyone debugging this, I strongly recommend checking from terminal:

top
vmstat 1 10
mpstat -P ALL 1 5

If %st is consistently above ~20–30%, you’re dealing with host-level CPU contention, not an app or orchestration issue.