WordPress powers 43% of all websites on the internet. Most run on shared hosting, depend on dozens of plugins, and are updated manually — creating ideal conditions for undetected outages.
When WordPress crashes, the typical scenario is: "Error Establishing a Database Connection" stays on your site for 3 hours until a client messages you on Telegram. External uptime monitoring would have caught this in 30 seconds.
Why WordPress Goes Down
1. Hosting Problems
Shared hosting is the primary cause of downtime. When a neighboring server account experiences a traffic spike, your site slows down or crashes. Managed WordPress hosting (WP Engine, Kinsta, Cloudways) solves this but costs more.
2. Plugin Conflicts
Updating one plugin can break another. WordPress with 20+ plugins means 20 points of failure. Auto-updates increase risk: a plugin updates overnight, your site crashes, and you find out in the morning from a client.
3. PHP Fatal Error
Memory exhaustion (Allowed memory size exhausted) or incompatible PHP code after updates. Your site displays "white screen of death" or 500 Internal Server Error. The server returns 500, but the process stays alive — you need a keyword check to detect it.
4. Database Connection Failure
"Error Establishing a Database Connection" is one of the most common WordPress errors. MySQL/MariaDB goes down, connection limits are exceeded, or credentials change. The server returns HTTP 500 or even 200 with an error page.
5. SSL Certificate Expiry
Let's Encrypt auto-renewal depends on a cron job that can silently stop working. Or your hosting provider forgets to renew the certificate. The result: browsers block access, showing "Not Secure". SSL monitoring warns you 30 days in advance.
What to Monitor on WordPress
Homepage (HTTP): GET https://yoursite.com — basic availability check. Keyword check on your brand name or heading — catches cases where the server returns 200 with an error page.
REST API (HTTP): GET https://yoursite.com/wp-json/wp/v2 — verifies WordPress backend works, bypassing any frontend cache.
Admin Login (HTTP): GET https://yoursite.com/wp-login.php — checks admin panel accessibility. If login is down while frontend works, suspect PHP crash or plugin conflict in admin area.
SSL (TLS Check): monitor certificate expiry, chain validity. Alert 30 days before expiry.
DNS (DNS Check): DNS monitoring — verifies domain resolves to the correct IP. Catches DNS hijacking and provider errors.
WooCommerce (HTTP): if you run a store — GET /shop + GET /checkout. Keyword check for "Add to Cart" — ensures the catalog loads.
Plugin vs External Monitoring
| Criteria | WordPress Plugin | External (AtomPing) |
|---|---|---|
| Works when WordPress crashes | No | Yes |
| SSL monitoring | Limited | Full |
| DNS monitoring | No | Yes |
| Multi-region checks | No | 11 agents |
| False alarm prevention | No | Quorum |
| Status page | No | Built-in |
| Impact on your site | Consumes resources | None |
Setup in 10 Minutes
Step 1: Register at AtomPing (free, no credit card).
Step 2: Create HTTP monitor for homepage. URL: https://yoursite.com. Interval: 30 seconds. Add keyword check for your site name.
Step 3: Create HTTP monitor for REST API: https://yoursite.com/wp-json/wp/v2. Checks WordPress backend, bypassing frontend cache.
Step 4: Create TLS monitor: yoursite.com. SSL expiry alert 30 days in advance.
Step 5: Configure alert channels: email + Telegram/Slack/Discord.
Step 6: Create status page with components: Website, Admin, API, SSL. Share link with clients.
Total: 4-5 monitors fully cover WordPress. On the free plan, you'll have 45+ monitors remaining for other sites.
WooCommerce: Additional Checks
If you run a store on WordPress, standard checks aren't enough. WooCommerce adds dependencies: payment gateways, shipping APIs, inventory sync. Any of these going down means lost revenue.
Catalog: HTTP check on /shop + keyword "Add to Cart". If the catalog is empty or shows error, keyword check will trigger.
Checkout: HTTP check on /checkout. If checkout is down — that's lost revenue.
Payment Gateway: monitor payment provider status pages (Stripe status, PayPal status). Webhook monitoring for payment confirmations.
WordPress Multisite and Agencies
Agencies managing 10-100 WordPress client sites can monitor all from one AtomPing account. 50 monitors on the free plan cover 10-12 client sites (4-5 monitors each). AtomPing Pro ($5/month) offers unlimited monitors for unlimited clients. See more: monitoring for agencies.
Automation: Monitoring Updates
Problem: WordPress auto-updates (core, plugins, themes) can break your site. Updates run via cron — usually overnight.
Solution: 30-second interval monitoring catches breakage within a minute of update. Keyword check for "Fatal Error" or "Error Establishing a Database Connection" (negative check — if text appears, alert).
Additionally: heartbeat monitoring for WP-Cron: if scheduler stops, tasks (scheduled posts, email queues, backups) won't run.
Related Articles
Complete Guide to Uptime Monitoring — from your first monitor to enterprise setup
SSL Certificate Monitoring — prevent expiry before users see "Not Secure"
Keyword Monitoring Use Cases — detect error pages and content failures
10 Causes of Downtime — how to prevent each one
Monitoring for Agencies — manage 100+ client sites
FAQ
Does WordPress have built-in uptime monitoring?
No. WordPress itself doesn't monitor its own availability. If your WordPress site goes down due to a hosting issue, PHP crash, or database failure — you won't know until a visitor tells you. External monitoring tools like AtomPing check your site from outside and alert you immediately.
What should I monitor on a WordPress site?
At minimum: homepage HTTP check (is the site loading?), wp-login.php (is admin accessible?), and /wp-json/wp/v2 endpoint (is the REST API responding?). Add SSL monitoring for certificate expiry. If you run WooCommerce — monitor the checkout page and payment gateway endpoint.
How often do WordPress sites go down?
Shared hosting: 1-5 outages per month (minutes to hours). Managed WordPress hosting (WP Engine, Kinsta): 0-1 outages per month (seconds to minutes). VPS/dedicated: depends on your configuration. Plugin conflicts and failed updates cause most downtime that hosting doesn't — these need monitoring too.
Can a WordPress plugin monitor uptime?
Plugins like Jetpack offer basic uptime monitoring, but they run inside WordPress — if WordPress crashes, the plugin crashes with it. External monitoring (AtomPing) checks your site from outside, independent of WordPress. When WordPress is down, the monitoring still works and alerts you.
What causes WordPress downtime?
Top 5 causes: (1) hosting server issues (shared hosting overload), (2) plugin conflicts after updates, (3) PHP memory exhaustion (Fatal Error), (4) database connection failures (Error Establishing a Database Connection), (5) SSL certificate expiry. Each requires different monitoring approach.
Is free monitoring enough for a WordPress site?
For most WordPress sites — yes. AtomPing Free (50 monitors, 30s interval, SSL monitoring, status pages) covers a WordPress site comprehensively. You need Pro only if you want custom domain for status page or unlimited monitors for agency scenarios (50+ client sites).