Key Takeaways (BLUF)
Bottom Line Up Front: WordPress's built-in cron system (WP-Cron) fires only when someone visits your site. On low-traffic sites, scheduled tasks can be delayed by hours. More critically, WP-Cron stops completely when your server goes down — which is exactly when you need an uptime alert most. Any monitoring solution that depends on WP-Cron to detect downtime is fundamentally broken. Use external cloud monitoring like WakeMetric instead.
What Is WP-Cron and How Does It Actually Work?
WordPress does not have a traditional system-level cron daemon. Instead, it implements a pseudo-cron system called WP-Cron, which runs scheduled tasks by piggybacking on website visits.
Every time a visitor loads any page on your WordPress site, WordPress checks a list of pending scheduled tasks. If any task is due or overdue, WordPress runs it at that moment, alongside the page load. This approach has a significant advantage: it requires no server configuration and works on shared hosting where you cannot set up real system cron jobs.
But this convenience comes with serious limitations that make WP-Cron fundamentally unsuitable for uptime monitoring.
The Three Critical Problems with WP-Cron for Uptime Monitoring
Understanding these three failure modes is essential before deciding how to handle any scheduled task on WordPress — and especially before relying on WP-Cron for anything as time-sensitive as downtime detection.
- Problem 1 — Traffic dependency: WP-Cron tasks only run when a visitor hits your site. On a low-traffic business website that receives 10–20 visitors per day, a scheduled "every 5 minutes" check may only run once or twice per hour. The check interval you configure is a best-case ceiling, not a guarantee.
- Problem 2 — The self-monitoring paradox: A WP-Cron-based uptime monitor is code that runs inside your WordPress installation. If your server goes down, runs out of memory, or encounters a fatal PHP error, WordPress stops executing entirely. The monitoring code stops with it. The scheduled check never fires. No alert is sent. This is the fundamental paradox of self-hosted monitoring: the tool goes offline at exactly the moment you need it most.
- Problem 3 — WP-Cron drift on heavy sites: On high-traffic sites, WP-Cron can fire multiple times within a single minute, causing duplicate task execution. On sites with aggressive caching, Cloudflare, or other proxies intercepting requests before they reach PHP, WP-Cron may fire unpredictably or not at all.
A Concrete Example: What Happens During a Real WordPress Crash
Imagine you have installed a monitoring plugin that uses WP-Cron to check your own site's availability every 5 minutes. At 2:47 AM, your hosting server runs out of memory and crashes. PHP stops executing. Your WordPress database becomes unreachable.
At 2:50 AM, WP-Cron is scheduled to run its uptime check. But WP-Cron only fires when a visitor hits your site. No visitors are coming at 2:50 AM, and even if they were, PHP cannot execute because the server is out of memory.
At 6:15 AM, your first morning visitor arrives. Their browser request kicks WP-Cron. But the server is still down, so PHP still cannot execute. Nothing runs.
At 7:30 AM, your hosting provider restores service. The next visitor loads a page. WP-Cron fires and runs all overdue scheduled tasks — including the uptime check, which now reports your site as "up." No downtime was ever recorded. No alert was ever sent. You had 4 hours and 43 minutes of complete downtime with zero notification.
This is not a theoretical scenario. It is the exact failure mode that WP-Cron-based monitoring plugins produce in real production environments.
How External Uptime Monitoring Solves This Problem
External uptime monitoring reverses the architecture entirely. Instead of running monitoring code inside your WordPress installation, external monitoring runs on completely independent cloud servers in different data centres, under different network connections, with no dependency on your server, your PHP installation, or your WordPress database.
WakeMetric's monitoring infrastructure, for example, performs HTTP checks from cloud nodes in Frankfurt, London, Virginia, Singapore, and Tokyo. These checks run on a fixed schedule regardless of whether anyone is visiting your WordPress site. They do not depend on WP-Cron, on PHP executing, or on your database being available.
When one of those checks returns an error, WakeMetric's infrastructure immediately re-verifies from multiple independent nodes. If the failure is confirmed from multiple locations, you receive an email alert — before your visitors find out, before your customers call, and long before a self-hosted monitoring plugin could ever detect anything.
WP-Cron vs External Monitoring: The Technical Comparison
Here is a direct comparison of what happens with each approach when your WordPress site goes down.
| Scenario | WP-Cron Based Monitor | External Cloud Monitor (WakeMetric) |
|---|---|---|
| Server runs out of memory at 2 AM | WP-Cron stops. No alert sent. | External check fires on schedule. Alert sent within minutes. |
| Fatal PHP error crashes WordPress | Plugin cannot execute. No alert sent. | External check detects error response. Alert sent. |
| Database connection fails | Plugin cannot query DB to send alert. No alert sent. | External check receives 500 error. Alert sent. |
| Low-traffic site at 3 AM (no visitors) | WP-Cron never fires. Check never runs. | External check fires regardless of site traffic. |
| Hosting provider network outage | PHP cannot reach any network. No alert sent. | Multiple global nodes detect outage independently. Alert sent. |
| Transient network blip (1 second) | WP-Cron fires and might log a false failure. | Multi-node consensus prevents false alarm. |
What About Using a Real System Cron Instead of WP-Cron?
A common recommendation for fixing WP-Cron reliability is to disable WP-Cron and set up a real system cron job on your hosting server to trigger wp-cron.php on a fixed schedule. This does solve the traffic-dependency problem — your scheduled tasks will fire on time even when no visitors are present.
However, this approach does not solve the self-monitoring paradox. The system cron job runs on the same server as your WordPress installation. When your server goes down, the system cron stops too. A monitoring script triggered by a system cron on the monitored server cannot report that the monitored server is offline.
True uptime monitoring requires infrastructure that is physically and logically independent of the monitored system. That means external cloud monitoring.
How to Disable WP-Cron and Set Up External Monitoring Properly
If you want to both fix WP-Cron reliability for non-monitoring scheduled tasks and set up proper external uptime monitoring, here is the recommended approach.
- Step 1: Disable WP-Cron by adding DEFINE('DISABLE_WP_CRON', true); to your wp-config.php file — this prevents duplicate WP-Cron executions
- Step 2: Set up a real system cron job (via cPanel, Plesk, or SSH) to request /wp-cron.php?doing_wp_cron every 5 minutes — this makes WooCommerce order emails, scheduled post publishing, and plugin tasks reliable
- Step 3: Install the WakeMetric plugin from WordPress.org for external uptime monitoring — this runs completely independently of your server and alerts you when your site goes down
- Step 4: Enter your alert email in WakeMetric and click Connect — you now have both reliable scheduled tasks and independent external monitoring
Frequently Asked Questions
Can I use WP-Cron for anything monitoring-related at all?
WP-Cron is reliable for tasks that can tolerate some delay and that run at the application level — things like sending a scheduled email newsletter, publishing a scheduled post, or clearing a plugin cache at midnight. These tasks are fine if they fire a few minutes late. But any task that needs to run precisely on schedule, or any task related to detecting server downtime, is unsuitable for WP-Cron. Use a real system cron for the former and external cloud monitoring for the latter.
I have a plugin that says it does uptime monitoring via WP-Cron. Is it useless?
A plugin that pings external URLs using WP-Cron can be useful for monitoring third-party services from your WordPress server — such as checking whether a payment gateway API is responding. For monitoring your own site's uptime, it is fundamentally unreliable because of the self-monitoring paradox: if your site goes down, the plugin stops with it.
Does WakeMetric use WP-Cron?
No. WakeMetric's uptime checks are performed by independent cloud infrastructure in multiple global regions. The WakeMetric WordPress plugin is a lightweight connector that sends your site details to WakeMetric's platform and fetches your monitoring status for display in the dashboard widget. The actual monitoring runs on WakeMetric's servers, completely independently of your WordPress installation.
Does disabling WP-Cron break anything?
Disabling WP-Cron (via DISABLE_WP_CRON in wp-config.php) without setting up a replacement system cron will break scheduled tasks like scheduled post publishing, WooCommerce order emails, plugin auto-updates, and backup scheduling. Always pair DISABLE_WP_CRON with a real system cron job pointing to /wp-cron.php?doing_wp_cron. Your hosting provider's control panel (cPanel, Plesk) usually makes this straightforward to configure.
Conclusion
WordPress's built-in scheduling system was designed for convenience, not for reliability. It cannot fire when no one is visiting your site, and it cannot alert you when your server is down — which is precisely the scenario you need to know about. For genuine uptime monitoring, you need a system that operates independently of your WordPress installation. Install the free WakeMetric plugin and let external cloud infrastructure do what WP-Cron was never designed for.