Website uptime monitors, compared by the job.
Website checks are a subfeature of GlimmerStatsBar (mac stats bar). This guide compares them with 20 dedicated products, from hosted uptime checks to browser tests and scheduled-job monitors.
Website checks alongside your Mac readings
GlimmerStatsBar (mac stats bar) combines website checks with CPU, memory, network, storage, battery and thermal readings, app histories, network maps and local recording. Uptime monitoring is one feature of the app.
Choose Cloud, This Mac or both for a website. Cloud checks continue while your Mac is asleep or offline. This Mac checks show the view from the selected Mac and need it awake, online and running GlimmerStatsBar (mac stats bar).
HTTP and HTTPS checks support an expected success status, required text and a slow-response threshold. The app shows response times, source-specific history and incidents. Email can report outages, reminders and recovery; Mac notifications are optional.
Website checks require a verified account. Free allows 1 monitor at a 5-minute minimum interval; Starter allows 2 at 5 minutes, Plus 5 at 1 minute and Pro 20 at 30 seconds. Larger plans are separate from the free Mac monitoring app.
Cloud SMTP checks test the port 25 greeting, with a 15-minute minimum interval. They do not test mail login or message delivery. JSON import and export moves monitor definitions, not incident history.
Compare the tools by purpose
The table highlights documented capabilities, not a score or an exhaustive list of every product. Open each official source for current plans and requirements. A public website request, a browser checkout and a scheduled-job heartbeat answer different questions.
| Product | Documented monitoring features | When it fits |
|---|---|---|
| GlimmerStatsBar (mac stats bar) | Cloud and This Mac HTTP checks, response times, required text, email, history and Cloud SMTP. | A few website checks beside everyday Mac and server readings. |
| UptimeRobot | HTTP, keywords, ports, ping and cron; SSL and domain alerts, public status pages and notification integrations. | A dedicated hosted monitor with more endpoint types and public incident communication. |
| Better Stack | Uptime and Playwright browser tests, cron heartbeats, status pages, on-call schedules and escalation. | Teams that need browser checks and a coordinated incident response. |
| StatusCake | Uptime, page speed, SSL, domain and server monitoring, plus status pages. | A hosted suite for availability and website maintenance signals. |
| Pingdom | Uptime checks, page-speed analysis, transaction monitoring and real user monitoring. | Availability plus page performance and visitor experience. |
| Uptime.com | HTTP and network checks, browser journeys, API tests, heartbeats, private locations and status pages. | Broader synthetic testing, private checks and service reporting. |
| Site24x7 | Website, SSL, DNS and API checks, browser transactions, real user monitoring and private pollers. | Website checks connected to wider infrastructure and application monitoring. |
| Uptrends | Global and private checks, browser journeys, API monitoring and website performance measurements. | Testing user journeys and APIs from selected locations. |
| Oh Dear | Uptime, SSL, broken links, DNS, domain expiry, cron, application health and status pages. | Finding website maintenance problems as well as outages. |
| HetrixTools | Website and server uptime, multiple check locations, server readings, notifications and status pages. | Availability and server resource monitoring in a hosted dashboard. |
| Pulsetic | Checks from multiple regions, SSL, keywords, ports, cron and DNS, with public status pages. | Hosted website checks and a public view of incidents. |
| Checkly | Playwright browser and API tests, checks defined in code, CI/CD and private locations. | Developers who want production tests alongside application code. |
| Hyperping | Uptime, browser tests, cron, SSL, status pages and on-call incident tools. | Website testing and incident communication in one hosted product. |
| Uptime Kuma | Self-hosted HTTP, keywords, JSON queries, TCP, DNS, push, Docker and many notification integrations. | Control over the monitoring host, with public status pages and your own upkeep. |
| Healthchecks.io | Heartbeat URLs, expected schedules, grace periods and alerts for late or missing jobs. | Checking that backups and scheduled jobs actually run; complements website requests. |
| Cronitor | Scheduled-job monitoring, heartbeats, HTTP and API checks, SSL and status pages. | Job execution signals and external availability checks together. |
| Dead Man’s Snitch | Scheduled heartbeat checks and notifications when an expected job signal does not arrive. | Missed-job detection; a heartbeat alone does not prove a public website is reachable. |
| Datadog Synthetic Monitoring | Browser, API and network tests with application traces, logs and infrastructure context. | Engineering teams already using a broad observability platform. |
| New Relic | Scripted browser and API checks, availability tests, private locations and application diagnostics. | Synthetic checks connected to application performance investigation. |
| Dotcom-Monitor | Real-browser journeys, APIs, page speed, availability, SSL and DNS checks. | Browser workflows and detailed website performance testing. |
| Montastic | HTTP, HTTPS, ping and ports, SSL and DNS alerts, notification channels and status pages. | A focused hosted monitor for availability and public updates. |
Where dedicated monitoring goes further
Our current website checks do not include public status pages, multi-region probe selection, browser checkout tests, cron heartbeats, advance certificate-expiry alerts, DNS-change alerts or team on-call escalation. Choose a dedicated tool when those are required.
Multiple probe locations help distinguish a regional problem from a wider outage. Browser tests exercise login or checkout steps. A status page tells customers what is happening. Heartbeats check that a scheduled job reported in time. These are separate capabilities, not other names for a simple HTTP check.
Compare the monitoring approach
Choose GlimmerStatsBar when a small set of website checks belongs beside your Mac readings. Choose a dedicated hosted product for broader tests, customer status pages or team response. Choose self-hosting when control of the monitoring host is worth the installation and maintenance.
GlimmerStatsBar vs UptimeRobot · GlimmerStatsBar vs Better Stack · GlimmerStatsBar vs Uptime Kuma
Official sources and comparison scope
We make GlimmerStatsBar. This comparison uses our current check definitions and the linked official product documentation. It compares features, not measured reliability or every plan entitlement.
Each product name in the table links to its official website or project. This is a broad comparison of 20 products, not a claim to list every monitoring website.
Questions you might have
Do Cloud checks continue while my Mac is asleep?
Yes. Cloud checks run on the server. This Mac checks need the selected Mac awake, online and running the app.
Are all GlimmerStatsBar website checks free?
Website checks require a verified account. Free allows 1 monitor at a 5-minute minimum interval; Starter allows 2 at 5 minutes, Plus 5 at 1 minute and Pro 20 at 30 seconds. Larger plans are separate from the free Mac monitoring app.
Is a cron heartbeat the same as a website uptime check?
No. A heartbeat proves that a job sent an expected signal. An external HTTP check asks whether a website responds. Use both when you need to know that a job ran and that its website is reachable.