TL;DR:
- WordPress downtime results from failures across six layers between visitors and the site, often caused by configuration issues or plugin conflicts. Diagnosing issues top-down—checking network, DNS, SSL, server, CDN, then application—saves time and prevents unnecessary edits. When problems persist beyond 30 minutes or involve security warnings, professional support becomes essential to avoid further damage.
WordPress downtime is defined as the state in which your site is unreachable due to failure in one or more of six distinct layers between your visitors and the WordPress application itself. The phrase “why is my WordPress down” covers everything from a misconfigured DNS record to a rogue plugin update, and the fastest route to recovery is knowing which layer has failed before you start making changes. Most downtime traces back to logical, identifiable causes such as plugin conflicts, expired SSL certificates, or hosting outages rather than any mysterious WordPress failure. This guide walks you through a structured diagnostic process so you can restore your site quickly and confidently.
Why is my WordPress down? How to confirm the outage first
Before you touch a single file, confirm that the outage is real and understand its scope. What looks like a site-wide failure is sometimes a local network issue, a browser cache problem, or a single page returning an error while the rest of the site runs fine.
Follow this sequence in the first ten minutes:
- Test from a different network. Load your site on mobile data, not your office Wi-Fi. If it loads on mobile, the problem is your local network or ISP, not WordPress.
- Test from a different device. Rule out browser extensions, cached data, or device-specific settings by trying a second machine or an incognito window.
- Use an external status checker. Tools such as Down For Everyone Or Just Me (downforeveryoneorjustme.com) or IsItDownRightNow confirm whether the outage is global or local.
- Check both the frontend and wp-admin. If your public site is down but wp-admin loads, the fault is likely a theme or page-builder conflict. If both are down, the issue sits deeper in the stack.
- Record the exact error message. HTTP status codes direct troubleshooting: a 500 error points to PHP issues, a 503 suggests server overload, and a database error message means MySQL connectivity has failed.
- Check your hosting control panel. Log into cPanel, Kinsta, WP Engine, or your host’s dashboard to see whether the server itself is reporting an incident or scheduled maintenance.
A practical 15-minute diagnostic flow is widely recommended: spend the first two minutes confirming scope, the next five identifying the symptom type, then move to layer-by-layer diagnosis. This discipline stops you from wasting time editing wp-config.php when the real problem is a Cloudflare firewall rule.
Pro Tip: Keep a simple troubleshooting checklist saved in your notes app or a shared team document. Documenting each finding as you go prevents you from repeating steps and gives your hosting provider or a support team the context they need to help you faster.
What are the six layers that cause WordPress downtime?
Multiple layers sit between a visitor and your WordPress site, and each produces distinct symptoms. Working through them top-down is the most efficient diagnostic approach.
| Layer | Typical symptom | Common cause |
|---|---|---|
| 1. Client network | Site appears down only for you | Local DNS cache, VPN, ISP outage |
| 2. DNS | “Server not found” in all browsers | Expired domain, misconfigured records, propagation delay |
| 3. SSL/TLS | Browser security warning, padlock error | Expired certificate, mismatched domain on cert |
| 4. Origin server | Blank page or timeout for all visitors | Hosting outage, firewall block, IP address change |
| 5. CDN/proxy | Branded error page (e.g. Cloudflare 5xx) | CDN misconfiguration, origin unreachable via proxy |
| 6. WordPress app | White screen of death, database error, maintenance message | Plugin conflict, PHP fatal error, corrupted core files |
Layer 2 DNS problems are particularly deceptive because a domain that has expired or had its nameservers changed will appear broken to every visitor globally, yet your hosting server is running perfectly. Always check your domain registrar’s control panel alongside your hosting dashboard. Expired SSL certificates cause browser security warnings that most visitors will not click through, making Layer 3 failures functionally identical to a full outage even though WordPress itself is operational. Cloudflare 5xx errors at Layer 5 display branded error pages, which is a clear signal that the fault lies in the proxy configuration or the connection between Cloudflare and your origin server, not in WordPress.
Pro Tip: Work top-down through the layers. Confirming that DNS resolves correctly before you start editing WordPress files saves significant time and prevents unnecessary changes to a working application.
How to fix common WordPress application errors
Once you have ruled out Layers 1 through 5, you are dealing with a WordPress application fault. These are the most frequent reasons for WordPress site not working, and most are resolvable without specialist infrastructure access.
Error establishing a database connection
WordPress reads database credentials from wp-config.php and opens a MySQL connection on every page request. When that connection fails, the entire site goes down. Open wp-config.php via SFTP or your hosting file manager and verify that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match the credentials shown in your hosting control panel. If credentials are correct but the error persists, the MySQL service itself may be down, which requires a hosting support ticket.
Plugin and theme conflicts
Plugin conflicts are the single most common cause of WordPress application downtime. Deactivate all plugins by renaming the plugins folder to something like “plugins_disabled” via SFTP when wp-admin is inaccessible. If the site recovers, rename the folder back and reactivate plugins one by one to identify the offending item. Apply the same logic to themes by switching to a default WordPress theme such as Twenty Twenty-Four via the database or filesystem.
Stuck maintenance mode
Deleting the hidden .maintenance file from the root of your WordPress installation restores a site that is stuck displaying a maintenance message after an interrupted update. The file is created automatically during updates and should be removed by WordPress on completion. When an update is interrupted, it is left behind indefinitely. After deleting it, revisit your WordPress update screens to complete any unfinished updates in sequence to restore full site health.
PHP fatal errors and corrupted core files
- Enable WP_DEBUG and WP_DEBUG_LOG in wp-config.php to write PHP errors to a log file rather than displaying them on screen.
- Keep WP_DEBUG_DISPLAY set to false during a live outage. Exposing WP_DEBUG_DISPLAY publicly risks revealing sensitive file paths and configuration data to anyone who visits the site.
- Replace corrupted WordPress core files by downloading a fresh copy of WordPress from WordPress.org and overwriting the wp-admin and wp-includes directories via SFTP, leaving wp-content and wp-config.php untouched.
- Check your .htaccess file for malformed rewrite rules by renaming it temporarily. WordPress will regenerate a clean version when you visit Settings > Permalinks.
Pro Tip: If wp-admin is completely inaccessible, use SFTP or your hosting file manager for all changes. Attempting to force access through repeated login attempts or database edits without SFTP access often compounds the problem.
When should you escalate to professional WordPress support?
DIY troubleshooting has clear limits. Knowing when to stop and call for help is as important as knowing how to diagnose. The real cost of WordPress downtime for a business extends well beyond the technical inconvenience, particularly when revenue, client trust, or data integrity are at risk.
Escalate immediately if you encounter any of the following:
- The outage is unresolved after 30 minutes. Prolonged outages or signs of malware require expert intervention to prevent further damage and data loss. Every additional minute of troubleshooting without progress increases the risk of compounding the fault.
- Browser security warnings appear for visitors. A “Deceptive site ahead” or malware warning from Google Safe Browsing indicates a security breach, not a configuration error. This requires immediate professional security review.
- You suspect domain hijacking or unauthorised file changes. Unexpected redirects, unfamiliar admin users, or modified core files are signs of a compromise that go beyond standard troubleshooting.
- Your hosting provider confirms the server is healthy but the site remains down. This narrows the fault to the WordPress application or a security issue, both of which benefit from specialist diagnosis.
- You are making repeated changes without a clear plan. Invasive or repeated edits to wp-config.php, the database, or core files without full understanding of the consequences can turn a recoverable outage into a data loss event.
For agencies managing WordPress sites on behalf of clients, the calculus is straightforward. Every hour spent troubleshooting a client site is an hour not spent on the creative or strategic work your agency was hired to do. A professional WordPress emergency support service provides guaranteed recovery times and takes the operational burden off your team entirely.
Key takeaways
WordPress downtime is caused by failures at one of six identifiable stack layers, and the fastest recovery always comes from diagnosing the correct layer before making any changes.
| Point | Details |
|---|---|
| Confirm scope first | Test from a different network and device before touching any files or settings. |
| Work top-down through layers | DNS, SSL, and CDN faults mimic WordPress errors but require completely different fixes. |
| Database errors need credential checks | Verify wp-config.php credentials against your hosting control panel before assuming server failure. |
| Plugin conflicts are the top app cause | Rename the plugins folder via SFTP to isolate conflicts when wp-admin is inaccessible. |
| Escalate after 30 minutes | Unresolved outages or security warnings require professional support to prevent further damage. |
The layer model changed how we approach every outage
When a client site goes down, the instinct is to open WordPress and start clicking. I have seen experienced developers spend 45 minutes editing wp-config.php only to discover the domain had simply expired. The six-layer model is not a theoretical framework. It is a practical discipline that stops you from wasting time in the wrong place.
In my experience, plugin conflicts account for the majority of WordPress application outages, but server and infrastructure issues account for a surprisingly large share of the cases that feel most urgent. The ones that come in on a Sunday evening, the ones where the client is already on the phone, those are often DNS or SSL issues that take five minutes to fix once you look in the right place.
The other mistake I see regularly is enabling WP_DEBUG_DISPLAY on a live site during an outage. The intention is good but the execution exposes sensitive configuration data to every visitor. Log to file, keep the display off, and read the log via SFTP. That single habit prevents a troubleshooting session from creating a secondary security problem.
Backups and a documented recovery plan are not optional extras. They are the difference between a 20-minute recovery and a four-hour rebuild. If you are managing WordPress sites without a tested backup and restore process, that is the first thing to fix before the next outage arrives.
— Marcel
Let Wpcto handle WordPress downtime for your agency
If you are an agency managing WordPress sites for clients, every outage you handle in-house is time and revenue you are not recovering. Wpcto provides specialist WordPress maintenance and support for design, brand, and digital agencies across the UK, covering emergency support, security monitoring, plugin and theme management, and hosting oversight. We sit behind your agency invisibly so your clients stay yours and your team stays focused on the work that actually grows your business.
Want to see how much uncaptured revenue is sitting in your existing WordPress client base? The WordPress Profit Calculator gives you a clear answer in under 90 seconds. It is free, takes no setup, and the result is usually surprising.
FAQ
Why is my WordPress site down but hosting is fine?
If your hosting server is confirmed healthy but your site is unreachable, the fault is most likely within the WordPress application itself. Common causes include a plugin conflict, a PHP fatal error, a database connection failure, or a corrupted .htaccess file.
How do I fix a WordPress database connection error?
Open wp-config.php via SFTP and verify that DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST match the credentials in your hosting control panel exactly. If credentials are correct and the error persists, the MySQL service may be down and requires a hosting support ticket.
What does the WordPress white screen of death mean?
The white screen of death is typically caused by a PHP fatal error or a plugin and theme conflict that prevents WordPress from rendering any output. Deactivating all plugins by renaming the plugins folder via SFTP is the fastest first step to isolate the cause.
How long should I troubleshoot before calling for help?
If the outage is unresolved after 30 minutes, or if you see browser security warnings or signs of unauthorised file changes, escalate to your hosting provider or a professional WordPress support service immediately to prevent further damage.
Can a CDN cause my WordPress site to appear down?
Yes. Cloudflare and other CDN providers display branded 5xx error pages when they cannot reach your origin server, which visitors experience as a full site outage even though WordPress itself may be running. Check your CDN dashboard and temporarily pause the CDN to confirm whether it is the source of the fault.