Hosting · Explainer
What Is an Entry Process Limit?
Short answer
An entry process limit caps how many PHP or CGI requests can run at the same moment inside your hosting account. CloudLinux sets a default of 20 entry processes for a typical shared account, and extra requests get a 508 Resource Limit Is Reached error. Cached pages skip PHP, so they do not use an entry process at all.
Key takeaways
- An entry process is one PHP or CGI request running right now, not a count of visitors.
- CloudLinux sets the default entry process limit at 20, with 40 for high-end accounts.
- When the limit fills up, extra visitors see a 508 Resource Limit Is Reached error.
- Cached pages and static files do not use an entry process, so caching frees slots fast.
- Slow plugins, long database queries and bot traffic fill entry processes first.
What is an entry process limit?
An entry process limit caps how many PHP or CGI requests can run inside your hosting account at the same moment.
CloudLinux, the system many shared hosts use, calls this limit EP and sets its default to 20 for a typical account. Each request that enters the account counts as one entry process until it finishes, then the count drops back. The limit is about concurrency, not total traffic.
The limit exists so one busy site cannot take every Apache connection on a shared server. CloudLinux built it after slow pages tied up all Apache slots and made the whole server look down.
What counts as an entry process?
A new HTTP request for a PHP or CGI script counts as one entry process when it enters your account.
CloudLinux counts each process as it enters the LVE, the isolated container around your account. It stops counting when the process exits.
Processes started inside the account, such as a PHP script that calls another program, do not add to the EP count. SSH sessions and cron jobs can also count as entry processes.
Your plan page lists the number, and you can read what each limit means in our guide to reading hosting CPU and RAM limits.
A normal WordPress page load uses one entry process for the PHP request that builds the HTML. Images, CSS files and JavaScript load after that as static files, so they do not open new entry processes.
What happens when you hit the limit?
Extra requests get a 508 Resource Limit Is Reached error until a slot frees up.
CloudLinux states that when the limit is reached, its Apache module cannot place the new request inside your account and returns error code 508. The rest of the server keeps working, and only your account shows the error.
Namecheap's overusage guide links the 508 code to entry processes, and links 500 or 503 codes to the total process limit instead.
The error is brief when traffic comes in a short burst, since each slot frees as soon as a request finishes. A page that takes 5 seconds to build holds its slot 25 times longer than a page that takes 0.2 seconds.
How is it different from CPU and memory limits?
The entry process limit counts simultaneous requests, while CPU and memory limits cap how much work those requests can do.
CloudLinux ships six limits together, and each one fails in its own way. CPU and disk I/O limits slow your site down when reached, since processes are put to sleep rather than stopped. Memory and total process limits kill scripts, which usually shows as a 500 or 503 error.
The table below shows the CloudLinux defaults for a typical shared account, as published in November 2026. Hosts can raise or lower any of these numbers per plan, so your plan may differ.
| Limit | Default | What it caps | What you see when it is hit |
|---|---|---|---|
| SPEED (CPU) | 100% of one core | Processor time | Pages load slowly |
| PMEM (memory) | 1 GB | RAM used by your processes | 500 or 503 errors |
| EP (entry processes) | 20 | Simultaneous PHP or CGI requests | 508 error |
| NPROC (processes) | 100 | All processes and threads | 500 or 503 errors |
| IO | 1,024 KB/s | Disk read and write speed | Slow disk work |
| IOPS | 1,024 per second | Disk read and write operations | Slow disk work |
CloudLinux also warns that NPROC should stay above EP plus 15, since the total process count includes the entry processes themselves. A limit of 20 entry processes with a total process cap of 100 leaves room for cron jobs, mail scripts and background tasks.
What are typical entry process limits by plan?
Entry process limits usually run from 15 on starter shared plans to 80 on high-end cloud plans.
Hostinger publishes entry process limits of 15, 20, 25 and 30 across its standard shared hosting tiers. Its cloud hosting tiers list 40, 50, 60 and 80 entry processes, with more memory and CPU at each step.
Namecheap's reseller guide shows a single resold account gets 20 entry processes. Its reseller tiers get 80, 160, 240 or 320 across all their client accounts.
CloudLinux recommends 20 entry processes for a typical hosting account and 40 for a high-end account. These are starting points, not rules, and a host can set any number it wants.
How do you check your entry process usage?
Open Resource Usage in cPanel and look at the entry process graph and fault history.
Namecheap's guide says to log in to cPanel and open the Resource Usage menu, which shows usage over time and which limits were reached. The cPanel sidebar also shows current entry process use next to CPU, memory and disk figures.
Check the history, not a single quiet moment, since a burst at noon will not show at midnight.
Look for red fault marks on the graph, which mark the moments the limit was hit. If faults cluster at the same time each day, look at what runs then: a backup plugin, a cron job, or a traffic spike.
How do you lower entry process use?
Speed up slow pages and cache them, so each request holds a slot for less time.
Page caching is the biggest win, since a cached page is served as a static file and never starts PHP. That means it uses no entry process at all, and a single slot can serve many visitors in a row.
A cache plugin or server-level caching both work, and you can compare the options in our guide to PHP workers and how they handle requests.
Next, find the slow pages. A plugin that calls an outside service on every load, a search form with no index, or a cart page that cannot be cached will hold slots open.
Turn off plugins one at a time and watch the Resource Usage graph after each change, leaving about an hour between checks.
Bots also fill slots, since they request many uncached pages in a row. A login page hit by brute-force attempts, an XML-RPC endpoint, or a feed URL crawled every minute can use several slots at once. Blocking the worst bot traffic and limiting login attempts frees slots for real visitors.
When should you upgrade your plan?
Upgrade when entry process faults keep happening after caching is on and slow pages are fixed.
A plan with 40 entry processes instead of 20 doubles the simultaneous requests you can handle, and it usually adds CPU and memory too. Hostinger states its limits are fixed per plan and cannot be raised one by one, so a higher tier is the only way to get more.
Before you pay more, check how many visitors shared hosting can handle at your current speed, since a faster site may not need a bigger plan at all. Our guide to how many visitors shared hosting can handle walks through that maths.
If faults persist on cached pages with normal traffic, the plan is too small and it is time to move up.
What mistakes should you avoid?
Do not treat the entry process limit as a visitor limit, and do not buy disk space to fix it.
The most common mistake is reading 20 entry processes as 20 visitors at once. One visitor loads a page in well under a second, so a limit of 20 can serve hundreds of visitors per minute when pages are fast and cached.
Another mistake is adding more plugins to fix a slow site, since each one adds PHP work and holds slots longer. Check the Resource Usage graph before and after every change, and keep only the plugins that earn their place.
Buying more disk space does nothing, since the limit counts requests, not files. If you still hit the limit every day, upgrade from shared hosting to a plan with more headroom rather than adding workarounds.
Frequently asked questions
Does an entry process limit cap how many visitors I can have?
No. It caps how many PHP requests run at the same instant, not how many people visit. A page that finishes in 0.2 seconds frees its slot fast, so a limit of 20 can serve hundreds of visitors per minute. Slow or uncached pages are what make the limit feel small.
Why do I get 508 errors when my traffic is low?
A 508 error means too many requests were running at once, even if total visits were low. One slow page, a backup job, or a bot crawling uncached URLs can fill all 20 slots. Check the Resource Usage graph in cPanel to see when the faults happened and what was running then.
Do cached pages use entry processes?
No. A cached page is served as a static file, so PHP never runs and no entry process opens. This is why caching is the fastest fix for 508 errors. Only uncached requests, such as cart pages, search results and admin pages, use entry processes.
Is the entry process limit per site or per account?
It is per hosting account. All sites, subdomains and addon domains in one cPanel account share the same limit. A busy second site can push the whole account over the edge, so check usage across every domain in the account before blaming one site.
Can I raise my entry process limit without changing hosts?
Usually only by moving to a higher plan with the same host. Most shared hosts fix limits per plan and do not sell entry processes on their own. Ask support what the next tier offers, and compare the CPU and memory figures too, since those often matter as much.
Sources
- Limits CloudLinux Documentation
- A Handy Guide to Resource Limits or What is LVE? Namecheap
- Ways of Resolving Resource Overusage Issues Namecheap
- Parameters and Limits of Hosting Plans in Hostinger Hostinger Support
- Anti-DDoS and Connection Throttling LiteSpeed Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
