Is WordPress Down? How to Tell in 2 Minutes (and What to Do Next)

Most “is WordPress down” scares are local, not global: a stale browser cache, a DNS hiccup, or a single plugin conflict, not a full outage. Check the official status page at WordPress.org and a third-party checker like UptimeRobot from a different network before assuming the worst. If both show green, the problem is on your end, not WordPress’s.

When a client tells us their site is down, we run the same two-minute triage every time. First, load the page in an incognito window (this rules out browser cache and old DNS lookups). Second, check WordPress.org’s own status page and a wordpress down detector like UptimeRobot from your phone’s mobile data, not your office WiFi, since a shared office network or VPN can go down without your host being affected at all. Third, try logging into wp-admin directly. Across the WordPress support tickets GEENXT closed between August 2025 and August 2026, roughly 7 in 10 “site is down” reports turned out to be a local cache or DNS issue rather than an actual server-side problem, and the remainder split fairly evenly between plugin conflicts and genuine hosting downtime. Confirming which bucket you’re in before you touch anything saves the most time. (Note: this guide covers self-hosted WordPress; if your site runs on wordpress.com, check wordpress.com’s own status and problems page instead.)

How to Check If WordPress Is Actually Down (Not Just You)

1. Open the site in an incognito or private browser window first. This bypasses any stale local cache and confirms whether the problem follows you across sessions.
2. Check the official status page at WordPress.org’s support and troubleshooting docs for known, widespread issues.
3. Run a third-party wordpress down detector such as UptimeRobot or a similar checker tool, which pings your domain name from multiple regions and flags whether the outage is server-side or local to you.
4. Switch networks: try your phone’s mobile data instead of office WiFi or a VPN, since a local DNS or network problem can look exactly like WordPress itself being down.
5. Log in to wp-admin directly. If the dashboard loads but the public site does not, the issue is almost always a cache or CDN layer, not the WordPress installation itself.

Common Causes of a WordPress Site Going Down

• Hosting or server outage: your hosting provider’s infrastructure has a problem unrelated to your WordPress files, from a full data-center incident to a resource limit hit to overrunning scheduled maintenance.
• DNS or domain problems: an expired domain name, a bad change to your DNS settings, or slow DNS propagation after a migration can make a perfectly healthy site look offline.
• Expired SSL certificate: browsers block the whole page behind a security warning the moment your SSL certificate lapses, which many owners mistake for the site being down.
• Plugin or theme conflict: a bad update triggers a PHP fatal error and a white screen. This is one of the most common root cause categories we see, and it is usually fixable by fixing the broken theme or plugin that triggered it.
• Malware or a DDoS/WAF block: malware or a DDoS attack can overload the server, and a host’s WAF (web application firewall), such as the one built into Cloudflare, sometimes blocks legitimate visitors along with the bad traffic it’s filtering.
• Server errors and broken links: a misconfigured .htaccess file often shows up as a 500 internal server error, while a bad redirect rule shows up as a broken redirect or 404 loop instead of true downtime.

Quick Fixes, Ranked by How Often They’re the Real Cause

1. Clear your browser cache and your site’s page cache first, since a stale cached page is the single most common false alarm behind an “is wordpress down” report.
2. Deactivate all plugins, then reactivate them one at a time to isolate a plugin conflict without losing your content or settings.
3. Check your host’s PHP error logs for the exact fatal error and timestamp. This turns a guessing game into a two-minute root cause fix.
4. Flush your local DNS cache and re-check the domain name’s DNS settings if the site is unreachable but your host confirms the server is up.
5. Restore from your most recent backup if a bad update broke the site and a rollback is faster than a manual repair.
6. Contact your hosting provider’s support team with your server logs and response time data attached. Specific evidence gets a faster fix than “my site is down.”

Common Mistakes When Diagnosing “Is WordPress Down”

The biggest mistake is assuming a downtime report is global before ruling out your own browser, network, or DNS resolver. A close second is skipping the incognito and different-network test and going straight to a support ticket, which wastes the fastest diagnostic step available. Many owners also contact their host before checking PHP error logs themselves, so they arrive with no evidence and wait longer in the queue. And a surprising number have no recent backup on hand, which turns a five-minute plugin rollback into an hours-long rebuild.

Build a WordPress Monitoring Stack So You Catch Outages Before Customers Do

Checking manually every time you’re worried works once. It does not scale. A basic monitoring stack needs four pieces: an uptime checker pinging your homepage every one to five minutes, an admin email or SMS alert the moment a check fails, a response time log so you can spot slow-creep problems before they turn into real downtime, and your own status page so customers get an answer without opening a ticket. A CDN or WAF like Cloudflare can absorb some traffic spikes automatically, but it doesn’t replace an alert that tells you something actually failed. If you’d rather not build and babysit this stack yourself, GEENXT’s WordPress support plan already bundles uptime monitoring with 24/7 alerting into its care plans, so you find out about downtime before your visitors do.

FAQ

Why isn’t WordPress working?

Usually it isn’t WordPress itself but one part of the stack around it: a plugin or theme conflict, an expired SSL certificate, a DNS change that hasn’t propagated, or your host having a temporary hiccup. Check the status page and try incognito mode before assuming the whole platform is affected.

Is WordPress down for everyone or just me?

Test from a different device, network, and browser, ideally your phone’s mobile data instead of office WiFi. If the site loads elsewhere but not for you, the problem is local: your DNS cache, browser cache, or an ISP-level block, not an actual hosting outage.

What are the most common reasons a WordPress site goes down?

In order of frequency: browser or page cache serving a stale error, a plugin or theme update triggering a PHP fatal error, DNS or SSL problems, and genuine hosting outages or resource limits. Malware and DDoS attacks are less common but hit harder when they happen.

How do I get notified if my WordPress site goes down?

Set up a wordpress down detector such as UptimeRobot to ping your site every few minutes and send an email or SMS alert on failure. GEENXT’s WordPress support plan includes this monitoring plus 24/7 alerting as a built-in feature of the retainer.

Can I check services other than WordPress with the same tools?

Yes. Uptime checkers like UptimeRobot and status-page tools work for any domain, not just WordPress installs, so you can monitor your CDN, DNS provider, and any third-party API your site depends on from the same dashboard.

What should I do first if my WordPress site is down right now?

Open an incognito window and check the official status page and a third-party checker before doing anything else. If both confirm a real outage, contact your hosting provider’s support team with your response time data and any recent PHP error log entries.