Free tools Windows power users keep installed
One-click scans. No signup required.
The quickest way to receive a WordPress outage alert is to install and connect Jetpack, then open Jetpack → Settings → Security in WordPress Admin and enable Downtime monitoring. Jetpack’s free monitor checks the homepage every five minutes, emails the WordPress.com account that connected the site when downtime is confirmed, and sends a recovery message when the site responds again. The Jetpack and WordPress mobile apps can also deliver push notifications.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
If your monitor must remain independent of WordPress, configure an external service such as UptimeRobot. Its website-monitoring service advertises checks as often as every 30 seconds and can route alerts through email, SMS, phone calls, mobile push, Slack, and webhooks. Using both approaches gives you a WordPress-native alert and a separate path that can still work when the WordPress installation or host is unavailable.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Choose the monitoring approach that fits your failure risk
There are two practical designs. Jetpack is the simplest for a normal WordPress site because it is installed in WordPress and requires little configuration. An external monitor is preferable when you want monitoring that does not depend on the site’s plugins, dashboard, or hosting account.
| Capability | Jetpack Downtime Monitoring | External monitor such as UptimeRobot |
|---|---|---|
| Setup | Install Jetpack, connect a WordPress.com account, and switch on Downtime monitoring. | Create a separate monitoring account and add the site as a monitor. |
| Advertised check interval | Every five minutes in the current standard documentation. | UptimeRobot advertises checks as often as every 30 seconds. |
| How outages are confirmed | Homepage HTTP HEAD checks; a failure is verified from three geographically different servers. | Depends on the service and monitor type; look for geographic verification and configurable retry rules. |
| Notification channels | Email; push notifications through the Jetpack or WordPress mobile apps. Jetpack Monitor upgrades may add one-minute checks, SMS, and multiple recipients. | Email, SMS, phone calls, Slack, webhooks, mobile push, and other integrations are advertised. |
| Independence from WordPress | No. The monitor is connected to the WordPress site and WordPress.com account. | Yes. The monitoring system is configured separately from the WordPress dashboard. |
| Recipient control | The free monitor emails only the WordPress.com account that originally connected Jetpack. | Recipient and integration controls depend on the external service and selected plan. |
| Cost information established here | Free downtime monitoring is documented; upgraded capabilities are plan-dependent. | Specific current pricing is not established here. |
Do not treat an advertised interval as a guaranteed detection time. Confirmation retries, network delays, DNS caching, and the time required to send an alert all add latency.
#1 Best Overall
- Hardware Controller with Professional Network Management-Centralized management for up to 100 Omada devices including Omada access points, Omada Security Gateways and Jetstream switches.
- Premium Hardware Design-Industry-leading flexible Rackmount/Desktop design with a powerful chipset, durable metal casing, 2 fast ethernet ports and 1 USB 2.0 port for auto backup.
- Dual power selection-Support PoE (802.3af/802.3at) and micro USB for flexible installations.
- Easy Network Monitor & Maintenance-The easy-to-use dashboard makes it simple to see your real-time network status and improve network maintenance for peace of mind.
- Cloud Access with No License Fee-Enjoy cloud service with no license fee with the use of OC200. Remote Cloud access and Omada app brings centralized cloud management of the whole network from different sites—all controlled from a single interface anywhere, anytime.
Set up Jetpack Downtime Monitoring
Prerequisites
- A working WordPress site with administrator access.
- The Jetpack plugin installed and activated.
- A successful Jetpack connection to a WordPress.com account.
- Access to the inbox for the account that connected the site.
- Optional: the Jetpack or WordPress mobile app with push notifications enabled.
Activation steps
- In WordPress Admin, open Plugins → Add New, search for Jetpack, install it, and activate it.
- Follow Jetpack’s connection flow and sign in to the WordPress.com account that should own the monitoring connection. Finish the connection rather than leaving the plugin in an unconnected state.
- Open Jetpack → Settings → Security.
- Find Downtime monitoring and turn it on.
- Check the connected account’s email address. The free monitor sends downtime email only to that account, so add forwarding or an inbox rule if your operating procedure requires another person to see the alert.
- For phone alerts, sign in to the Jetpack or WordPress mobile app, select the site, and allow push notifications in both the app and the phone’s operating-system settings.
Jetpack describes the feature as continuously watching the website and alerting you when downtime is detected. It also sends a recovery notification after the site is reachable again. Send a controlled test, such as briefly blocking the site from an authorized test environment if your hosting and security procedures allow it, and verify both the outage and recovery messages before relying on the monitor.
How Jetpack decides that the site is down
The current Jetpack support description says the monitor checks the homepage every five minutes with an HTTP HEAD request. A response status of 400 or higher, more than three redirects, or a response taking longer than 20 seconds creates a tentative failure. Jetpack then repeats the check from three geographically different servers. Only when all three checks fail does it mark the site down and notify the owner.
This confirmation process reduces alerts caused by a single probe or a transient route problem, but it also means that a very brief outage may end before a confirmed alert is sent. A site that is technically returning a page can still be unusable to visitors if the page is extremely slow or if a critical feature is broken.
What the upgraded monitor may add
Jetpack’s dashboard documentation describes an upgraded Jetpack Monitor with one-minute monitoring intervals, SMS notifications, and multiple email recipients. Plan features and availability can change, so verify the current offer in your Jetpack account before designing an escalation policy around any of them.
Rank #2
- Automatic Router Rebooter / Reset - Stop manually restarting your router! Automate the process to ensure highly reliable internet connection uptime
- Constantly Monitors Router and/or Modem Internet Health. Keep Connect provides 24/7/365 protection to ensure that your smart home and connected devices are always online and available.
- Notifications - Free Texts or Emails from Keep Connect notifying you of detected eventsif you choose to enter your phone number/email. You may also choose No Notifications.
- Perfect for Smart Home Reliability - Schedule Periodic Resets to keep your connection fresh and fast.
- Premium Cloud Services App Available (iOS App Store and Google Play Store) - Our Premium Keep Connect Cloud Services platform allows using our Online/Mobile App to monitor many locations in one place as well. Cloud Services allows remote management of devices at all locations as well as heartbeat monitoring of your Keep Connects to notify you in the event of an ISP internet outage at one of your sites.
Use an independent monitor when WordPress itself may be unavailable
A WordPress plugin cannot be your only line of defense if the outage prevents WordPress from loading, disables the plugin, breaks the Jetpack connection, or affects the host’s entire control plane. An external monitor runs outside that stack and can therefore alert you about a failed origin even when you cannot open /wp-admin.
Configure an external HTTP monitor
- Create an account with the external monitoring provider and confirm the alert destinations you intend to use.
- Create an HTTP or HTTPS website monitor for the public canonical URL, normally the homepage. Use the same hostname that visitors use, including the preferred
wwwor non-wwwform. - Choose the shortest check interval that your plan and site can support. UptimeRobot advertises checks as often as every 30 seconds; that is a provider capability, not a promise that every outage will be reported within 30 seconds.
- Select the notification channels for the people who must respond. UptimeRobot’s published integrations include email, SMS, phone calls, Slack, webhooks, and mobile push, with additional integrations listed separately.
- Set retry or confirmation behavior if the service exposes it. A confirmation rule that requires more than one failed probe reduces false alarms but delays notification.
- Save the monitor and trigger a safe test. Confirm that each selected channel receives the alert, that the message identifies the correct site, and that the recovery event closes the incident.
- Record the monitor URL, account owner, recipients, and escalation instructions in your operations documentation. Store recovery credentials outside WordPress so a WordPress outage does not remove access to the monitor.
Choose an external monitor’s settings deliberately
- Check location: Use multiple regions when available. A single region can mistake a local routing failure for a worldwide outage.
- Interval: Faster checks reduce detection delay but can produce more alerts during transient network events and may cost more.
- Recipients: Send the first alert to the on-call person and a shared incident address, not only to one employee’s inbox.
- Maintenance windows: Silence planned deployments, DNS changes, or host migrations so maintenance does not become an avoidable incident. Make the window finite and review its end time.
- Escalation: Use a webhook or team-chat integration for the first notification and a phone or SMS escalation when the alert remains open.
Monitor more than the homepage when the business depends on it
A homepage HTTP check answers one narrow question: can a remote system obtain an acceptable response from that URL? It does not prove that every WordPress function works.
Separate availability checks from transaction checks
Add checks for the functions that would actually cost you money or block users. Depending on your monitoring service, these may be keyword checks, API checks, synthetic browser transactions, or scripted tests.
- Login: Verify that the login page loads and that a test account can authenticate if your security policy permits synthetic credentials.
- Checkout or forms: Test the complete path through cart, payment hand-off, or lead submission in a non-destructive environment or with a controlled test transaction.
- Search: Confirm that a representative query returns results rather than a blank or error page.
- REST API: Check a protected endpoint or a known public endpoint when mobile apps or integrations rely on it.
- Scheduled work: Watch the job queue, Action Scheduler, or host cron status separately. A site can serve pages while scheduled backups, email, or publishing tasks are failing.
Use a dedicated test account and test data for synthetic transactions. Never put real customer credentials or payment details into a third-party monitor unless your security and compliance teams have approved that arrangement.
Rank #3
- (10/100/1G) Gigabit Bypass network tap / sniffer equivalent to port mirror on a switch.
- The two monitor/sniff ports are isolated from the network being monitored.
- Automatic bypass of device on power fail.
- Power-over-Ethernet (POE) pass-through. Rated at .75A max at 57vdc
- 5v power through USB3 port or 5v wall transformer (or both). ~500ma consumption.
Include certificate, DNS, and host signals
Visitors can lose access even when WordPress code is healthy. Monitor certificate expiry, DNS resolution, redirect chains, and the host’s status information where those checks are available. Keep the origin hostname and hosting control-panel address in your runbook; a DNS or CDN failure can make the public hostname unusable while the origin remains reachable.
Understand false positives and missed outages
No uptime monitor catches every failure. Jetpack documents several conditions that can create a false positive or hide a real problem.
Intermittent slowness
Jetpack can treat a response taking more than 20 seconds as inaccessible. A site that usually loads but occasionally stalls may therefore generate an alert even though some visitors see a page. Investigate server saturation, database locks, slow external APIs, PHP worker exhaustion, and overloaded plugins rather than simply increasing the timeout.
Redirect loops or excessive redirects
More than three redirects is a tentative Jetpack failure. Check WordPress Address and Site Address settings, HTTP-to-HTTPS rules, canonical-host redirects, and CDN rules. Test both the preferred hostname and any legacy hostname that might be redirecting repeatedly.
Rank #4
- NEVER MANUALLY REBOOT YOUR ROUTER AGAIN – The ConnectSense Rebooter Pro plugs between your modem or router and the wall outlet, automatically detecting lost internet connectivity across up to 5 network targets and power cycling your equipment instantly — keeping your home, office, or remote location always online 24/7.
- SCHEDULED & AUTOMATIC REBOOTS – Set up to 10 custom reboot schedules to proactively clear memory leaks, prevent slowdowns, and keep your connection fresh — even before problems occur. Perfect for smart homes, security cameras, smart locks, thermostats, and any device that depends on a stable internet connection.
- REMOTE CONTROL FROM ANYWHERE – Trigger a manual reboot anytime from the free ConnectSense app (iOS & Android) or directly from your home network. Whether you're traveling, at work, or managing a vacation rental or remote office, you stay in control of your network without needing to be on-site.
- AUTOMATIC POWER OUTAGE RECOVERY – When the power goes out, the Rebooter Pro automatically restores and reboots your networking equipment once power returns, eliminating downtime and the need for manual intervention. Ideal for unattended locations, rental properties, and small business networks.
- INTEGRATOR & PRO-GRADE FEATURES – The only router rebooter with a built-in local HTTPS API, giving IT professionals, smart home integrators, and power users advanced automation, monitoring, and remote management capabilities — no cloud subscription required for local control.
Blocked monitoring user agents
Security plugins, firewalls, rate limits, or host rules can block a monitor’s request while allowing ordinary browsers through. Review the web server and firewall logs, identify the monitoring user agent, and create the narrowest allow rule your security policy permits. Do not broadly disable protection just to suppress an alert.
Cloudflare cache and challenge behavior
Cloudflare can serve a cached copy while the origin is down, making an HTTP check appear healthy even though dynamic requests fail. Conversely, an Under Attack browser challenge can reject a monitor that cannot execute the required browser test. Decide whether you want to monitor the public CDN edge, the origin, or both, and configure a check type that matches that goal.
Recommended Free Tools
Application failures behind a successful page
A green homepage does not prove that checkout, login, search, an API, or scheduled tasks work. Add the transaction or endpoint checks described above and give each one a distinct alert name so responders know which function failed.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to do when an outage alert arrives
Respond in a fixed order. The first objective is to determine whether the failure is global, regional, or limited to one function; the second is to restore service without destroying evidence.
Best Value
![[Upgraded] AURSINC NanoVNA-H Vector Network Analyzer 9KHz -1.5GHz Latest HW V3.7 HF VHF UHF Antenna Analyzer, Measuring S Parameters, SWR, Phase, Delay, Smith Chart](https://m.media-amazon.com/images/I/41hseV6xSbL._SL160_.jpg)
- [UPGRADED NanoVNA-H] New HW Version V3.7. It is upgradeable as new firmware is developed. With MicroSD card port now can have the measurement data or the screenshots saved in the it at anytime. Added battery circuit management, more secure. Redesigned PCB, you can connect to mobile phone with Type C-Type C cable (original PCB needs OTG cable), see a clear HD image on your phone. Added a ABS case, which is protective and dust-proof. Disply: 2.8 inch TFT (320 x240).
- [IMPROVED FREQUENCY ALGORITHM] The improved frequency algorithm can use the odd harmonic extension of si5351 to support the measurement frequency up to 1.5GHz. The 9KHz-300MHz frequency range of the si5351 direct output provides better than 70dB dynamic, The extended 300M-900MHz band provides better than 60dB of dynamics, and the 900M-1.5GHz band is better than 40dB of dynamics.
- [MULTIPLE FUNCTIONS] The default firmware main function is used for antenna performance measurement. The TX/RX method can measure the complete S11 and S21 parameters. If you need to obtain S12 and S22, you need to manually replace the transceiver port wiring. The CH0 output level is increased to 0dBm when using the fundamental wave, resulting in more accurate reflection measurement.
- [SUPPORT ANDROID PHONE & PC SOFTSARE CONTROL] Designed a practical and simple control application on PC, you can download touchstone(SNP) files for radio design and simulation software. There is a PC interface that adds functionality and lets you work interactively on a bigger screen. Supports time domain analysis function (TDR). Compatible with most Android mobile phones, convenient for connecting to mobile phones. Support Windows Computer Control.
- [STRONG AND SECURE POWER SUPPLY] This VNA is battery powered or USB powered. Built in 650mAh battery, could work for 2 hours continuously. For longer measurement time, kindly connect an external power source. The product interface displays battery usage, providing a clear understanding of the power status.
- Read the alert details. Note the URL, status code, first-failure time, probe location, and whether the monitor says the event is still open.
- Confirm from another network. Open the site using a phone connection or a different network and device. This distinguishes a local DNS, browser, or ISP problem from a public outage.
- Check the host. Review the hosting provider’s status page, control panel, resource graphs, recent notices, and any emergency maintenance message.
- Check the edge services. If you use a CDN, DNS provider, WAF, or proxy, inspect its incident page and recent configuration changes. Verify that a challenge or cached response is not misleading the monitor.
- Review recent changes. Identify plugin, theme, WordPress core, PHP, DNS, SSL, CDN, and server changes made shortly before the alert. Roll back only a change you can identify and reverse safely.
- Inspect the response. A 5xx “server” status can result from a fatal plugin or theme error. Look at PHP error logs, web-server logs, WordPress debug output, and the host’s fatal-error tools without displaying sensitive diagnostics publicly.
- Test the critical path. Once the homepage responds, test login, forms, checkout, APIs, and scheduled operations. A recovery page alone is not proof that the incident is over.
- Escalate with evidence. Give the host the timestamp, affected hostname, status code, probe region, request path, and relevant log excerpt. Do not send passwords or private customer data.
- Verify recovery. Wait for the monitor’s recovery notification, then confirm from an independent network and check the application-level monitors.
- Record the cause. Document the trigger, duration, remediation, and follow-up action. Keep the incident record separate from the alert so the next responder can act quickly.
Interpret common response categories
| Observed result | Likely direction for investigation |
|---|---|
| DNS failure or hostname does not resolve | DNS records, nameserver delegation, registrar changes, or provider outage. |
| TLS or certificate error | Expired certificate, incomplete chain, hostname mismatch, or a CDN-to-origin certificate setting. |
| 4xx response | Access rule, authentication requirement, WAF block, missing route, or an intentional maintenance restriction. |
| 5xx response | Host failure, PHP fatal error, exhausted resources, broken plugin or theme, database failure, or upstream dependency. |
| Timeout with no status | Network path, overloaded server, firewall drop, stalled PHP process, database lock, or an upstream request that never completes. |
| Homepage works but transaction test fails | Application-level defect, payment or API dependency, session problem, queue failure, or a broken integration. |
Make the alerting system dependable
Use two independent paths for important sites
For a revenue-generating or high-visibility site, enable Jetpack for the WordPress-native signal and an external monitor for independent confirmation. They will not necessarily alert at the same moment because their intervals, probe locations, and confirmation rules differ. Treat the first alert as a trigger to investigate, not as a precise measurement of the outage’s start.
Test after every major change
After changing DNS, SSL, CDN rules, firewall settings, hosting, WordPress, PHP, or a monitoring recipient, run an alert-and-recovery test. Confirm that the monitor can still reach the final canonical URL, that redirects remain within the allowed limit, and that the notification reaches the current on-call person.
Protect access to the monitors
- Use a unique password and multi-factor authentication for each monitoring account.
- Keep at least two administrators or an organization-owned mailbox so one person’s absence does not block incident response.
- Limit webhook permissions and rotate tokens when a team member leaves.
- Do not place monitoring credentials in a WordPress plugin setting that becomes inaccessible during the outage.
Define what “down” means for your site
Write a short service-level rule before an incident: for example, a confirmed homepage failure, a failed checkout transaction, or a critical API error. This prevents responders from arguing about whether an alert is real while customers are waiting. Pair the rule with a maintenance procedure, an escalation contact, and a recovery check.
Which option should you choose?
Choose Jetpack first when simplicity matters
Jetpack is the practical starting point for a small site, blog, portfolio, or brochure site where email or mobile push is sufficient and the owner wants setup inside WordPress. It requires no separate monitoring dashboard, and its three-location confirmation reduces some one-off network errors.
Add an external monitor when independence matters
Use an external monitor when the site is business-critical, when several people need alerts, when SMS or phone escalation is required, or when you need monitoring to continue during a WordPress or hosting failure. An external service is also the better foundation for multiple monitors covering the homepage, API, login, and business transactions.
Use both for high-impact sites
Running both is justified when a missed outage is more costly than maintaining two configurations. Keep their URLs, recipients, maintenance windows, and test schedules documented so duplicate alerts produce one coordinated incident rather than confusion.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
