Quick Answer: A website usually goes down because of a server problem, an expired domain or SSL certificate, a DNS issue, a faulty plugin or theme update, exceeded resource limits, or a security block. Start by checking whether the site is down for everyone or only you, then read the exact error message, since it points to the cause.
Few things make a business owner panic faster than typing in their own web address and seeing a blank page or an error message. Every minute offline can mean missed calls, lost orders and visitors who go straight to a competitor.
The good news is that most outages have a short list of causes, and the error you see is usually a strong clue. This guide walks you through how to confirm the problem, what common error messages mean, and the order in which to check things so you fix the issue fast instead of guessing.
Check your site from a different network and an online status tool. If it loads elsewhere, the problem is on your device or connection, not your website.
Before touching any settings, rule out a local issue:
If the site works on mobile data but not on your office network, your IP address may have been blocked by the server firewall after repeated failed logins. That is a common and easy fix through your host’s support team.
The error code tells you where the failure is happening: on your server, in your site’s code, in DNS, or in your security settings.
| What You See | What It Usually Means | Where to Look First |
|---|---|---|
| 500 Internal Server Error | Something in the site’s code or configuration failed | Recent plugin, theme or code changes |
| 502 Bad Gateway | One server got an invalid response from another | Server load, PHP processes, CDN or proxy |
| 503 Service Unavailable | Server is overloaded or in maintenance | Traffic spikes, resource limits, maintenance mode |
| 504 Gateway Timeout | The server took too long to respond | Slow database queries, heavy scripts |
| 403 Forbidden | Access is denied | File permissions, firewall or security plugin |
| 404 Not Found | The page does not exist at that address | Changed URLs, deleted pages, permalink settings |
| “This site can’t be reached” | Browser cannot find the server | DNS records, domain status |
| “Your connection is not private” | SSL certificate problem | Certificate expiry or setup |
| “Error establishing a database connection” | WordPress cannot reach its database | Database server, login details, corrupted tables |
An expired domain is one of the most common and most preventable causes of a site going offline. When a domain lapses, the registrar typically stops pointing it to your hosting, and visitors see a parking page or nothing at all.
Most registrars offer a grace period after expiry where you can still renew, but recovery gets more expensive the longer you wait. Turn on auto renew and keep the billing card on file current. Many renewal failures happen simply because a card expired.
If visitors see a full screen privacy warning, your SSL certificate has likely expired or was installed incorrectly. Free Let’s Encrypt certificates have short lifespans (currently 90 days) and are designed to renew automatically. If auto renewal fails, browsers like Chrome, Safari and Firefox will warn visitors away from your site.
DNS connects your domain to your server. If records were edited by mistake, nameservers were changed, or a recent hosting move has not finished updating, browsers cannot find your site. This often shows up as “This site can’t be reached” or a server IP not found message.
For WordPress sites, a faulty plugin or theme update is the leading cause of sudden errors. A new version may conflict with your PHP version, another plugin or your theme.
Since WordPress 5.2, the platform includes a recovery mode. If a plugin causes a fatal error, the site shows a “critical error” message and WordPress emails the admin address a special login link that lets you turn off the faulty plugin. Check the admin inbox, including spam, before anything else.
Every hosting plan has limits on CPU, memory and simultaneous processes. A sudden traffic spike, a busy online store sale, or aggressive bots crawling your pages can push a site past those limits, which often shows up as 503 or 508 errors. If this keeps happening during normal traffic, it is a sign the site has outgrown its current plan.
Hardware failures, network problems at the data center and planned maintenance can all take a site offline. Reputable hosts publish status updates and notify customers about scheduled work. This is the one cause you cannot fix yourself, which is why responsive support matters so much.
Malware infections can crash a site, redirect visitors to spam pages, or get the site flagged by Google Safe Browsing with a red “Deceptive site ahead” warning. Some hosts also suspend infected accounts to protect other customers. Signs include unfamiliar files, strange redirects, new admin users you did not create, and sudden spam pages showing in Google results.
Accounts can be suspended for unpaid invoices, terms of service violations, or using far more resources than a plan allows. A suspension page usually says so directly. Check your hosting account email for billing or policy notices.
Security plugins and server firewalls protect your site, but overly strict rules can block real visitors, entire countries, or even you. If the site works for some people and not others, firewall rules and IP blocks are worth checking.
Work from the outside in: confirm the outage, read the error, check domain and SSL status, review recent changes, then contact your host.
Expert tip: Giving support those details up front can turn a long back and forth into a quick fix. “502 error since 2:15 PM, started after updating WooCommerce, domain and SSL are valid” gives a technician almost everything they need.
No host can honestly promise zero downtime, but you can make outages rarer and shorter.
Open your site on a different network, such as your phone using mobile data, and test it with a free checker like downforeveryoneorjustme.com. If the site loads elsewhere, the issue is likely your device, browser cache or local network, or your IP may be blocked by a firewall.
This usually means the problem is local. Your computer may have an old DNS record cached, a browser extension may be interfering, or your office IP may have been blocked after failed login attempts. Clear your browser cache, try incognito mode, and ask your host to check for an IP block.
A 503 error means the server is temporarily unable to handle the request. Common causes include a traffic spike, hitting your plan’s resource limits, a stuck maintenance mode, or heavy bot activity. It is often temporary, but repeated 503 errors are a sign the site needs more resources or optimization.
When a domain expires, it usually stops pointing to your website and email, so both can go offline. Most registrars give a grace period to renew at the normal price, followed by a redemption period with extra fees. If it is not renewed in time, someone else may register it.
Yes. A plugin that conflicts with your theme, PHP version or another plugin can trigger a critical error and take the site offline. WordPress recovery mode emails the admin a link to log in and turn off the faulty plugin, or your host can help deactivate it through the file manager.
It depends on the cause. A plugin conflict or expired SSL can often be fixed within minutes once identified. DNS changes can take hours to fully update, while server hardware problems depend on your host’s response. Monitoring tools help you catch outages early, which shortens downtime significantly.
Brief, occasional downtime generally does not cause lasting ranking damage. Google’s own guidance notes that short outages are expected. However, outages that last a day or more, or happen repeatedly, can lead Google to crawl the site less often and may temporarily drop affected pages from results.
Most quality hosts aim for at least 99.9% uptime, which allows roughly 43 minutes of downtime per month. Pay attention to how a host defines and measures uptime in its service level agreement, and use your own monitoring tool so you have independent records.
When your website goes down, a calm, step by step check beats random fixes every time. Confirm the outage, read the error, check your domain and SSL status, review recent changes and bring your host in early. Most outages trace back to a handful of causes, and many of them can be prevented with auto renew, backups and monitoring.
If downtime, slow support or resource limits keep getting in your way, it may be time for hosting built around reliability. The WebHostServers.co team offers 24/7 human support, daily backups and free website migration. Feel free to reach out to our team with any questions about keeping your site online.