First: Confirm It's Actually Down

Before assuming the worst, rule out the obvious. Sometimes a website appears down only to you because of a local browser cache issue, your own internet connection, or a DNS propagation lag if changes were made recently.

  • Visit downforeveryoneorjustme.com or isitdownrightnow.com and enter your domain. If these tools report your site as online, the problem is on your end - clear your browser cache or try on mobile data.
  • Try your site on a different device and a different network (e.g., mobile data rather than Wi-Fi).
  • Ask a colleague or contact in a different location to try loading the site.

If these tools confirm the site is down for everyone, you have a genuine outage on your hands. Keep reading.

Note the Error Message - It Tells You a Lot

The error code your browser displays is not just an annoyance - it's a diagnostic clue. Different errors point to different root causes:

  • 500 Internal Server Error - Something has gone wrong on the server itself. Often caused by a bad CMS plugin update, corrupt file, or PHP/runtime error.
  • 503 Service Unavailable - The server is overloaded or temporarily offline. Could be a traffic spike, a hosting maintenance window, or a resource limit being hit.
  • 502 Bad Gateway - Your hosting server received an invalid response from an upstream server. Often related to caching layers, CDN issues, or load balancer problems.
  • 404 Not Found - The URL you're visiting doesn't exist on the server. If this is your homepage, something has gone badly wrong with your routing, redirects, or CMS configuration.
  • Blank white screen - Known as the "White Screen of Death" in CMS environments. Usually a fatal PHP error that the platform is suppressing. Common after updates.
  • ERR_NAME_NOT_RESOLVED or DNS errors - Your domain name is not resolving. This often means your domain registration has lapsed, your DNS records have been changed, or a name server is unreachable.
  • SSL certificate warning - Your browser is blocking the site because your HTTPS certificate has expired or become invalid. Visitors will see a scary "Your connection is not private" warning.

Take a screenshot of the error. Whether you fix this yourself or call in professional emergency support, that error message is evidence. Don't just refresh and hope it goes away - document it first.

Check Your Hosting Control Panel

If you have access to a hosting control panel (cPanel, Plesk, Kinsta, WP Engine dashboard, etc.), log in now. Look for:

  • Any maintenance announcements or banners from your host
  • Server resource usage - has CPU or memory hit its limit?
  • Recent activity logs - did anything change in the last hour?
  • Scheduled tasks or cron jobs that may have triggered a process

Many hosting providers also have a public status page. Search for "[your host name] status" to check whether they're experiencing a wider outage. If they are, your only option may be to wait - or to initiate an emergency migration to a more reliable provider.

When Did It Last Work?

This question sounds simple, but it's one of the most powerful diagnostic tools available. Pinpointing the last known good state helps you narrow the cause dramatically.

  • Was there a plugin, theme, or CMS update applied recently? Updates are one of the most common causes of sudden outages, particularly in WordPress, Umbraco, and similar platforms.
  • Did someone edit a configuration file or make a code deployment?
  • Has your domain or hosting renewal recently been due? Lapsed registrations are a surprisingly common cause of sudden "disappearance."
  • Has there been a spike in traffic? A press feature, a viral post, or a large email campaign can push server resources beyond their limits.
  • Did your SSL certificate expire? Certificates typically renew automatically, but the process can fail silently.

Immediate Steps to Take

  1. Document everything. Screenshot the error, note the time, write down anything that changed recently.
  2. Check your hosting status page and your email for any communications from your provider.
  3. Log into your hosting panel and look at recent activity and server health metrics.
  4. Contact your hosting provider via chat or phone - not just ticket. Most offer priority emergency support channels.
  5. Notify your team. If your site is a revenue-generating asset, your sales team, customer service, or marketing lead needs to know immediately.
  6. Post a brief message on social media if you have significant web traffic. Transparency with your audience prevents damaging speculation.
  7. Activate a maintenance page if possible - a branded holding page is far less damaging to trust than an error screen.

When You Need Professional Emergency Help

If you've run through the above and cannot identify the cause - or if the cause is clear but beyond your technical capability to fix - it's time to escalate. The key metric here is time. Every minute your site is offline is costing you: in lost enquiries, reduced trust, damage to search rankings, and in some cases, contractual SLA breaches with your own customers.

A professional emergency digital support service should be able to:

  • Triage the issue remotely within the first 15–30 minutes
  • Access your hosting environment and CMS directly
  • Identify the root cause, not just apply a temporary fix
  • Restore from a clean backup if required
  • Get you back online - and document what happened so it can't happen again
88% of users won't return after a bad site experience
£4,900 average hourly cost of downtime for an SME
4 min average response time with Parachute emergency cover

Prevention: What to Have in Place Before It Happens Again

Once you're back online, the immediate crisis is over - but the real work begins. A site that has gone down once is statistically more likely to experience issues again, particularly if the root cause was structural rather than incidental. Consider putting the following in place:

  • Uptime monitoring - Tools like UptimeRobot or Pingdom alert you the moment your site goes down, rather than you finding out from a customer.
  • Regular automated backups - Stored off-server, and tested periodically to ensure they're actually restorable.
  • Staging environments - Any update or code change should be tested on a staging copy of your site before it touches the live environment.
  • An emergency support retainer - Having a trusted agency on standby with knowledge of your site means recovery time is measured in minutes, not days.