Back to All Articles
WordPressOct 30, 20267 min read

WordPress HTTP Error Codes Explained: 4xx vs 5xx and What Monitoring Can Catch

WordPress HTTP errors are not all created equal. A 404 means a page is missing. A 500 means PHP crashed. A 503 means your server is overwhelmed. Here is what every error code means and which ones external monitoring catches automatically.

P
Prabin Jha
Founder & Lead Architect
LinkedIn

Key Takeaways (BLUF)

Bottom Line Up Front: WordPress HTTP error codes fall into two main categories. 4xx errors (400–499) are client-side errors — usually a missing page, a bad request, or an authentication failure. 5xx errors (500–599) are server-side errors — your server or WordPress itself failed to process the request. External monitoring tools like WakeMetric detect 5xx errors (and unreachable sites) as downtime events and alert you. 4xx errors on individual pages are generally not monitored as site-wide outages unless the entire site returns a 4xx.

4xx WordPress Errors: Client-Side and Usually Not a Site-Wide Outage

4xx errors indicate the problem is with the request, not the server. The server is running correctly — it just cannot fulfill this specific request.

Error CodeNameCommon Cause in WordPressMonitoring Classification
400Bad RequestMalformed form submission, invalid cookie, corrupted query stringNot a site-wide outage — page-level issue
401UnauthorizedAccessing a protected resource without valid credentialsNot a site-wide outage — authentication issue
403ForbiddenFile permission error, .htaccess restriction, blocked by security pluginCan be site-wide if entire site is blocked — WakeMetric detects this
404Not FoundDeleted page, changed permalink structure, missing attachment fileNot a site-wide outage — individual page missing
429Too Many RequestsRate limiting by security plugin, host, or CloudflareUsually page-level — monitoring depends on whether homepage is affected

5xx WordPress Errors: Server-Side and Always Monitored as Downtime

5xx errors indicate the server encountered a problem and could not complete the request. For external uptime monitoring purposes, any 5xx response from your homepage URL is classified as a downtime event.

Error CodeNameCommon Cause in WordPressWakeMetric Detection
500Internal Server ErrorPHP fatal error, memory limit exceeded, .htaccess syntax error✅ Detected as downtime — alert sent
502Bad GatewayPHP-FPM not responding, upstream proxy error✅ Detected as downtime — alert sent
503Service UnavailableServer overloaded, WordPress maintenance mode, PHP-FPM pool exhausted✅ Detected as downtime — alert sent
504Gateway TimeoutPHP script exceeded execution time limit, slow database query✅ Detected as downtime — alert sent
521Web Server Down (Cloudflare)Origin server not accepting connections from Cloudflare✅ Detected as downtime — alert sent
522Connection Timed Out (Cloudflare)Cloudflare could not reach origin server within timeout✅ Detected as downtime — alert sent
524A Timeout Occurred (Cloudflare)Origin server responded but PHP timed out before completing✅ Detected as downtime — alert sent

What "Site Unreachable" Means in WakeMetric Monitoring

Beyond HTTP error codes, WakeMetric also detects when your site returns no response at all — known as a connection timeout or connection refused. This occurs when:

  • Your server is completely offline (hardware failure, power issue, hosting provider outage)
  • Your domain's DNS records no longer point to your server (domain expired, DNS misconfiguration)
  • Your server's firewall is blocking all incoming HTTP/HTTPS connections
  • Your IP address has changed but DNS has not propagated to the new address

Which WordPress Errors WakeMetric Monitors Automatically

WakeMetric's free Community Plan monitors your WordPress site's primary URL. Any response other than a 2xx (success) response — including all 5xx errors and connection failures — is classified as a downtime event. 4xx errors are only classified as downtime if the homepage itself returns a 4xx (such as a 403 Forbidden blocking the entire site).

Frequently Asked Questions

My site has a lot of 404 errors. Will WakeMetric alert me about those?

WakeMetric monitors your primary site URL (your homepage or whichever URL you connected). If your homepage returns 200 OK, WakeMetric will not alert you about 404 errors on individual pages — those are content issues, not site outages. To audit and fix 404 errors across your WordPress site, use a plugin like Redirection or a Google Search Console crawl report.

What is a WordPress 521 error and why does it appear?

HTTP 521 is a Cloudflare-specific error that means Cloudflare successfully received the request, attempted to connect to your origin server, and the connection was actively refused. This is distinct from a 522 (connection timeout) where Cloudflare tried to connect but got no response. A 521 usually means your origin server's web server (Nginx or Apache) is stopped or crashed, or a firewall rule is blocking Cloudflare's IP addresses from reaching your server.

Does WakeMetric monitor SSL certificate errors as a separate category from HTTP errors?

Yes. WakeMetric monitors SSL certificate validity and expiry separately from HTTP response codes. An expired SSL certificate typically causes browsers to refuse to connect at all (rather than returning an HTTP error code), which WakeMetric detects as site unreachable. WakeMetric also provides advance SSL expiry alerts at 30, 14, and 7 days before the certificate expires — allowing you to renew before the site becomes unreachable.

Conclusion

Understanding which HTTP errors indicate a site-wide WordPress outage versus a page-level issue helps you prioritize monitoring and response. Any 5xx error or unreachable response from your homepage is an outage that requires immediate attention — and WakeMetric's external monitoring catches all of them. Install the free WakeMetric plugin and receive an alert the moment any 5xx error or connection failure hits your WordPress site.

Ready to Upgrade from UptimeRobot?

Migrate in under 60 seconds. Get 15-second checks across 450+ global locations with zero false alerts.