Website Downtime Checklist: What a Small Business Should Check Before Calling the Host

A practical website downtime checklist to help small businesses distinguish DNS, hosting, SSL, WordPress and local network problems. For WordPress-specific outages, also use our WordPress website not loading guide.

For more specific faults, see Cloudflare Error 522/524 troubleshooting, WordPress update recovery and website technical support.

First confirm the scope

When a website will not load, avoid changing settings immediately. Check whether the problem affects everyone or only one device, network or location. Try mobile data as well as office Wi-Fi and use a private browser. If the site works elsewhere, the web server may be fine and the issue could be local DNS, filtering or caching.

Check the exact error

A timeout, DNS error, SSL warning, 500 error and WordPress critical-error screen point to different layers. Record the message and time before refreshing repeatedly. Screenshots and server logs are more useful than the general statement that the site was down.

Verify domain and DNS

Confirm the domain has not expired and that its nameservers still point where expected. Recent DNS changes are especially relevant. If the site shows an old server or works intermittently, read the DNS propagation guide before making another change.

Check hosting status and resource limits

Look for provider incidents, suspended services, storage exhaustion or resource limits. A hosting dashboard showing online does not prove WordPress is healthy, but it can quickly reveal account-level problems. Our website-down-but-hosting-online guide covers the next layer.

Separate SSL from availability

A certificate warning means the server may be reachable even though the browser does not trust the HTTPS connection. Check expiry, hostname coverage and certificate provisioning rather than rebuilding WordPress. See SSL certificate troubleshooting.

Investigate WordPress errors methodically

A 500 error or critical-error message may follow a plugin update, PHP change or exhausted memory. Review what changed recently and use logs where available. Avoid disabling random components on a live site without a recovery point. The critical error guide provides a structured process.

Check Cloudflare separately

If Cloudflare is in front of the site, its error code can identify an origin communication issue. A 522 or 524 does not mean the domain is necessarily misconfigured. Use the Cloudflare error guide to distinguish connection and timeout symptoms.

Do not forget business email

If both website and email fail at the same time, DNS or domain changes deserve immediate attention. If only the website is down while Microsoft 365 continues working, that narrows the scope. Avoid replacing the whole DNS zone during a website incident.

Escalate with useful evidence

When contacting support, provide the URL, exact error, start time, networks tested and any recent changes. TempWebz offers website technical support for WordPress, hosting and DNS incidents where the cause is unclear and the priority is restoring service without unnecessary changes.

Practical questions to ask before making changes

Before changing a live business website, write down what you expect the change to achieve and how you will verify it. Know what can be rolled back, where the latest recovery copy is stored and which customer-facing functions need retesting. This simple discipline prevents several unrelated changes being mixed together and makes technical support far more efficient if escalation is needed.

Also consider whether the problem is genuinely inside WordPress. Domain registration, DNS, hosting, SSL, email delivery, local networks and third-party services can all produce symptoms that appear on the website. Checking the right layer first protects a working site from unnecessary modifications.

What should be documented afterwards?

Keep a short record of the date, the original symptom or objective, what was changed and the result. For infrastructure work, note the provider and account that owns the setting. For WordPress work, record significant plugin, theme or PHP changes. Documentation does not need to be complicated; it needs to be understandable to the next person who has to diagnose the site under time pressure.

How to handle website downtime diagnosis without creating a second problem

The safest starting point is to separate observation from action. Record the current behaviour, the relevant account or provider, and any recent change that could be connected. Then decide what evidence would confirm the cause before altering a live setting. Small-business systems overlap: WordPress, hosting, DNS, SSL and email can produce similar symptoms even though the repair belongs in a completely different layer.

Make one meaningful change at a time and keep a recovery path. For WordPress work that normally means a current backup and, for higher-risk work, a staging test. For DNS or email changes it means preserving the existing records before editing them. For hosting changes it means keeping the previous environment available until the replacement has been tested. The objective is not to avoid change. It is to make every change explainable and reversible.

What should be verified afterwards?

Do not stop at the technical control panel. Test the service the way a customer or staff member uses it. Open important pages on a phone and desktop, follow navigation, submit a genuine form, confirm the message arrives, and check any login or download that matters. If email or DNS was involved, test from an unrelated external account. If hosting or PHP changed, review server logs as well as visible pages. A green status indicator proves only what that particular tool measured.

Keep a short change record containing the date, original objective, component changed and result of the verification. This becomes valuable when a problem appears later. Instead of guessing what might have happened, the next person can see what changed and what was known to work immediately afterwards.

When deeper investigation is justified

Escalation is sensible when the same fault returns, the cause crosses several providers, business-critical data is at risk, or the next diagnostic step would require an irreversible change. Repeatedly toggling plugins, rewriting DNS or replacing configuration without evidence can turn a contained fault into a wider outage. Preserve logs and backups, document what has already been tested and avoid making several speculative changes at once.

For a small business, the strongest technical outcome is usually uneventful: the service works, ownership is clear, recovery is documented and future changes can be made without rediscovering the entire environment. That principle matters more than chasing a perfect dashboard score.

A simple review routine for the next 30 days

After the immediate work is complete, schedule one follow-up review rather than assuming the result will remain correct indefinitely. Confirm that the original symptom has not returned, backups have continued, no unexpected administrator or infrastructure changes have appeared, and the customer-facing functions still work. If the work involved email, repeat an external send-and-receive test. If it involved the website, check a representative mobile page and submit a form. If it involved hosting or DNS, confirm the documented provider and records still match the live configuration.

This follow-up is also the right time to remove temporary access, old test accounts, unused staging copies or short-term workarounds created during troubleshooting. Temporary fixes have a habit of becoming permanent infrastructure when nobody records why they exist. Removing them deliberately keeps the environment easier to understand and reduces future maintenance.

Finally, update the business’s technical record with the current domain registrar, DNS provider, host, email platform and recovery contacts. That information may feel administrative while everything works, but during an outage it can save more time than another optimisation plugin. Good technical management is not about making a website complicated. It is about keeping the important parts known, testable and recoverable.

As a final control, confirm ownership. The business should know who can approve changes, who holds administrator access and where recovery information is kept. Systems become fragile when they depend on undocumented knowledge held by one person. Clear ownership and a tested fallback make future support faster and reduce rushed changes during an incident.