Your website is down. Maybe you found out because a customer called. Maybe you noticed it yourself when you tried to pull something up during a meeting. Either way, the immediate feeling is a combination of alarm and helplessness, especially if you are not the person who built the site and do not know where to start.
Most outages fall into a few recognizable patterns. Confirming which one you are dealing with usually determines whether the answer is a billing issue, a hosting problem, or an application failure inside the site.
Step 1: Confirm That It Is Actually Down
The first question is whether the problem is broadly visible or limited to one device, browser, or network.
External checks through tools like downforeveryoneorjustme.com or isitdownrightnow.com usually answer that quickly. If those checks confirm downtime from outside your network, the issue is real.
If the tool says your site is up but you cannot reach it, the issue may be:
- A caching or DNS issue specific to your browser or network (try a different browser, or try accessing the site from a mobile device using cellular data instead of WiFi)
- A problem with your internet connection, not the site itself
- A DNS propagation delay if your site was recently migrated or DNS settings were recently changed
If multiple people on different networks and devices cannot reach the site, the situation is worth treating as a genuine outage.
Step 2: Note What You Are Seeing
The error message or behavior the browser shows is useful diagnostic information. Recording the exact message before any calls begin usually makes support conversations faster. Common messages and what they suggest:
“This site can’t be reached” or “ERR_CONNECTION_REFUSED”: The server is not responding at all. This often points to a hosting server problem, a firewall issue, or in some cases, a billing lapse on your hosting account.
“502 Bad Gateway” or “503 Service Unavailable”: The server received your request but could not process it. This may indicate that WordPress or another application on the server crashed, that the server is overloaded, or that a recent update or change broke something.
“Your connection is not private” (SSL error): The site may still be technically reachable but is displaying an SSL certificate problem. See the separate article on SSL certificate errors for steps specific to this situation.
“404 Not Found”: The server is reachable but cannot find the specific page. If this appears on your homepage rather than a specific internal page, it may indicate a WordPress permalink issue, a misconfigured server redirect, or a change to the site’s file structure.
Blank white page: Sometimes called a “white screen of death” in WordPress. The server is responding but returning nothing. This is often caused by a PHP error, a failed plugin update, or a memory limit issue.
Site loads but is broken visually: Missing images, broken layouts, or a default theme appearing instead of your design. This may indicate a partial failure, a theme issue, or a caching problem.
Step 3: Whether It Is Only Your Site or Your Entire Hosting Account
If you have multiple pages or sites under the same hosting account, try accessing a few of them. If all of them are down, the problem is likely at the hosting server or account level. If only one site is down, the problem may be specific to that site’s configuration.
Also try accessing your hosting control panel directly. If your hosting provider’s login page is also unreachable, that points to a broader hosting infrastructure issue.
Step 4: Recent Alerts or Notices
Hosting providers typically send email notices before and during maintenance windows, and also when billing fails. The email address attached to the hosting account often contains the fastest explanation, especially when the cause is a missed renewal or a scheduled maintenance event.
If billing lapsed, the fix is often straightforward: renewal through the hosting portal, followed in some cases by manual reactivation from the host.
Step 5: Contact Your Hosting Provider
For most types of outages, the hosting provider is the first escalation point. The most useful details to have ready are:
- Your account login email
- Your domain name
- The exact error message you are seeing
- When you (or a customer) first noticed the problem
- Whether any changes were made to the site recently (plugin updates, theme changes, new content published)
Most major hosting providers offer live chat support in addition to tickets and phone support. When the outage is actively costing business, the fastest channel usually helps, and support tends to move more quickly when they receive confirmed downtime details and the exact error message.
If your site is managed by a web professional or agency, contact them at the same time. They may have faster access to your hosting environment and may already be aware of the issue if they have uptime monitoring in place.
Step 6: If the Outage Is Caused by a Recent Change
If someone made a change to the site shortly before it went down (a plugin update, a theme change, a new page published), that change is the most likely cause and the most direct path to resolution.
If you have a staging environment, the change may have been deployed from there. If you have a recent backup, restoring to it may be faster than diagnosing the specific cause.
If the change was a plugin update and your host uses WordPress management tools (such as those found in managed WordPress hosting control panels), they may be able to roll back the update or restore from an automatic pre-update backup.
Step 7: If the Outage Persists and Your Host Cannot Identify the Cause
If your hosting provider confirms their servers are operating normally but your site remains down, the problem is likely specific to your site’s configuration, application, or files rather than the server itself.
At this point, if you do not have a web professional involved yet, it is worth bringing one in. Diagnosis of application-level failures (WordPress crashes, database errors, PHP conflicts) is faster for someone with server access and experience with the types of problems that cause each error code.
What to Do While You Wait
If the outage is going to take more than a few minutes to resolve, businesses often post a short acknowledgement and an alternate contact method. That can mean a Google Business Profile update, a social post with a phone number, or a temporary email contact. Silence usually creates more confusion than a brief status note.
After the Site Comes Back Up
Once the site is restored, get a brief written explanation from whoever fixed it. You want to know:
- What caused the outage
- What was done to fix it
- Whether any data was lost or any backups were used
- Whether any changes need to be made to prevent the same thing from happening again
If your site went down due to an expired SSL certificate, an expired domain, or a missed hosting renewal, put reminders on your calendar well before the next expiration date. These are preventable causes of downtime, and they tend to recur unless the renewal process is made more reliable.
Finally, sites with uptime monitoring usually find out about downtime before a customer reports it. That earlier detection is often the difference between a brief interruption and a longer business disruption.
Related reading: Why an SSL Certificate Error on Your Own Website Needs Immediate Attention, Backups Are Not Optional: What Business Website Backups Should Actually Look Like, and What Those Plugin Update Warnings Actually Mean and What Happens If You Ignore Them.