"Overselling" gets thrown around as a dirty word in hosting, but every reseller does it to some degree — the question is whether you do it intentionally with safe ratios, or accidentally with disastrous ones. This article explains what overselling actually is, how to do it without burning your customers, and how to recognize when you've done it wrong.
What overselling actually means
Overselling is allocating more aggregate resources to packages than you have physical resources to deliver. If your reseller plan has 50 GB of disk and you sell ten 10 GB packages, you've "oversold" by 100%. This is fine because no one uses their full quota — the average shared hosting customer uses 5-15% of allocated disk.
The dangerous version is when overselling combines with no per-account resource caps. One customer maxes out CPU and memory, and every other customer on the server sees sluggish responses or 500 errors. Your support inbox lights up.
Real-world utilization ratios
Industry averages across thousands of shared hosting accounts:
- Disk: customers use 5-15% of their allocated quota
- Bandwidth: 2-8% of allocated transfer
- CPU: 0.5-3% time-averaged, but with bursts to 100% during cron jobs and traffic spikes
- RAM: 50-500 MB resident at any time, with PHP-FPM peaks during traffic bursts
This is why hosts can offer "unlimited" disk and bandwidth without going broke — the median user is several orders of magnitude under the headline number.
Safe overselling ratios
The hosts that get overselling right tend to follow these ratios:
- Disk: 5-10x oversell (safe; people don't fill quotas)
- Bandwidth: 10-20x oversell (very safe; almost no one uses theirs)
- CPU: 4x oversell maximum, with hard per-account caps. This is the dangerous one.
- RAM: 4x oversell maximum, with hard per-account caps
- I/O: 4-6x oversell
Translation: if your reseller plan has 4 CPU cores worth of allocation, don't set up packages totaling more than 16 cores' worth of CPU caps.
The thing that actually saves you: per-account caps
Overselling is fine when each account has hard limits that protect everyone else. On ipxcore reseller infrastructure, those limits are enforced by CloudLinux LVE:
- CPU cap: the absolute most CPU one account can use, regardless of demand. 100% = one full core.
- Physical memory (PMEM) limit: hard cap on resident memory. Going over kills processes.
- I/O limit: KB/s of disk read/write. Prevents one account from saturating disk.
- Inode limit: total file count. Prevents runaway file creation.
- Number of processes (NPROC): caps total simultaneous PHP/cron/etc. processes per account.
- Entry processes (EP): caps simultaneous web requests being processed. The single most important setting for shared hosting stability.
When a limit is hit, that account sees a temporary 508 error or queue. Other accounts on the server are unaffected. This is the entire point.
Recommended starting LVE values
For a typical reseller serving small business and WordPress customers:
| Setting | Starter | Standard | Pro |
| CPU cap | 50% | 100% | 200% |
| PMEM | 1024 MB | 2048 MB | 4096 MB |
| I/O (KB/s) | 1024 | 4096 | 8192 |
| Inodes | 250k | 500k | 1M |
| NPROC | 30 | 60 | 100 |
| EP | 10 | 20 | 40 |
Adjust based on your actual customer profile. WooCommerce stores need more memory and EP than blogs.
Monitoring: catch problems before customers do
The CloudLinux LVE Manager shows real-time and historical resource usage per account. Check it weekly. Look for:
- Accounts hitting limits frequently: they need a bigger tier, or are misbehaving (cryptominer, infinite loop, etc.)
- Accounts using nothing: healthy — you can safely sell more
- Trending upward: growth; plan capacity
The LVE faults log tells you exactly when accounts hit limits. If a particular account is constantly faulting, contact them — they'll either upsell to a bigger tier (revenue!) or you'll discover their site is hacked and burning CPU mining crypto (also valuable!).
Warning signs you've oversold
- Customers complaining about general slowness, not specific errors
- Multiple unrelated customers reporting issues at the same times of day (peak traffic)
- Server load average consistently above core count
- cPanel itself feeling slow when you log in
If you see these signs, your options are: enable stricter LVE limits, upgrade your reseller plan, or migrate the heaviest accounts to a separate server.
The honest answer
Overselling 4-8x with proper LVE caps is industry standard and safe. Overselling without LVE caps is unsafe at any ratio. If your ipxcore reseller plan didn't come with LVE configuration enabled, open a ticket — we'll set sensible defaults for free.
