CPU, memory, process or entry-process limits protect shared hosting stability.
Applies to: CloudLinux performance and resource limits
CloudLinux limits protect the shared platform and are burstable ceilings rather than dedicated resources. A limit event is a symptom to investigate; repeated events usually require application optimisation, traffic control or a larger plan.
Before you start
- Open the affected hosting service and note the exact time, URL and operation that was slow or failed.
- Have recent CloudLinux usage, application logs and any monitoring alert available for the same time window.
Work through these checks
- Review resource usage and fault timestamps.
- Check for runaway cron jobs, bots, slow plugins and database queries.
- Cache the site and optimise images.
- Upgrade only after the cause and normal workload are understood.
Confirm the result
- The same operation completes without another limit event during a comparable test.
- CloudLinux graphs and application logs show which change improved the workload rather than merely hiding the symptom.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The problem started immediately after a change. | A deployment, plugin, permission, PHP or configuration change introduced the fault. | Roll back only the last known change, clear caches and retest before making a second change. |
| The fault is intermittent. | Resource limits, traffic spikes, remote dependencies or scheduled work may be involved. | Record exact timestamps and compare them with CloudLinux usage, application logs and the Service Status page. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The affected domain and SiteWorx account
- The exact error text and time
- The last change made
- Relevant log lines with passwords and personal data removed
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Understand a CloudLinux CPU limit event
- Understand CloudLinux entry-process and process limits
- View website and error logs
- Understand CloudLinux IO and IOPS limits
- Understand a CloudLinux memory limit event
Last reviewed: 2026-07-18.
