Better Stack Uptime vs UptimeRobot

Better Stack Uptime

Ten documented monitor types from uptime and keyword to DNS, domain expiry, SSL and TCP/UDP port, plus hosted Playwright browser checks at 30-second intervals, is broader coverage than most vendors publish. What earns the score is that the confirmation logic is written down: an incident is created only after a check fails from at least three locations out of a default of four, with an explicit warning that removing locations raises false positives. I still get no probe cities, no description of what an API monitor may assert on headers or body, and private-network monitoring is a heading rather than a documented agent or probe.

UptimeRobot

Nine monitor types plus heartbeat, SSL and domain expiry, ICMP with traceroute and response times, JSON assertions with all-or-any pass logic, DNS checks, maintenance windows and a 15-second interval are documented, and a failed check is re-checked from a different data center in the same region before an alert goes out — the confirmation logic I always ask for, actually written down. The re-check stays within one region and regions are selectable without a city-by-city list, and we found no public information on browser or transaction checks, private locations inside the customer's network, or published probe health.

Better Stack Uptime

Escalation policies with steps, delays, re-alerting and fallback, follow-the-sun regional schedules with overrides and cover requests, acknowledge-and-resolve inside Slack or Teams, severity- and metadata-based routing, smart incident merging and post-mortems drafted from the incident timeline — that is nearly a standalone incident tool. Voice, SMS, e-mail, Slack, Teams and push are all listed under 'all-you-can-alert pricing', but the terms reserve the right to set quotas on resource use, and I found no public information on whether delivery of each channel is itself monitored and reported.

UptimeRobot

Every channel I'd ask about is documented — email, SMS, phone call, mobile push, Slack, Teams, webhooks, and forwarding to PagerDuty — with per-monitor contact assignment, an up-to-60-second timeout to prevent false positives, and a 3-of-5 consecutive-request rule before a response-time alert fires. SMS and voice costs are published in credit packs with voice calls flat at two credits and a country-by-country credit list, and the pages even disclose that a failed auto-refill charge switches auto-refill off with no notification sent — an honest detail I respect. Escalation policies and on-call schedules, though, are only reachable through third-party integrations like ilert and Zenduty, and we found no public information on native escalation with timeouts, acknowledge-from-app or chat, alert grouping, or recovery notifications.

Better Stack Uptime

Custom domain by CNAME, sections grouping monitors, heartbeats and third-party services, incident and maintenance templates, per-component e-mail subscriptions, password-, SSO- and IP-allowlist-protected private pages, translations in beta, embeddable badges and announcements, and CSS plus JavaScript customization make a serious page. Subscriber channels beyond e-mail are not described, however, and the captured pages say nothing about how the status page itself stays online if the vendor's own service goes down.

UptimeRobot

Custom domain with automatic Let's Encrypt certificates, password protection, eleven languages, whitelabeling, embeddable badges, incident and maintenance announcements and email subscribers are all documented, with per-plan page counts from one to unlimited. Two caveats the pages themselves state: the custom domain must be a subdomain — apex domains are unsupported — and a downgrade, expired trial or failed payment immediately blocks the whole page on the custom domain. We found no public information on SMS, RSS or webhook subscribers, component groups, incident templates, or how the status page hosting is kept separate from the main service.

Better Stack Uptime

A JSON:API REST API documented across monitors, heartbeats, incidents, status pages, metadata, team members, organization roles and usage, with team-scoped and global bearer tokens, plus Terraform management, SAML SSO for Okta, Azure and Google, and Okta SCIM with group push that creates teams — the administration story is real and current. I found no public information on audit logs, two-factor authentication, bulk monitor import or white-label client reports, which keeps it a rung below the top.

UptimeRobot

The v3 REST API covers monitors, alert contacts, maintenance windows and public status pages with documented rate limits, OAuth 2.0, key rotation and bulk operations, alongside an official CLI and MCP, read/write/notify-only team roles, and two-factor authentication required for privileged admin access per the security annex. Terraform and Ansible appear as community tooling for onboarding monitors via infrastructure-as-code rather than a documented first-class provider. We found no public information on SAML single sign-on, SCIM provisioning, audit logs, or client sub-accounts with their own logins.

Better Stack Uptime

Compound SLA reports across selected monitors, MTTA and MTTR, on-call and response-effort reports with metadata and resource-group filters, CSV export that honours the filters plus a live shareable CSV URL, response times retrievable by API, and the monitoring IP addresses and User-Agent published in the FAQs — the record is genuinely exportable. But retention is stated only for logs at 30 days and errors at 90 days, never for check results themselves; there is no SLA with credits, no public incident history or post-mortems from the vendor, and its own availability is evidenced only by a 'System status' footer line.

UptimeRobot

The reporting engine is real: uptime percentages for 24 hours to 365 days, MTBF per monitor and account over 7, 30 or 365 days, monthly uptime reports with downtime budgets, SLA policies with 99.9% and 99.99% targets whose uptime is the average of member monitors shown to three decimals, per-client policies each with their own report, and retention stated per plan at 3 to 24 months. But the questions I ask of the monitor itself go unanswered: we found no public information on the vendor's own public status page or incident history, an SLA with credits, published probe IP addresses for allow-listing, response time percentiles or breakdowns, or a raw export of check results.

Better Stack Uptime

The contracting entity is Better Stack, Inc., a Delaware corporation under New York law and courts; the privacy policy says personal data is processed 'primarily in the European Union' while the data processing agreement permits transfers to the United States under the Data Privacy Framework and standard contractual clauses. A DPA is published, a subprocessor list is maintained online, and SOC2 Type 2 is stated, but we found no public information on an EU contracting entity or EU representative, and subprocessor locations beyond the United States are not itemised.

UptimeRobot

The contracting entity is UptimeRobot s. r. o. of Bratislava with Slovak governing law and Slovak courts in both the terms and the DPA, a published DPA version 2.2 with SCC modules and a docking clause, 30-day subprocessor change notice, full liability for subprocessors, deletion within 90 days with written certification, backup deletion within 180, and breach notice within 72 hours. Subprocessors are named with purposes — Hetzner hosts the monitoring infrastructure, API services and status pages — and processing is stated as primary European Union with a United States secondary under stated safeguards, with encryption in transit and at rest. It stays below the top because UptimeRobot itself holds SOC 2 Type I while the Type II and ISO 27001 certifications belong to its infrastructure providers, and individual subprocessor locations are not stated.

Better Stack Uptime

The free tier is fully specified — ten monitors, one status page, 100,000 exceptions — and add-ons carry exact unit prices: Single Sign-On with Okta or Azure at $5 per user per month, Playwright minutes at $1 per 100 minutes, additional exceptions at $0.000050 each, with taxes stated exclusive of VAT. But no paid uptime tier price or monitor-scaling rule appears on the captured pricing page and enterprise is a custom quote, so a real annual cost cannot be computed; 'all-you-can-alert' pricing sits beside terms reserving the right to set quotas, and the captured pages give different pictures of refunds — a 60-day money-back guarantee on the pricing page against terms stating no refund is owed.

UptimeRobot

The free tier is fully spelled out — 50 monitors, 5-minute interval, one status page, no credit card — and paid tiers publish interval, status-page count, seats, retention and included SMS credits, with extra seats at $15/19 a month, SMS and voice credit packs from $3 for 10 credits, voice calls flat at two credits, and a country-by-country credit consumption list in a blog post. The pages even disclose the ugly edge: a failed auto-refill charge switches auto-refill off with no notification sent, and auto-refill needs a card, excludes PayPal and the smallest pack. But Solo and Scale are listed as starting prices, extra monitors and shorter intervals are sold as Upgrades without a captured unit price, and we found no public information on VAT treatment or monthly list prices.