My Website Appears to Be Down: Safe Checks Before You Contact Support
My Website Appears to Be Down: Safe Checks Before You Contact Support
A page that will not load does not always mean the entire website is offline. The cause may be limited to one browser, device, internet provider, page, or geographic area. It may also be a temporary hosting, DNS, SSL, WordPress, or Cloudflare problem. The checks below help separate those possibilities without changing the site.
1. Record exactly what you see
Do not repeatedly refresh or start changing settings. Note the affected URL, the time and time zone, and the exact message or status code. Take a full-screen screenshot. If a Cloudflare error page appears, include the Ray ID shown near the bottom; Cloudflare identifies the CF-RAY value as useful for correlating a request during troubleshooting.[1]
Examples worth copying exactly include 404, 500, 502, 521, 522, DNS_PROBE_FINISHED_NXDOMAIN, certificate warnings, or a blank page. Also note whether the home page, one internal page, or the WordPress admin area is affected.
2. Check whether the issue is local
Open the URL in a private/incognito window, then try another supported browser. If possible, test on a phone using mobile data rather than the same Wi-Fi. Ask one colleague in another location to test the same URL. These comparisons do not fix the issue, but they reveal whether it follows one browser, one network, or everyone.
If the site works elsewhere, restart the affected browser and device. You may then follow the separate cache-and-cookie article. Do not bypass a browser certificate warning or enter credentials on a page whose identity cannot be verified.
3. Check service status
If the site uses Cloudflare, review the official Cloudflare Status page for a current incident.[2] Your hosting provider, CRM, form provider, or managed WordPress host may have a separate status page. A green global status does not prove that your individual origin server is healthy, but an active incident can explain a broad outage.
4. Look for recent changes
Tell support about changes made shortly before the problem began: a domain or DNS edit, plugin or theme update, WordPress core update, hosting migration, SSL renewal, firewall rule, redirect, or deployment. Do not roll back, delete a DNS record, disable security, or deactivate plugins on a live site unless an authorized administrator has a backup and a tested recovery plan.
WordPress documents that a failed update can leave a site showing “Briefly unavailable for scheduled maintenance.” Its troubleshooting guidance also recommends backing up WordPress files and the database before upgrades or repair work.[3] Those are administrator tasks, not first-response client steps.
5. Prepare a useful support report
Send support:
- the exact affected URL;
- when the issue started, including time zone;
- the exact error and a screenshot;
- the devices, browsers, and networks tested;
- whether private browsing changed the result;
- whether all pages or only one page fail;
- any recent site, hosting, SSL, plugin, or DNS changes; and
- the Cloudflare Ray ID, if displayed.
For visual problems, failed resources, or slow loads, Cloudflare says a HAR file can capture the browser’s request sequence and timing.[1] Only create one if support requests it. HAR files can contain sensitive data, so reproduce the problem in a private window, avoid entering passwords or payment details, and review or sanitize the file before sharing.
When to escalate urgently
Contact support immediately if the outage affects checkout, lead capture, client login, or the entire public site; if browsers show a security or certificate warning; if the site redirects to an unfamiliar domain; or if you suspect compromise. Stop testing transactions after one clearly labeled test so you do not create duplicate orders or leads.
A strong first report lets support distinguish browser, DNS, Cloudflare, hosting, and application issues quickly, without risky guesswork.