Your website just went down. Before you panic, here is the single most important thing to do in the first 60 seconds: check whether the problem is on your end or theirs. Open isitdownrightnow.com or downforeveryoneorjustme.com and enter your domain. If the tool confirms your site is down for everyone — not just you — you have a genuine outage that needs resolving now. If it says the site is up, the problem is local to your device or network, and a quick restart or cache clear usually fixes it.
That one check saves you from spending 45 minutes on the phone with your hosting provider when the issue is simply a stale browser cache on your laptop.
How Much Is Every Minute Actually Costing You?
For a small UK business, a downed website is not just an inconvenience. Downtime can cost small businesses an average of £412 per minute — and that figure does not include the longer-term reputational damage: a customer who lands on an error page and cannot find your contact details does not wait around. They go to your competitor.
The average website experiences three hours of host downtime every month and 760 outages per year, according to research by Hosting Facts. Most of those outages are short and unnoticed — but the ones that stretch beyond 20 minutes during business hours are the ones that cost you.
The pressure to act fast is real. Here is exactly what to do.
Step 1: Confirm It Is a Real Outage (Not a Local Glitch)
Before touching anything else, rule out the simplest explanations:
- Run a down-checker tool. Use isitdownrightnow.com or downforeveryoneorjustme.com. Both test your URL from multiple global locations simultaneously.
- Switch networks. Turn off your Wi-Fi and load the site on 4G/5G mobile data. If it loads fine on mobile data, your broadband router or ISP is the culprit — not your hosting.
- Try a different browser and device. A cached error page can make a healthy site look broken.
- Check an incognito/private window. Browser extensions and logged-in cookies occasionally cause loading failures that look like genuine downtime.
If the checker confirms the site is down globally, move to Step 2.
Step 2: Check Your Hosting Provider's Status Page
Your hosting company is the most common source of unexpected downtime. Shared hosting means your website sits on the same server as hundreds of other websites. When that server struggles, everyone on it is affected.
Go directly to your hosting provider's status page. Most UK hosts maintain one:
- SiteGround: status.siteground.com
- Heart Internet: status.heartinternet.co.uk
- 123 Reg: status.123-reg.co.uk
- GoDaddy UK: status.godaddy.com
- Krystal: status.krystal.co.uk
Also check their official Twitter/X account — hosts frequently post real-time updates there before updating their status page, because updating social media takes 30 seconds and updating a formal status page takes longer.
If the host confirms an active incident, your job is to wait and monitor — there is nothing you can change on your end that will speed up their infrastructure repair. Set a timer to recheck every 15 minutes.
If the host's status page shows everything green (all systems operational) while your site is still down, the problem is almost certainly specific to your account. Log in to your hosting control panel (cPanel, Plesk, or your host's custom dashboard) and look for any account-level warnings: suspended accounts, resource limit alerts, or recent error logs. If you are not sure what you are looking at, remote hosting support can help you read those signals quickly.
Step 3: Identify Which of These Six Causes Fits Your Situation
Most UK small business website outages fall into one of six categories. Identifying the right one saves you significant time.
1. Hosting Server Failure
Signs: Host's status page shows an active incident. Your error page says "503 Service Unavailable" or "502 Bad Gateway."
What to do: Wait for host resolution. While you wait, post a brief notice on your Google Business Profile and social media so customers know you are aware of the issue. If the outage runs beyond two hours with no update from your host, call their support line rather than using live chat — phone queues clear faster during widespread outages.
2. Expired Domain Name
Signs: The error says "This site can't be reached" or your browser shows "DNS_PROBE_FINISHED_NXDOMAIN." Your site was last renewed more than a year ago.
What to do: Log in to your domain registrar (GoDaddy, Namecheap, 123 Reg, etc.) immediately. Most registrars offer a grace period of 30 days after expiry during which you can renew without penalty. After that, the domain enters a redemption period where recovery costs can run into hundreds of pounds. Renew it now — DNS propagation after renewal typically takes between 15 minutes and 48 hours depending on your registrar and TTL settings.
Counter-intuitive tip: Even if you set up auto-renewal, check that your payment card on file has not expired. A surprising number of domain outages happen because an auto-renewal failed silently on an expired card, and the registrar's warning emails went to an old address. If the domain settings, nameservers, or DNS records need untangling, see domain related problems for remote help.
3. Expired or Broken SSL Certificate
Signs: The site loads, but browsers show a red "Not Secure" warning or block access entirely. Your URL begins with http:// instead of https://.
What to do: Log in to your hosting control panel and check your SSL certificate expiry date. If you use a free Let's Encrypt certificate (the most common type), auto-renewal sometimes fails if your hosting account has been modified. Most hosts allow you to re-issue the certificate in one click from within cPanel. If you use a paid SSL through your registrar, contact them directly to renew.
SSL errors are one of the fastest ways to lose customer trust — visitors see a security warning and immediately leave. If the certificate keeps failing or you are getting mixed-content errors, SSL and HTTPS issues are worth looking into before customers notice.
4. WordPress Plugin or Theme Conflict
Signs: Your site was working fine until a recent update. The error shows a white screen, a PHP fatal error, or a 500 Internal Server Error. You (or your developer) updated something in the last 24–48 hours.
What to do: Access your site's files via FTP or your host's File Manager. Navigate to wp-content/plugins/ and rename the entire folder to plugins_disabled. This deactivates all plugins at once and will usually restore the site immediately if a plugin conflict is the cause. Once the site loads, rename the folder back to plugins and reactivate plugins one by one — testing after each — until you identify the culprit.
If a theme update is suspected, switch to a default WordPress theme (Twenty Twenty-Four) via your database or FTP. For conflicts that go deeper than a simple deactivation can fix, website functionality issues covers CMS faults, broken plugins, and API errors.
5. Bandwidth or Resource Limit Exceeded
Signs: Error page says "508 Resource Limit Reached" or "Account Suspended." Happens suddenly after a spike in traffic — perhaps a social media post went viral, or you were featured in a local press article.
What to do: Log in to cPanel and check your resource usage stats. If you have hit your bandwidth ceiling, contact your host about upgrading your plan or requesting a temporary limit increase. Some hosts will restore access immediately on request while you arrange an upgrade. This is one situation where a quick phone call beats waiting in a live chat queue.
6. DNS Misconfiguration
Signs: You recently changed hosting providers, migrated your website, or edited your DNS settings. The site works from some locations but not others.
DNS settings getting changed incorrectly can happen during a website migration, a hosting change, or even an accidental edit — causing your domain to stop pointing to the right place even though your website files are completely fine.
What to do: Use dnschecker.org to see how your DNS records are propagating worldwide. If records are inconsistent across different global locations, propagation is still in progress — this can take up to 48 hours and there is little you can do to speed it up. If records look incorrect (pointing to the wrong IP address), log in to your DNS provider and verify that your A record points to your current hosting server's IP.
Step 4: Check Your Error Logs
If none of the above applies and your site is still down, your hosting error logs are the next place to look. In cPanel, find the "Errors" section or "Raw Access Logs." The entries at the bottom of the file are the most recent and typically tell you exactly what failed and when.
Common entries to look for:
PHP Fatal error— a code problem, often from a bad plugin or updatePermission denied— file permissions were changed, often after a migrationMySQL server has gone away— your database is unreachable, which requires hosting supportmod_security— a security rule is blocking requests, usually after a false-positive trigger
You do not need to be a developer to read these logs — paste the error line into Google and you will usually find the exact fix within the first two results.
Step 5: Communicate With Your Customers While You Fix It
This step is the one most UK business owners skip, and it is the one that causes the most lasting damage. A customer who sees your site is down and hears nothing from you will assume you have closed, been hacked, or are simply unreliable. A customer who sees your site is down and then spots a quick post on Facebook saying "We're aware our site is having a technical issue — we're on it and expect to be back online within the hour" will wait. Transparency converts a potential lost customer into a patient one.
Platforms to update immediately:
- Google Business Profile — post a quick update; this appears directly in search results
- Facebook / Instagram — brief, calm, no technical jargon
- WhatsApp Business — send a status if your customer base uses it
- Email — only if the outage is likely to extend beyond a few hours
When to Call a Professional (and What to Expect)
If you have worked through the steps above and cannot identify or fix the cause within 30–45 minutes, the problem is almost certainly one that requires someone with direct server access and technical expertise.
Signs you need professional help immediately:
- Your hosting provider cannot identify the cause
- Error logs show database corruption or a security breach
- The site has been defaced or is showing unfamiliar content (a sign of a hack)
- You have no recent backup and are afraid to make changes
- The outage is during a critical trading period (e.g., a product launch, sale event, or seasonal peak)
If the issue turns out to be a security incident rather than a technical fault, the approach is different — website security and malware removal is a separate process that goes beyond getting the site back online. A professional technician can typically diagnose the cause within 15–30 minutes and either fix it directly or give you a clear recovery path. You can see the full range of website support services for UK businesses if you want to understand what remote assistance covers.
How to Prevent the Next Outage
Fixing today's problem is only half the job. The other half is ensuring it happens far less often in future.
Set up free uptime monitoring. UptimeRobot's free plan checks your site every five minutes from multiple locations and sends you an immediate email or SMS alert the moment it detects downtime. One of the worst parts about website downtime is that you often do not know it is happening — by the time someone tells you, it might have been down for hours. Five minutes to set up UptimeRobot means you are always the first to know, not the last.
Enable auto-renewal for your domain and SSL — but verify that the payment card linked to each is current and not about to expire. Put a recurring calendar reminder to check this every six months. If keeping on top of these admin tasks feels like one more thing on an already full plate, virtual assistance is one way businesses delegate exactly this kind of ongoing maintenance.
Take weekly backups and store them off-server. Most UK hosts offer automated backups, but they store them on the same server your site runs on. If that server fails catastrophically, your backup fails with it. Use a plugin like UpdraftPlus (WordPress) to send automatic weekly backups to Google Drive or Dropbox.
Move off shared hosting if your site generates real revenue. Shared hosting is fine for a basic informational site. If you are processing orders, taking bookings, or running time-sensitive campaigns, a VPS (Virtual Private Server) or managed WordPress hosting plan gives you dedicated resources — your uptime is no longer affected by what the 200 other sites on your server are doing.
Keep your website content and structure in good shape. Outdated themes, neglected plugins, and poor site architecture all increase the risk of technical failures. If your site has accumulated design debt or content that has not been touched in years, website design and content support can help bring it to a more stable, maintainable standard.
Quick Reference: Website Down Checklist
Work through these eight checks in order. Most causes are identified within the first four.
1. Confirm it's a real outage — Visit isitdownrightnow.com and enter your domain. If it shows the site is up, your issue is local. (~1 minute)
2. Check your host's status page — Go to your hosting provider's status page or their Twitter/X account for live incident updates. (~2 minutes)
3. Check your domain expiry — Log in to your domain registrar dashboard and confirm your domain has not lapsed. (~2 minutes)
4. Check your SSL expiry — Open your hosting control panel and verify your SSL certificate is current and active. (~2 minutes)
5. Check for recent WordPress updates — Go to wp-admin → Updates, or review recent changes via FTP, to identify any plugin or theme that may have caused a conflict. (~5 minutes)
6. Review your error logs — In cPanel, open the Errors section and read the most recent entries at the bottom of the log file. (~5 minutes)
7. Check DNS propagation — Use dnschecker.org to confirm your domain is pointing to the correct server across global locations. (~2 minutes)
8. Communicate with your customers — Post a brief update on Google Business Profile and your social media channels so customers know you are aware and working on it. (~5 minutes)
Work through all eight and you will have either fixed the problem or pinpointed the cause — in under 25 minutes in most cases.