When should I upgrade my plan?

Applies to: All plans (Self-Managed and Managed).

Upgrade your plan when you keep hitting your account's limits and tuning no longer fixes it — for example, you see 508 "Resource Limit Reached" errors regularly, your CPU or memory sits near its cap, or you have run out of websites, storage or databases. A bigger plan raises your CloudLinux resource limits and your cPanel feature limits in one step. This article lists the signals to watch and points you to the upgrade itself.

First try the quick wins below. If they do not give you enough headroom, it is time to move up.

Signals you have outgrown your plan

Signal	What you are seeing	What it usually means
Frequent 508 errors	Visitors see 508 "Resource Limit Reached" at busy times	Your account is hitting its CloudLinux CPU, memory or process limits
Sustained high usage	The usage graphs sit at or near the cap most of the day, not just in short spikes	The plan is too small for your steady traffic
Storage nearly full	Disk usage is close to your plan's SSD allowance, or you cannot upload files	You need more storage (or a clean-up)
Out of websites	You cannot add another addon domain	You have used your plan's website allowance
Out of databases or FTP accounts	cPanel refuses to create a new MySQL database or FTP login	You have hit the per-plan count

A one-off 508 during a traffic spike is normal and clears on its own when usage drops — it is not a full outage. Treat repeated 508s, or limits you hit every day, as the real signal.

Where to check your usage first

CPU, memory, processes and I/O: open cPanel from your service (client area -> Services -> My Services -> Log in to cPanel) and view the resource-usage / CloudLinux statistics tools. If a metric is "faulted" often, that limit is your bottleneck.
Disk usage: the same cPanel dashboard shows disk space used against your plan allowance. There is no file-count (inode) limit to watch.
Website, database and FTP counts: these are set by your plan; see the per-plan limits in the articles below.

Try these before upgrading

A bigger plan is the right fix when you have genuinely outgrown your current one — but cheap tuning often buys real headroom first:

Turn on caching. On WordPress, the LiteSpeed Cache (LSCache) plugin pairs with our LiteSpeed server cache and cuts CPU dramatically.
Use a modern PHP version. Set a current PHP (for example 8.x) per domain in cPanel -> MultiPHP Manager — newer versions are usually faster.
Trim plugins and optimise queries. Fewer, leaner plugins and a tuned database reduce CPU, memory and 508s.
Free up space. Delete old backups, logs and unused files to recover disk space.

If you have done these and still hit the wall, upgrade.

Add-ons vs a full upgrade

If only one resource is short, a configurable add-on may be cheaper than the next plan:

Extra disk (+25 GB, EUR 4/mo) if only storage is tight.
Extra databases (+5, EUR 1.50/mo) if you only need more MySQL databases.

But if CPU, memory or 508 errors are the problem, those are set by your plan tier — add-ons do not raise them, so move to a higher plan.

Should I move from Self-Managed to Managed?

Consider Managed (not just a bigger Self-Managed plan) if your site is now business-critical. Managed adds 24/7 monitoring and on-call, managed updates and patching, an uptime SLA with service credits, and daily 30-day off-site backups. Self-Managed is self-serve with no uptime SLA. See the comparison linked below.

How to upgrade

You change plans in the client area — see How to upgrade or downgrade your plan for the exact steps. Your data, domains and settings stay in place; you keep the same cPanel account.

Result: Once the upgrade is active, your CloudLinux limits and cPanel feature limits rise to the new plan's level, and the 508 errors caused by hitting the old caps should stop.