Articles on: Performance and troubleshooting

What happens when a site reaches its CPU, memory, or storage limits

Each FlyingHost site runs in its own isolated container with the CPU, memory, and storage included in its plan. Short spikes are usually harmless, but sustained usage at a limit can affect the site.


CPU limit


When the site uses all available CPU, requests must wait for CPU time. The site normally stays online, but uncached pages, WordPress admin, cron jobs, imports, and other dynamic work may become slow or time out.


Common causes include traffic spikes, bots, slow plugins, heavy database queries, backups, imports, and frequent cron jobs.


Memory limit


When the site runs out of memory, the system may stop a memory-heavy process to keep the container within its limit. This can cause slow requests, temporary errors, or service restarts until memory becomes available again.


Repeated high memory usage often points to a plugin, large import, database workload, or too many simultaneous PHP requests.


Storage limit


When storage is full, the site cannot write new data. Uploads, plugin updates, cache files, logs, and database writes may fail. Some existing pages may still load, but WordPress can behave unpredictably until space is freed or the plan is upgraded.


Cockpit Resources page showing memory, CPU, PHP worker, and storage charts


Resource alerts by email


FlyingHost monitors production sites for:


  • High CPU usage
  • High memory usage
  • High storage usage
  • PHP capacity limits


When sustained usage triggers an alert, we email the members of your FlyingHost organization. The email identifies the affected site and links to its Resources page in Cockpit.


Staging sites do not send these resource-alert emails. An alert is a warning to investigate; it does not always mean that you need a larger plan.


Diagnose sustained resource usage


  1. Open the site in Cockpit and select Resources.
  2. Check the same time range as the alert.
  3. Compare CPU, memory, PHP workers, traffic, and logs.
  4. Look for traffic spikes, bots, cron jobs, imports, scans, or recent changes.
  5. Free unused storage or optimize the workload.
  6. Upgrade the plan if legitimate usage regularly reaches the limit.


Cockpit Traffic overview showing the site’s top paths and countries by requests


See FlyingHost plans and resource limits for the limits included with each plan. For PHP-specific capacity issues, see PHP workers explained.

Updated on: 14/11/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!