"Unlimited bandwidth." "Unlimited storage." "Unlimited domains." If you've shopped for shared hosting in the last decade, you've seen these words. They're a marketing convention, not a technical reality. Bandwidth and storage are finite resources, and someone is paying for them — usually you, in ways the marketing doesn't disclose.

This isn't a hit piece on shared hosting. We sell shared hosting. It's a great fit for a lot of websites. But the cheap end of the market relies on overselling — packing more accounts onto a server than the server can comfortably support — and the techniques used to make this profitable affect your site's performance in ways most customers never notice.

Here are the seven most common patterns. If your current host does any of these, you're paying the cost in performance, even if your invoice is small.

1. CPU and memory throttling that spikes silently

Most cheap hosts use CloudLinux to set per-account CPU and memory limits — usually 100% of one core and 1 GB of RAM. Hit those limits and your account is throttled: PHP requests queue, response times spike, eventually requests start returning 508 errors.

The trick: most dashboards don't show you when you've been throttled. Your visitors see slow pages or errors. You see "everything looks fine" in cPanel.

How to detect: SSH in and run tail -f /var/log/lvestats.log if your host allows it. The "LVE" entries show throttling events.

2. "Inode" limits that never appear in the marketing

Inodes are the entries in a filesystem that point to files. Every file, folder, and email on your account counts as one inode. Most cheap hosts cap inodes at 250,000 or 500,000.

WordPress alone with several plugins and a few thousand cached pages can hit 100,000 inodes easily. Add an email account with 10 years of history and you're at the cap. When you hit it, you can't upload new files — and many cheap hosts auto-suspend accounts that exceed the limit.

This is never disclosed in the "unlimited storage" marketing. It is in the Terms of Service.

3. Concurrent process / Entry Process limits

You're allowed maybe 20–40 concurrent PHP processes. Sounds like plenty. But every visitor on your site, every cron job, every background task counts toward this number.

Hit a moment of organic traffic — a tweet goes mildly viral, an email blast lands — and suddenly 50 visitors arrive simultaneously. Process limit hit. Visitor 41 onwards sees a "503 Service Unavailable" page until things drain.

Your host doesn't notify you. The traffic spike that should have been your best week becomes the moment your site went down.

4. "Unlimited bandwidth" with a hidden "fair use" clause

Read your host's TOS. There will be a clause along the lines of: "Bandwidth and storage are unlimited subject to fair and reasonable use, as determined by the provider."

"Determined by the provider" is the key phrase. In practice, this means: if your bandwidth is significantly higher than the average customer's, you'll get a friendly email asking you to upgrade or move.

What "unlimited" actually means The internal threshold is usually around the 95th percentile of all customer accounts on that server. If you're using more bandwidth than 95% of other customers, you're a "policy violator." This number isn't published.

5. Backups that quietly stop running

Many cheap hosts include "free daily backups" but quietly disable them when:

  • Your account exceeds a certain size (often 5–10 GB)
  • The backup process keeps timing out (large database = slow backup)
  • You've used too many inodes

The backups stop. The dashboard doesn't tell you. You discover this on the day you actually need a backup. By then it's months too late.

Test your backups quarterly: ask your host to restore a recent one to a staging account. If they can't, you don't have backups.

6. Database connection limits set artificially low

Your host might allow you 50 simultaneous MySQL connections. Sounds like a lot. WordPress with a busy plugin can use 5–10 connections per page load. WooCommerce with logged-in users can use more. Twenty concurrent visitors and you're hitting the limit.

The error message is "Too many connections" — usually surfaced as a generic database error to your visitors. Your host doesn't proactively raise this; they wait for you to file a ticket and then ask if you'd like to upgrade.

7. The shared IP address poisoned by other customers

Your site shares an IP with hundreds of others on the same server. If even one of them sends spam, runs phishing, or gets blacklisted, the entire IP gets flagged. Your customer's emails go to spam folders. Your site gets blocked by corporate firewalls.

You did nothing wrong. Your neighbors did. There's no warning system.

Solution: get a dedicated IP (most hosts charge $2–$5/month extra), or move to a host that uses container isolation properly so each customer has cleaner network separation. Or move to a VPS, which has its own IP.

Suspect your host is overselling?

Send us your domain. We'll run a non-invasive performance test from multiple locations and tell you if you're being throttled, IP-blocked, or running into resource limits.

Get a hosting check

How to spot an oversold host before you buy

Before signing up:

  1. Read the Terms of Service. Search for "fair use," "inode," "concurrent," "CPU limit." If those words appear, the limits exist whether or not the marketing mentions them.
  2. Ask sales for the actual numerical limits for CPU, RAM, inodes, processes, and database connections. Honest hosts will give you specific numbers. Dishonest ones will deflect with "you'll never hit them."
  3. Check the host's own page speed. If their marketing site is slow, what does that tell you about their hosting?
  4. Look at server-status pages and Reddit. r/webhosting and HostingForums have ongoing threads about which hosts oversell most aggressively. The patterns are visible in customer complaints.

Are we any different?

Honest answer: every shared hosting business has resource limits. Servers are finite. The difference is in how aggressive the overselling is and how transparent the host is about it.

Our shared hosting plans state the limits explicitly. We don't use the word "unlimited" except where it's literally true (number of email accounts, number of subdomains). Our backups have monitoring; if they stop running, we know within an hour, not three months later.

That's not because we're saints. It's because at scale, the operational cost of dealing with angry customers from overselling exceeds the revenue overselling generates. Hosts who oversell aggressively are betting that the churn is cheaper than the staff. We've calculated it the other way.

The takeaway

Hosting marketing is full of words that mean less than they appear to. "Unlimited" means "unlimited until our internal threshold." "99.9% uptime" means "we will refund your $3 when we're down for a day." "Free backups" means "until we decide your account is too big to back up efficiently."

This isn't unique to hosting. But the gap between marketing claims and operational reality is wider in shared hosting than in most consumer purchases.

Read the TOS. Ask for actual numbers. And test your backups. Those three habits will save you 90% of the heartache from an oversold host.