WordPress uptime monitoring with a website down alert that calls your phone

Add your public homepage to an external monitor, define the response you expect and connect alerts to someone who can act. To monitor WordPress site uptime usefully, choose URLs around business activities rather than assuming the homepage represents everything.

For lead generation, add your advertising destination or contact page. For WooCommerce, consider separate product and cart endpoints. Each check establishes HTTP availability for that address. It does not submit a lead, add merchandise or place an order.

A second endpoint such as /wp-login.php or a /wp-json/ REST URL can give you another response to compare during an investigation. Inspect its normal behavior first. Security settings may intentionally block access or redirect requests, and a REST response has its own expected status. A successful public homepage can also be cached while a dynamic endpoint fails.

When comparing approaches, read best WordPress uptime monitoring services compared. Consider the failures you need to detect, your alert recipients and the business process involved.

No. TrackDowntime is an external service, so there is no WordPress uptime monitoring plugin to install. Its checks and alerting run on separate infrastructure. They can continue even when WordPress cannot execute PHP, connect to its database or load its installed plugins.

A plugin running entirely inside the site depends on that environment being available. Some plugins use an external service instead. Evaluate where the actual checks run rather than judging a tool only by whether it offers a plugin.

This distinction matters during a hosting outage. If your server stops answering, the external request fails independently of anything WordPress can report. An expired SSL certificate or DNS problem can also prevent visitors reaching the domain before WordPress has any opportunity to run.

You configure TrackDowntime outside wp-admin. It provides no WordPress dashboard plugin, wp-admin widget, plugin update management or backup management. Keep your maintenance and recovery tools alongside monitoring. A phone alert gives your team a reason to investigate; it does not restore a backup, repair PHP or reverse an update.

Configure the site's endpoint on Professional or Enterprise and add the phone numbers that should receive calls and SMS. Every listed number gets both channels. Your WordPress downtime alert can reach the owner and the technical contact without depending on either person checking an inbox.

The alert schedule starts at 0 minutes and repeats at 5, 10, 15, 20, 30, 40, 50 and 60 minutes, then at 2, 4, 8, 24, 48 and 96 hours until recovery. These are repeat points for an ongoing incident. Timeouts are rechecked before alerting, so the check interval is not a guaranteed deadline for a delivered call.

Review downtime alerts by phone call and website monitoring SMS alerts when deciding who should receive each site's warnings. Alerts are never billed per message, including repeated attempts during an unresolved outage.

Agree who will contact the host, inspect recent changes and communicate with the business owner. Keep those instructions accessible outside the affected WordPress site so a failed server does not also hide the response plan.

A database connection failure can show visitors the message "Error establishing a database connection" with HTTP 500. The PHP fatal error screen saying "There has been a critical error on this website" also returns HTTP 500. A monitor expecting 200 identifies those responses as failures without needing to read the error message.

During updates, WordPress maintenance mode displays "Briefly unavailable for scheduled maintenance" and returns HTTP 503. That response also fails an expected 200 check. It indicates an unavailable endpoint, not proof of which update or component caused the interruption. Review the site and host to establish the cause.

If a plugin or security tool redirects the homepage to a login or maintenance page, set Expected Status Code to 200 and turn Follow redirects off. The initial redirect then fails the rule. Apply this only where the normal homepage should answer directly. Following redirects could otherwise lead to a destination that responds successfully.

Monitoring can also reveal failed requests associated with hosting outages, DNS trouble or expired SSL. Treat the alert as evidence that the configured request failed. It does not identify a faulty plugin or establish that every visitor everywhere has the same experience.

TrackDowntime checks from a single network and has no multi-location monitoring. A failure restricted to another network or region may need evidence from that location. Its results describe the monitored requests, rather than a complete view of every visitor's connection.

There is no keyword or content matching. A page returning 200 with a broken layout, missing contact form or error text can pass. The same applies to a security challenge served directly with the expected code. Status checks cannot decide whether the visible page is useful.

There are no browser or transaction checks. A healthy WooCommerce cart response does not prove that checkout, payment or order confirmation works. Pair HTTP monitoring with appropriate functional testing for those flows. TrackDowntime also provides no status pages. Use its incident records for investigation without treating them as a public incident communication system.

Professional costs $99/mo or $588/yr and includes 25 endpoints, 60 second checks and 90 days of history. It adds SMS and phone calls to every listed number, supports 10 email recipients and includes custom headers. It suits a business site or agency portfolio that fits those endpoint and recipient allowances.

Enterprise costs $299/mo or $1,788/yr. It includes unlimited endpoints, unlimited recipients, history without a limit, 60 second checks, SMS, phone calls and a white label report name. Agencies can plan client coverage through website monitoring for agencies rather than treating each client homepage as the whole monitoring scope.

Starter costs $49/mo or $288/yr for 5 endpoints, 5 minute checks and 30 days of history. Its channels are email for you plus 3 recipients, Slack and a signed webhook. Choose a higher plan when the requirement is a ringing phone. Compare the allowances on pricing before deciding.

An uptime report is available per endpoint for 24h, 7d, 30d, 90d and all kept history, within your plan's retention. Export CSV for a client review or hosting discussion.