Dealing with Hosting Provider Limits and Throttling

Introduction

Hosting providers use limits to keep servers stable and prevent one account from consuming too many shared resources. These limits are common on shared hosting, reseller hosting, cloud hosting and VPS plans.

When a website reaches hosting limits, it may become slow, return errors, fail to send email, show 508 Resource Limit Reached, produce 503 errors, delay PHP requests or temporarily stop responding. The correct fix depends on which limit is being reached and why.

Quick answer

Hosting limits and throttling

Hosting limits are rules that define how much server resource an account or VPS can use.

Common limits include:

• CPU usage
• memory/RAM
• disk I/O
• IOPS
• entry processes
• PHP workers
• database connections
• database size
• inode count
• storage usage
• bandwidth
• email sending volume
• cron job frequency
• process count
• file upload size
• request rate

Why hosting providers use limits

Hosting limits protect the stability of the server.

Providers use limits to:

• prevent one account from affecting others
• reduce abuse
• control spam
• protect shared IP reputation
• prevent runaway scripts
• limit malware impact
• keep server load predictable
• separate plan tiers
• avoid database overload
• protect storage and backups

Shared hosting limits

Shared hosting usually has the strictest limits because many customers use the same server.

Common shared hosting limits:

• CPU percentage
• physical memory
• I/O speed
• entry processes
• number of processes
• inode count
• email per hour
• database size
• MySQL connections
• cron execution
• maximum execution time
• upload size
• account storage

VPS limits

A VPS gives more control, but it still has limits.

Common VPS limits:

• allocated CPU cores
• RAM
• swap
• disk space
• disk I/O
• network bandwidth
• port speed
• provider abuse limits
• IP reputation restrictions
• outbound email restrictions
• backup snapshot limits
• virtualization overhead

Entry processes and PHP workers

Entry processes and PHP workers control how many dynamic requests can run at the same time.

They affect:

• WordPress page loads
• WooCommerce checkout
• admin dashboard
• AJAX requests
• contact forms
• API calls
• cron tasks
• plugin-heavy pages

Common symptoms:

• 508 Resource Limit Reached
• slow dynamic pages
• admin panel freezes
• intermittent 503 errors
• forms fail during traffic spikes
• checkout delays

CPU and memory limits

CPU and memory limits affect how much work the website can perform.

High CPU may come from:

• traffic spikes
• uncached WordPress pages
• heavy plugins
• slow database queries
• bots/crawlers
• image processing
• backups
• malware
• cron jobs

High memory may come from:

• PHP workers
• large imports
• WooCommerce
• page builders
• database queries
• memory leaks
• too many concurrent tasks

Disk I/O and inode limits

Disk I/O controls how fast files and database data can be read or written. Inode limits control how many files and folders an account can have.

Disk I/O issues may come from:

• large backups
• cache generation
• many small files
• malware files
• logs growing too large
• heavy database writes
• image processing
• imports/exports

Inode problems may come from:

• cache files
• old backups
• email storage
• temporary files
• session files
• malware
• many small generated thumbnails

Email sending limits

Many hosting providers limit outgoing email to prevent spam and protect reputation.

Limits may include:

• emails per hour
• emails per day
• recipients per message
• bounce rate limits
• SMTP login limits
• PHP mail limits
• attachment size
• queue size
• account suspension thresholds

Why this matters

Understanding limits helps you avoid guessing. You can separate DNS problems, application problems, hosting limits and server capacity issues.

How to check hosting limits

Use hosting panel metrics, logs and CheckDomainHealth tools.

1. Website status — Confirm whether the site returns 200, 503, 508, 500 or timeout.
2. Resource usage — Review CPU, memory, I/O, entry processes and process count.
3. Error logs — Check PHP, web server and application logs.
4. Traffic pattern — Look for spikes, bots, crawlers or campaigns.
5. Cron jobs — Check scheduled tasks and backups.
6. Database usage — Check slow queries, connection limits and database size.
7. Email sending — Check mail queue, hourly limits and bounces.
8. File count — Check inode usage and old backups/cache.

Common problems

How to deal with hosting throttling

1. Step 1: Identify the exact limit

   Check whether the issue is CPU, RAM, I/O, entry processes, email, bandwidth or inode count.

2. Step 2: Check logs and timing

   Match resource spikes with traffic, cron jobs, backups, plugin actions or errors.

3. Step 3: Enable caching

   Use page cache, object cache or CDN where appropriate.

4. Step 4: Reduce heavy plugins/scripts

   Disable unused plugins, themes, modules and background tasks.

5. Step 5: Optimize database

   Review slow queries, transients, revisions and large tables.

6. Step 6: Control bots

   Limit abusive crawlers and unwanted automated traffic.

7. Step 7: Move heavy jobs

   Run backups, imports and scans during low-traffic periods.

8. Step 8: Fix email sending

   Use SMTP or transactional email for important/high-volume messages.

9. Step 9: Clean storage and inodes

   Remove old backups, cache files, logs and unused mail.

10. Step 10: Upgrade if needed

    Move to a stronger plan, VPS or dedicated server when optimized usage still exceeds limits.

Optimize before upgrading

Before upgrading, check whether the site is wasting resources.

Optimize:

• page caching
• image sizes
• database tables
• plugin count
• theme performance
• cron frequency
• bot traffic
• object cache
• CDN usage
• old backups
• unused files
• PHP version
• slow queries

When to upgrade hosting

Upgrade when limits are reached regularly after reasonable optimization.

Upgrade signs:

• frequent 508 or 503 errors
• repeated CPU/RAM saturation
• entry processes max out daily
• WooCommerce/admin operations are consistently slow
• traffic has grown
• cron jobs are necessary and heavy
• database workload is increasing
• shared hosting restrictions block required features
• email needs exceed hosting limits
• business risk from downtime is too high

Upgrade path:

• higher shared hosting plan
• business hosting
• managed VPS
• unmanaged VPS
• dedicated server
• load-balanced infrastructure

What to ask hosting support

Hello,

Our website appears to be hitting hosting resource limits.

Can you please confirm:

1. Which limit was reached?
CPU, RAM, I/O, entry processes, processes, email, bandwidth, inode count or database?

2. Exact time range of the limit events.

3. Top processes, scripts or URLs involved if available.

4. Whether the issue came from website traffic, bots, cron jobs, backups, email or database usage.

5. Recommended optimization or upgrade path.

Domain/account:
example.com

Thank you.

Useful hosting limit checks

Check website status:
curl -I https://example.com

Follow redirects:
curl -IL http://example.com

Check server load on VPS:
uptime

Check memory:
free -m

Check disk:
df -h

Check largest folders:
du -h --max-depth=1 ~/ 2>/dev/null | sort -h

Check running processes:
top

Check listening services:
sudo ss -tulpn

Check Apache error log:
tail -100 ~/logs/error_log

Check Nginx error log:
sudo tail -100 /var/log/nginx/error.log

Shared hosting vs VPS decision

Shared hosting is simpler but more limited. VPS hosting gives more control but requires more responsibility.

Frequently asked questions