On This Page
Key takeaways
- Confirm the outage is real before troubleshooting, using a different network and an independent uptime checker.
- Most South African downtime traces back to expired domains, suspended hosting, or DNS issues, not a cyberattack.
- Keep customers informed through your Google Business Profile and social accounts while the fix is underway.
- Uptime monitoring and auto-renewal on domains and hosting prevent the most common causes of downtime before they happen.
Confirm the Website Is Actually Down
A page that will not load on your phone is not proof the whole site is down. Before you panic or call your developer, rule out your own connection and device first. A few quick checks take two minutes and can save you an awkward, unnecessary call.
This matters because the fix changes completely depending on where the fault sits. A local network issue needs nothing more than a router restart, while a genuine server outage needs your host involved. Work through the checks below in order so you know which situation you are actually in.
Check From a Different Network and Device
Switch from Wi-Fi to mobile data, or ask someone on a different network entirely to load the site. If the page opens for them, the fault most likely sits with your router, your ISP, or a stale DNS entry cached on your own machine. A mobile data test is the fastest way to isolate the problem before you contact anyone else.
Use an Independent Uptime Checker
An independent uptime checker pings your site from servers outside South Africa and shows if the outage is affecting every visitor or just you. This separates a genuine outage from a local hiccup within seconds, with no login required. A global uptime check takes the guesswork out before you escalate to your host or developer.
Rule Out Load Shedding and Local Power Problems
If your website runs on a server at your own premises rather than through a hosting provider, a power outage at your office takes the site down along with everything else. Check your load shedding schedule and your router's power supply before assuming a server-side fault. Most small business websites are hosted off-site, so this points to your in-house setup rather than your host, when it applies.
The Most Common Reasons a South African Website Goes Down
Most downtime is not mysterious once you know where to look. A handful of causes account for the bulk of outages small business owners report, and nearly all of them trace back to hosting, domains, or power rather than anything more dramatic.
Knowing which category your outage falls into tells you who to call and what to say to them. It also stops you wasting an afternoon rebuilding pages that were never actually broken.
Hosting and Server Problems
Shared hosting plans can overload during a traffic spike or scheduled maintenance window, and the server simply stops responding to requests. A hosting outage usually shows up as a timeout or a generic error page rather than anything resembling your site's actual design. Your host's status page or support line is the first place to check, not your website's code.
Domain Expiry and DNS Issues
A domain that lapses because the renewal invoice went to an old email address takes your entire site offline overnight, with no warning on the site itself. Domain expiry is one of the most preventable causes of downtime in South Africa, where the registrar and the hosting provider are often two completely separate companies. DNS changes that have not fully propagated yet can also make a site load for some visitors and not others at the same time.
Load Shedding and Its Knock-On Effects
Even websites hosted in the cloud can go down when load shedding knocks out your office internet, your point of sale system, or the connection your developer needs to access the server and fix a problem. This chain reaction is covered in more detail in how load shedding affects performance. Power stage timing is worth checking against your outage log before assuming the cause is something more serious.
The Step-by-Step Troubleshooting Checklist
Once you have confirmed the site is genuinely down, work through these checks in order instead of jumping straight to the most dramatic explanation. Most outages are resolved somewhere in the first three steps.
Keep a short note of what you find at each step. Your host or developer will ask exactly these questions, and having the answers ready cuts the time to a fix considerably.
Check Domain and DNS Status
Look up your domain's expiry date through a WHOIS lookup and confirm the nameservers still point to your hosting provider. A domain that expired yesterday behaves exactly like a broken website to every visitor who tries to reach it. A WHOIS lookup takes thirty seconds and rules out the single most preventable cause of downtime.
Check Your Hosting Dashboard and Server Status
Log into your hosting control panel and look for a suspension notice, an unpaid invoice flag, or a resource limit warning. Many hosts also publish a live server status page that sits separate from the control panel and updates in real time. If the account is in good standing and the server shows green, the fault is more likely DNS or your own local network.
Check Search Console for Server Errors
Google Search Console logs crawl errors whenever Google's own bots cannot reach your site, which confirms the outage from a source outside your own network. The Page Indexing report shows a spike in server errors around the exact time your site went down. Once the site is back up, check the same report again before resubmitting anything to Google.
What to Do While You Wait for a Fix
A website outage is a communication problem as much as a technical one. Customers who cannot reach your site will look for you elsewhere within minutes, especially if a competitor's number is the next search result.
Use the downtime window to protect the channels you still control. None of this fixes the server, but it keeps customers from assuming you have closed down.
Update Your Google Business Profile and Social Accounts
Post a short update telling customers you are aware of the issue and still trading as normal. A status update keeps your phone number and trading hours visible even while the website itself is offline. If you have not logged into the profile in months, confirm it is still verified using Google's profile verification guidance.
Have a Holding Message Ready to Send
A one-line WhatsApp broadcast or email to recent enquiries buys goodwill while the technical fix is underway. Customers forgive downtime far more easily when they hear about it from you first rather than discovering it themselves. Keep a template message saved somewhere so you are not drafting one under pressure.
Log Everything for Your Developer or Host
Note the time the site went down, exactly what the error page said, and which checks from this list you have already run. This saves a round of back-and-forth once you are actually on the phone with support. A clear incident timeline means they spend less time asking questions and more time fixing the fault.
When to Call In Professional Help
Some outages you can fix yourself in minutes. Others need a developer, a hosting support ticket, or someone who actually understands your site's setup, and knowing the difference saves hours of trial and error.
If you have worked through the checklist above and the cause still is not obvious, it is time to bring someone in rather than keep guessing.
Signs the Problem Is Beyond a Quick Fix
A server status page showing all green, a domain that is not expired, and a site that is still down point to something more specific, like a broken plugin update, a misconfigured SSL certificate, or a corrupted database. These causes usually need someone with direct server access to diagnose properly. Repeated short outages over several days are also a sign of an underlying capacity problem, not a one-off glitch.
What to Tell Your Developer or Agency
Hand over the incident timeline you kept in the previous step, along with exactly what each check in this list showed. The faster they can rule things out, the faster they get to the actual cause. A clear handover usually means the difference between a ten-minute fix and a half-day of back-and-forth guessing.
Choosing Between DIY and a Maintenance Plan
If this is the second or third time this year that you have run through this checklist, the cheaper option is usually ongoing support rather than another one-off fix. Ongoing technical SEO support covers exactly this kind of monitoring and response. A maintenance retainer, outlined on the pricing page, is built for businesses that would rather not be the ones running this checklist at all.
Preventing the Next Outage
Downtime you plan for costs far less than downtime that catches you off guard. Once the current outage is resolved, use it as the trigger to put a few safeguards in place.
None of this requires a large budget. It mostly requires consistency and one afternoon to set it up properly.
Set Up Independent Uptime Monitoring
A monitoring tool that checks your site every few minutes and messages you the moment it goes down means you hear about problems before your customers do. Uptime monitoring is cheap and takes minutes to configure for most hosting setups. Waiting for a customer complaint is the slowest possible way to find out your site is offline.
Keep Domain and Hosting Renewals on Autopilot
Set domain and hosting renewals to auto-renew against a card that will not expire, and point the renewal emails to an inbox someone actually checks weekly. Auto-renewal removes the single most common and most avoidable cause of downtime in South Africa. A review of technical SEO basics is a good moment to confirm this is already set up correctly.
Resubmit Your Sitemap and Schedule a Regular Audit
Once the site is confirmed stable, resubmit your XML sitemap in Search Console so Google recrawls your pages sooner rather than later. A regular technical audit catches expiring certificates and failing backups before either one causes the next outage. Treating this as routine maintenance rather than an emergency is what keeps the next outage from happening at all.
Frequently asked questions
How do I know if my website is down for everyone or just me?
Check it from a different network, such as mobile data, and run it through a third-party uptime checker. If it loads elsewhere but not for you, the fault is with your own connection or device, not your site.
Why did my website suddenly disappear with no warning?
The two most common causes are an expired domain renewal and a hosting account suspended for an unpaid invoice. Check your domain's WHOIS record and your hosting dashboard before assuming anything more serious.
Can load shedding take my website offline?
Only if your site is hosted on a server at your own premises, since cloud hosting keeps running during local power cuts. Load shedding is more likely to affect your ability to manage or fix the site than to cause the outage itself.
How long should I wait before contacting my host or developer?
If the checklist above does not resolve it within fifteen minutes, contact support with your incident timeline ready. The faster they have the details, the faster they can diagnose the fault.
Should I tell customers my website is down?
Yes, a short update on your Google Business Profile and social accounts keeps you reachable and protects trust while the fix is underway. Silence during an outage tends to cost more goodwill than the outage itself.