for wordpress sites · every 30 seconds
WordPress uptime monitoring that catches downtime a plugin update caused
WordPress uptime monitoring watches your site from the outside and tells you the moment it stops working, without a plugin adding load to wp-admin. AlertPing checks your WordPress site every 30 seconds, reads the actual page for the white screen a bad update leaves behind, confirms the failure from three regions, and alerts you by SMS before your visitors see it.
Last updated July 2026
no plugin to install | reads the white screen | SMS on every plan
alertping ▸ run check
live
▸ type a domain and run a real-feel check
▸ probes from 3 regions · FRA · IAD · SIN
▸ waiting…▌
queued probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (FRA, IAD, SIN). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: Frankfurt.
the short answer
The best way to monitor WordPress uptime is an external service that checks the site from outside your host every 30 to 60 seconds, so it sees exactly what a visitor sees. Watch for a keyword on the page, not just a 200 status code, because a WordPress fatal error often returns a clean 200 with a white screen. A plugin adds monitoring inside wp-admin, but a plugin cannot report an outage when the whole site, and therefore the plugin, is down. Pick a tool with multi-region confirmation and SMS alerts so you hear about a real outage in seconds and never get paged for a network blip.
the way wordpress fails
A WordPress site rarely returns a clean 500
Most WordPress outages are not the server falling over. They are a plugin update, a theme conflict, a hit database or an expired certificate, and they break the page while the host and the hosting dashboard both stay green. A status-code checker that only asks “did the server answer?” calls every one of these healthy.
That is why you find out from a customer instead of a monitor. The site was technically responding the whole time. It just was not working.
failure 01
The white screen of death
A plugin or theme update throws a fatal PHP error and WordPress serves a blank white page, often with a 200 status. A keyword check that looks for your header text catches it in one probe; a status-code check never will.
failure 02
Error establishing a database connection
When MySQL is overloaded or credentials break, WordPress prints its famous database error. The page loads, so the server looks up. A keyword or content assertion is what turns that into an alert.
failure 03
The SSL certificate expired overnight
An expired TLS certificate hides the whole site behind a full-page browser warning. It is the single most preventable outage there is, and it happens because nobody owns the renewal date.
failure 04
A monitoring plugin that dies with the site
A plugin that runs inside WordPress cannot email you when WordPress itself is down. The outage that matters most is exactly the one it cannot see. External monitoring lives on our servers, not yours.
plugin or external
WordPress uptime monitoring plugin vs external monitoring
A plugin is easy to install and useful for logins, updates and inside-the-dashboard health. For uptime specifically, an external monitor is the one that can actually reach you when the site is gone. Here is the honest split.
| Consideration | Monitoring plugin | External monitoring (AlertPing) |
|---|---|---|
| Detects a full outage | No. If WordPress is down, the plugin is down too | Yes. Checks run from our servers, independent of yours |
| Adds load to your site | Yes, another plugin running on every request | None. Nothing installed, no PHP, no cron on your box |
| Catches the white screen | Sometimes, if the plugin still loads | Yes, with a keyword assertion on real page content |
| Check frequency | Tied to WordPress cron, which only fires on traffic | Every 30 seconds on a fixed schedule, traffic or not |
| SMS and Slack alerts | Usually email only, or a paid add-on | SMS, email, Slack and webhook on every plan |
| SSL expiry warning | Rarely | Yes, with SSL certificate monitoring built in |
Both have a place. Keep a plugin for update and login logs if you like it. Use external monitoring for the outage that takes the whole site, and the plugin, offline.
what to actually check
Five checks that catch a real WordPress outage
01 · keyword on the homepage
Read the page, not just the status code
Pick a word that only appears when the site renders correctly, your site name in the header or a menu label, and assert it is present. The moment a plugin update swaps your homepage for a blank page or a PHP notice, the keyword vanishes and the alert fires. This one check catches more real WordPress downtime than any status code ever will.
02 · the checkout or contact path
Monitor WooCommerce checkout separately
Your homepage can be perfectly fine while the cart or the contact form is broken. Add a second monitor on /cart or /checkout with its own assertion, so a theme deploy that breaks the buy button pages you in under a minute.
03 · ssl expiry
Catch the certificate before it lapses
Get warned 30, 14 and 7 days before the TLS certificate expires, so it never takes the site down behind a browser warning on a Sunday morning.
04 · three regions agree
3 of 3 confirmation kills the false alarm
A single failed probe from one network proves nothing. AlertPing re-checks instantly from Frankfurt, Virginia and Singapore, and only pages you when all three agree the site is down. You keep trusting the alerts, which is the whole point of having them.
05 · the wp-cron heartbeat
Know if scheduled jobs stopped
Backups, scheduled posts and order emails all ride on cron. A cron heartbeat alerts you when a job that should run every night quietly stops.
setup in minutes
How to set up WordPress uptime monitoring
-
1
Add your site URL
Paste your homepage address and pick an HTTP check. No plugin, no FTP, no code on your server. Monitoring starts on the next 30-second cycle.
-
2
Add a keyword assertion
Tell the check to expect a word that only shows when the page renders right. Now a white screen or a database error counts as down, not up.
-
3
Wire your alert channels
Add SMS, email, Slack or a webhook, and set quiet hours or an escalation chain. Every plan includes SMS, with no per-message credits to buy.
-
4
Publish a status page
Turn on a branded status page so visitors and clients can check for themselves during an incident instead of emailing you.
who monitors wordpress this way
From one blog to a fleet of client sites
woocommerce stores
A down checkout has a dollar figure
Monitor the homepage, a product page and the checkout path as separate checks, each with its own assertion. When a plugin update breaks the add-to-cart button but the page still returns 200, you know in under a minute, not from the weekend sales report.
agencies & care plans
The care plan you can defend
If you run WordPress care plans, monitoring is the part the client sees working every month. Watch every client site from one dashboard with uptime monitoring for agencies, 100 sites for $59 a month flat, and send an SLA report that renews the retainer.
membership & lms sites
Logged-in areas that must stay up
Membership, course and community sites lose trust fast when the login or dashboard breaks. Assert on a string that only appears for a working member area, so a broken update surfaces before your members email support.
publishers & blogs
Traffic spikes and shared hosting
A post takes off, shared hosting buckles, and the site 503s at the exact moment it matters most. A 30-second check with SMS means you can upgrade the plan or clear the cache while the traffic is still there.
asked before buying
WordPress uptime monitoring, answered straight
How do I monitor my WordPress site uptime?
Add your site to an external uptime monitor as an HTTP check, set the interval to 30 or 60 seconds, and add a keyword assertion on text that only appears when the page renders correctly. Wire up SMS or Slack alerts, and turn on SSL expiry warnings. You do not need a plugin, and external monitoring keeps working when WordPress itself is down.
Do I need a WordPress uptime monitoring plugin?
Not for uptime. A plugin runs inside WordPress, so when the site goes down the plugin goes with it and cannot alert you. Plugins are useful for login logs, update history and in-dashboard health, but the outage that takes the whole site offline needs an external monitor running on separate servers.
Why does my WordPress site show as up when it is broken?
Because a status-code check only asks whether the server answered, and WordPress often answers with a 200 even while showing a white screen or a database error. Add a keyword or content assertion so the monitor reads the actual page. If the expected text is missing, the site counts as down even though the server replied.
Does monitoring slow down my WordPress site?
External monitoring adds no load at all. Nothing is installed on your server, there is no PHP running and no extra database queries. AlertPing simply requests your pages from the outside every 30 seconds, the same as any visitor, so your site speed is untouched.
before you commit
Three more questions
Want to see it first? Run a real check on your live WordPress site in the interactive demo before you pay anything.
Can I monitor a staging or password-protected WordPress site?
Yes. Add a custom request header or a query token so the monitor can reach a staging URL, and use a keyword assertion on a string that only renders for an authenticated or unlocked page. For basic-auth staging, store the credentials on the monitor and it will send them with each check.
How is this different from what my managed WordPress host offers?
Managed hosts monitor their own infrastructure, not whether your specific site renders. Their dashboard stays green through a plugin fatal, a bad theme deploy or an expired certificate, because from the host point of view the server is fine. External monitoring checks the page a visitor actually gets. Most people run both.
What does it cost to monitor a WordPress site?
Starter is $19 a month for 20 monitors with 60-second checks and SMS included, which covers one site with several checks or a handful of small sites. Team is $59 a month for 100 monitors and 30-second checks, which is what most agencies and WooCommerce stores land on. Yearly billing takes 20% off.
Know your WordPress site is down before your visitors do
30-second checks that read the real page, 3-region confirmation, SMS included, and no plugin slowing your site down. Running in under a minute.