Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Troubleshooting

Server CPU high: how to identify the workload

Published August 2026 · 8 min read

A high CPU graph tells you the server is busy, not why. The next step is to identify which processes are using CPU and then connect that activity to requests, jobs, queries, deployments, or unexpected software.

Check whether the spike is brief or sustained

Short bursts during backups, package updates, builds, or traffic peaks can be normal. Sustained saturation that increases request latency or queue depth is more likely to need investigation or capacity changes.

Identify the process, then the trigger

A web worker at 100% CPU is only an intermediate clue. Match it to access logs, slow requests, plugin activity, a specific API endpoint, database query, scheduled task, or application trace.

Include database and I/O wait in the picture

A server can feel CPU-bound when tasks are actually waiting on storage or database locks. Review load, I/O wait, query activity, and process state instead of relying on one percentage.

Rule out abuse and compromised workloads

Unexpected miners, brute-force traffic, vulnerable applications, or compromised accounts can create unexplained compute. If the workload does not match legitimate activity, preserve evidence and investigate security before simply adding CPU.

Next step

High server CPU can come from traffic, PHP workers, databases, compression, backups, malware, cron jobs, builds, or runaway processes. Find the process and trigger before scaling.

Read server diagnostics guides

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

cPanel error logs: where to look when a site breaks

cPanel exposes recent website errors, while server and application logs may contain deeper detail. Learn which log to check for PHP, Apache, cPanel, mail, and system failures.

Read the guide

Database connection failed: how to check the whole path

A database connection failure can involve DNS, host, port, firewall, service state, TLS, credentials, privileges, connection limits, or application configuration.

Read the guide

More troubleshooting guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move