Website Down on Shared Hosting? What to Check First 

Key highlights 

• Confirm the outage first: use an external checker before assuming your host is at fault. 

• Shared hosting resource limits can cause slowdowns, errors or temporary availability problems. 

• Error codes like 500, 502 and 503 each point to a different cause. 

• Bluehost backs shared hosting with a 99.99% uptime SLA, so recurring outages are worth investigating.  

• Recurring downtime on shared hosting can signal it’s time for a plan with more dedicated resources. 

The page won’t load. The hosting dashboard says everything is fine, but the site stays down anyway. That leaves one question: is the problem on your end, or your host’s? 

Checking things in the right order gets you to the cause of a website down on shared hosting faster than guessing. Shared hosting adds a wrinkle dedicated servers don’t have: other sites on the same server can affect performance or availability too. 

This guide walks through the checks in a practical order so you can identify the likely cause without changing unrelated settings. 

Check whether your site is down for everyone or just you 

Use an external down-checker or try loading the site from another device and network. If the site loads elsewhere but not for you, the problem sits on your end, not your host’s. Confirming this first saves you from chasing a hosting problem that might not exist. 

Use an external down-checker 

Run your domain through a third-party checker like Down for Everyone or Just Me or isup.me. These tools check your site from outside networks and report whether it loads for them. If the site loads for the checker but not for you, the problem is likely local or regional. 

Try another device and network 

Switch to a phone on cellular data instead of Wi-Fi, or ask someone on a different network to load the site. A site that loads elsewhere but not on your device points to a local DNS cache or browser issue. Clear the cache and try again before assuming the server is at fault. 

Pro tip: Check cellular data first. It skips your home router and local DNS cache in one step, so you rule out two local causes at once. 

Check your hosting account and server status 

Log into your hosting account and look for your provider’s status page, usually linked from the support or help section. Status pages separate active incidents from scheduled maintenance, so you can tell which one you’re dealing with. 

If the status page shows everything operational, the cause sits somewhere more specific: your account, your DNS or your site itself. Confirm your billing is current too, since a lapsed payment can also take a site offline. 

Note: If the status page shows a live incident, monitor the incident page rather than making changes. Editing files or DNS records during an active outage can create a second problem to fix once the first one clears. 

Rule out a domain or DNS problem 

Check whether your domain has expired and confirm your DNS records point to the right nameservers. Both are common causes of a site going dark that have nothing to do with your server itself. 

Confirm the domain hasn’t expired 

Log into your domain registrar and check the expiration date. An expired domain stops resolving even if your hosting account and files are completely fine, and auto-renewal failures happen more often than people expect. 

Give DNS changes time to propagate 

If you recently changed hosts, updated nameservers or edited a DNS record, the change can take up to 48 hours to fully propagate. Some visitors will see your site during this window while others see an error or an old version, which is normal and not a sign of a new problem. 

Pro tip: Use a DNS checker tool to see how your records are resolving across different regions.  If most regions show the correct records while a few still show the previous values, the difference may be caused by resolver caching rather than a new DNS configuration error 

Look for an SSL certificate error 

An expired or misconfigured SSL certificate can display a browser warning or prevent access before they ever reach your site. Check your certificate’s expiration date first, since most hosts auto-renew but the process can fail silently. 

If the certificate looks valid but the warning persists, check for a mismatch between the certificate and your domain. This often happens after a recent domain or subdomain change, or right after installing a new certificate that hasn’t fully activated yet. 

Mixed content, where some page elements still load over HTTP, can also trigger a partial warning even when the certificate itself is fine. 

A warning that disappears after a certificate or DNS change may have been caused by activation or propagation delay. Do not bypass the warning while it remains active.

Check your shared hosting resource limits 

Shared hosting means your account shares CPU, memory and running processes with other sites on the same server.  When your site reaches a resource limit, it may slow down, return temporary errors or become briefly unavailable. 

Three limits matter most on shared plans: 

• CPU usage: A traffic spike or a resource-heavy plugin can max out your allotted processing power. 

• Memory limits: A script may fail if it requires more PHP memory or account memory than the hosting environment makes available. 

• Concurrent processes: Shared hosting accounts can run a limited number of server tasks at the same time. Too many overlapping PHP, cron, email or database processes may delay or block new requests. 

Resource exhaustion may appear as slow loading, timeouts or a 500-series error. Check whether your hosting dashboard provides CPU, memory or process-usage reports. If it does not, ask support to review the account’s recent resource usage. 

Test for a plugin, theme or PHP conflict 

 A plugin, theme or PHP update installed shortly before the downtime may be responsible, even if the visible error message is not specific. Testing each one in isolation shows you exactly which one broke the site. 

Note: Before making changes, create a backup or confirm that a recent restore point is available. Change one item at a time so you can reverse the step if it creates another problem. 

Deactivate plugins one at a time 

 If you can access WordPress, deactivate all plugins and check whether the site returns. If it does, reactivate the plugins one at a time until the problem returns. If you cannot access WordPress, rename the plugins folder through the file manager or FTP to deactivate them together. 

Switch to a default theme temporarily 

Switch temporarily to a default WordPress theme that is already installed. If the site loads, the active theme or one of its related extensions may be causing the problem. . Keep your original theme installed so you can switch back once you find the problem. 

Pro tip: Clear your site’s cache and your browser’s cache after each test. A cached version of the broken site can make a fix look like it isn’t working yet. 

Fix a database connection error 

“Error establishing a database connection” means your site can’t reach the database that stores its content, even though the server itself may be running fine.  

Three things typically cause it: 

• Wrong credentials: The database name, username or password in your config file doesn’t match what the database expects, often after a migration or a manual edit. 

• Corrupted database tables: A table gets damaged during an update or an unexpected restart, blocking the site from reading its own content. 

• An unresponsive database server: The database service itself is overloaded or down, more likely if this started right after a resource-limit issue. 

Check the credentials first because they are easier and safer to verify before attempting a database repair. Confirm the database name, username and password in your config file match what your hosting dashboard shows. 

Check for malware or account suspension 

A site that’s inaccessible with no error message, or flagged with a browser warning, often means malware or a suspended account. Both get flagged by your host or by Google, usually with a specific notice. 

Malware shows up in a few recognizable ways: 

• A browser or search warning: Chrome or Google Search Console flags the site as unsafe or hacked. 

• Unfamiliar admin users or files: New accounts or files you didn’t create appear in your dashboard or file manager. 

• Redirected or defaced content: Visitors land on a different page than the one you built, often spam or ads. 

Account suspension usually follows excessive resource use, a terms-of-service violation or a missed payment and your host typically emails a notice explaining why. Check your email, including spam, before assuming the suspension came without warning. 

Either cause needs a real fix before the site comes back online, not just time. 

Know when recurring downtime means it’s time to upgrade 

One resource-limit event may come from a traffic spike, scheduled task, inefficient plugin, malware or configuration problem. Investigate the cause before deciding whether the plan is too small. If the problem follows a regular schedule, check backups, security scans, imports and cron jobs before concluding that the website needs a larger plan. 

A few signs point to outgrowing your current plan: 

• Downtime that follows a normal traffic day, not just a spike 

• The same error, like a 503 or a resource warning, recurring on a regular schedule 

• Support confirming the account is regularly near its visitor or resource ceiling 

Published monthly-visit figures are planning guidance rather than fixed traffic limits. Actual capacity depends on the website’s code, caching, database activity and visitor behavior. Once a site consistently pushes past that range, more resource headroom solves the downtime issue for good. 

Bluehost upgrade options: Bluehost’s shared hosting plans include a clear upgrade path to higher-tier hosting or VPS. Growing past shared hosting doesn’t mean starting over with a new host, backed by a 99.99% uptime SLA and 24/7 expert support. 

 If legitimate traffic or processing demand repeatedly exhausts the shared hosting resources, compare a higher Bluehost Web Hosting tier or VPS Hosting for greater resource control. 

Final thoughts 

Most cases of a website down on shared hosting trace back to one of these checks. Working through them in order gets you to the fix faster than troubleshooting at random. If every step comes back clean and the site is still down, your host’s support team can pull server-side logs you can’t see. 

Still dealing with downtime that keeps coming back? Bluehost backs every shared hosting plan with a 99.99% uptime SLA and 24/7 expert support. Help is there the moment resource limits or server issues get in the way.  

Still experiencing recurring resource-related downtime? Compare Bluehost Web Hosting plans and choose the resource level that supports your site’s current traffic and growth. 

FAQs