Drawback of shared hosting?

Dani AI

Generated

Shared hosting is cheap and simple, but the tradeoffs are isolation and predictability. The examples in this thread illustrate that clearly: ’s database-limit incident is a classic “noisy neighbor” failure where one tenant exhausts shared quotas and causes timeouts; ’s post is a reminder that attacks aimed at one account (DDoS, spam, blacklisting) can spill over and disrupt others on the same IP or network.

Practical diagnostic checklist to add context:

  • Check host-provided resource graphs (CPU, memory, I/O, concurrent processes) and inode/file-handle use around the outage times.
  • Inspect webserver and database error logs for connection timeouts, 5xx spikes, or repeated open-failure messages.
  • Review access logs for traffic spikes or many identical requests from few IPs (DDoS signal).
  • Run external uptime/synthetic checks to confirm whether problems are intermittent or sustained.
  • Ask the provider for per-account process lists and any throttling events tied to the account.

Short-term mitigations that often help without immediate migration:

  • Add aggressive page/object caching and offload static assets to a CDN or object storage.
  • Move mail to a dedicated third-party provider to avoid shared-IP blacklisting.
  • Optimize database use: shorten connection lifetimes, remove long-running queries, and use caches for frequent reads.
  • Request host-side rate limits or temporary IP blocks for abusive traffic, or ask for account isolation/dedicated IP.

When to consider upgrading: recurring resource caps, need for custom server modules or root access, frequent neighbor-caused outages, regulatory/compliance needs, or business-critical uptime. For hobby sites shared hosting is fine; for forums, e-commerce, or anything with steady traffic, plan a migration to VPS/managed cloud with backups, lowered DNS TTL, and a staged validation.

Recommended Answers

All 2 Replies

I would say there are many drawbacks with shared hostings. What do you need it for?

Personally I try to avoid them. Once I was asked to find why a specific website at a specific hour stopped working, after some research I saw that MySQL had max_user_connections & max_connections set to 161 (which is very low). In practice one of the other websites opened so many permanent connections, during that hour, that the pool of the server was saturated, so all the other attempts were going in timeout.

Similar issues happens if the open file limit of MySQL is to low and if in the server there are too many tables, which are files. If the limit is reached, then it causes accessing errors.

Member Avatar for Member #120589

Had an issue with other site on host getting DDOSed. Over an over for weeks. Killed off my friend's forum.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.