whats-best.ai
Search Sign in

Uptime Monitoring & Status Pages

UptimeRobot

EU-Made Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by UptimeRobot s. r. o. · uptimerobot.com

Compare with Better Stack Uptime → Compare with Oh Dear → Report an error on this page Is this your product? →

Link to this page

UptimeRobot: AI-assisted analysis on whats-best.ai UptimeRobot: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

UptimeRobot at a glance

Vendor
UptimeRobot s. r. o.
Headquarters
Not stated on the vendor’s pages as of 1 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 1 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 1 Nov 2026
Panel verdict
The AI panel rates UptimeRobot 3/5, the mean of 6 judges. UptimeRobot is an uptime monitoring and status page service from UptimeRobot s. how scores are made
As of
Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources

UptimeRobot alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The E-Commerce Operations Manager

Weighted verdict

Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The E-Commerce Operations Manager

Panel median The E-Commerce Operations Manager This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The E-Commerce Operations Manager
Checks, locations & failure confirmation 3.5 of 5 3.5 of 5
Alerting, escalation & on-call 3 of 5 3 of 5
Status pages & incident communication 3 of 5 3 of 5
API, monitoring as code & team administration 3 of 5 3 of 5
Uptime reports, data & the vendor's own reliability 3 of 5 3 of 5
European sovereignty 3.5 of 5 3.5 of 5
Pricing transparency 3.5 of 5 3.5 of 5

Checks, locations & failure confirmation

How this is scored

What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.

0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.

3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.

5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.

8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.

10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.

Report an error

The E-Commerce Operations Manager

Nine monitor types are documented — website, keyword, ping, port, TCP, UDP, DNS, cron/heartbeat and third-party services — with checks as often as every 15 seconds, a failed check re-confirmed from a different data center in the same region before any alert goes out, custom timeouts up to a minute, response-time limits with alerting, and maintenance windows; JSON body assertions exist on API checks. What I found no public information on is a browser or transaction check that walks a login or checkout flow — the exact blind spot that once let our homepage answer 200 while the payment page errored for six hours — or probe locations named by city, or private probes inside our own network. 9 13 14 22 8

Report an error

Alerting, escalation & on-call

How this is scored

How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.

0 — No alerting at all; results can only be viewed in the dashboard.

3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.

5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.

8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.

10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.

Report an error

The E-Commerce Operations Manager

Alerts reach people by email, SMS, phone call, mobile push, Slack, Microsoft Teams, Telegram and webhooks — up to sixteen ways — with per-monitor contacts, a delay rule before slow-response alerts (only after 3 of 5 consecutive requests), and maintenance windows that mute alerts. SMS and voice calls work on every plan via prepaid credits, from "$3 for 10 SMS or voice call credits" up to "$100 for 1000 SMS or voice call credits", one voice call alert equals two credits, and SMS cost varies by country — so waking whoever is on duty that night in peak season is covered. On-call rotations and escalation appear through integrations (PagerDuty, ilert, Zenduty, PagerTree); we found no public information on the product's own escalation policies with timeouts, schedules, or acknowledging and resolving from the app itself. 6 8 13 14 15 16 22

Report an error

Status pages & incident communication

How this is scored

How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.

0 — No status page of any kind.

3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.

5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.

8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.

10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.

Report an error

The E-Commerce Operations Manager

Status pages exist on every plan: monitors appear as components, incidents and planned maintenance get timeline updates, subscribers receive automated email, and a page can sit on our own subdomain via CNAME with automatic Let's Encrypt SSL, password protection, white-label, eleven languages including German and French, Google Analytics and embeddable badges in iframe, Markdown or HTML form. Paid tiers add custom design and up to 100 or unlimited pages. We found no public information on SMS, RSS or webhook subscribers, per-component subscription choices, single-sign-on or IP-restricted private pages, or any statement of how the page itself stays online if the monitoring service goes down. 4 8 10 17 18

Report an error

API, monitoring as code & team administration

How this is scored

How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.

0 — No API, no team accounts; one login per account and monitors are set up only by hand.

3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.

5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.

8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.

10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.

Report an error

The E-Commerce Operations Manager

The v3 REST API is documented to create, edit and delete monitors, alert contacts, maintenance windows and public status pages, returning JSON, JSON-P or XML with published rate limits (10 requests per minute on the free plan, up to 5000 on paid) and bulk operations; teammates get admin, read, write and notify-only access with two-factor authentication, and an SLA policy can be created per client on paid plans. A CLI and MCP are listed alongside the API, with Ansible and Terraform shown as community tools for onboarding monitors. We found no public information on single sign-on (SAML), SCIM provisioning, audit logs, or client sub-accounts with their own logins. 6 7 8 13 19 20 21

Report an error

Uptime reports, data & the vendor's own reliability

How this is scored

What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.

0 — No history of any kind; only the current state is shown.

3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.

5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.

8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.

10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.

Report an error

The E-Commerce Operations Manager

This is what I would hand the agency after a bad night: a monthly or quarterly email report with overall uptime, incident count, total downtime, average duration, mean time between failures per monitor and for the whole account, a response-time summary including peaks above 1,000 ms, and every monitor with daily status bars; SLA policies measure uptime against a target I set (99.9% equals 43m 12s over 30 days) and email the verdict with the downtime budget used, and paid plans keep 12 or 24 months of history with an export function in the services. We found no public information on response-time percentiles or DNS/TLS breakdowns, published probe IP addresses for allow-listing, or the vendor's own status page and incident history. 1 8 11 21 22

Report an error

European sovereignty

How this is scored

Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.

Report an error

The E-Commerce Operations Manager

The contracting entity is UptimeRobot s. r. o. of Bratislava with published registration and VAT numbers, Slovak law and the courts of Bratislava, and a published data processing agreement carrying the Standard Contractual Clauses, security-incident notification within 72 hours, and deletion within 90 days of termination. The subprocessor list is public: Hetzner hosts the monitoring infrastructure, API services and status pages with primary processing in the European Union, Plivo sends SMS and voice, Sendgrid and Amazon SES the emails, Stripe and PayPal take payments, Intercom and User.com run support — while check data is secondarily stored in United States data centers run by AWS, Digital Ocean and Limestone Networks. UptimeRobot itself holds SOC 2 Type I, with SOC 2 Type II and ISO 27001 held by its infrastructure providers — a workable chain for our German, Austrian and Swiss shop, though the American data centers and US SaaS links keep it short of an end-to-end European chain. 9 10 11

Report an error

Pricing transparency

How this is scored

Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.

5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.

Report an error

The E-Commerce Operations Manager

Tiers are public with their scaling: Free at €0 with 50 monitors and 5-minute checks, Solo starting at €108 per year with 60-second checks, 3 status pages and 12-month retention, Team at €360 per year with 30-second checks, 3 seats and 100 status pages, and Scale starting at €660 per year with 15-second checks, 200 or 500 monitors and 5 seats; extra login seats cost $15 or $19 per month, SMS and voice credits run from "$3 for 10 SMS or voice call credits" to "$100 for 1000 SMS or voice call credits", and auto-refill triggers once the balance reaches 25 credits. We found no public information on monthly prices per tier, the monitor count on Solo, VAT treatment, or per-country SMS rates on the pricing page itself — the credit consumption by country sits in a separate blog post — and Enterprise is a custom quote. 8 9 16 17

Report an error

European sovereignty — proven facts

0 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined — uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined ⚠ unverified — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about UptimeRobot

Is UptimeRobot European?

Yes. whats-best.ai classifies UptimeRobot as EU-Made.

Where does UptimeRobot store data?

Not stated on the vendor’s pages as of 1 Nov 2026.

Does UptimeRobot have a free plan?

Yes. UptimeRobot has a free plan, per the vendor’s page captured 1 Nov 2026.

What are the best alternatives to UptimeRobot?

As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) highest among the other 14 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Hyperping (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: UptimeRobot alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Do you know more about UptimeRobot? Tell us Report an error on this page

Sources (23)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor homepage uptimerobot.com Checked 1 Nov 2026 Details →
  2. 2 Features page (SSL monitoring) uptimerobot.com Checked 1 Nov 2026 Details →
  3. 3 Features page (cron job monitoring) uptimerobot.com Checked 1 Nov 2026 Details →
  4. 4 Features page (status pages) uptimerobot.com Checked 1 Nov 2026 Details →
  5. 5 Features page (alerting) uptimerobot.com Checked 1 Nov 2026 Details →
  6. 6 Integrations page uptimerobot.com Checked 1 Nov 2026 Details →
  7. 7 API documentation uptimerobot.com Checked 1 Nov 2026 Details →
  8. 8 Pricing page uptimerobot.com Checked 1 Nov 2026 Details →
  9. 9 Terms of service (names the operating company) uptimerobot.com Checked 1 Nov 2026 Details →
  10. 10 Privacy policy uptimerobot.com Checked 1 Nov 2026 Details →
  11. 11 Data processing agreement (dpa) uptimerobot.com Checked 1 Nov 2026 Details →
  12. 12 Security / trust page uptimerobot.com Checked 1 Nov 2026 Details →
  13. 13 Checks, locations & failure confirmation — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
  14. 14 Checks, locations & failure confirmation — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
  15. 15 Alerting, escalation & on-call — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  16. 16 Alerting, escalation & on-call — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  17. 17 Status pages & incident communication — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  18. 18 Status pages & incident communication — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  19. 19 API, monitoring as code & team administration — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  20. 20 API, monitoring as code & team administration — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
  21. 21 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  22. 22 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
  23. 23 Self-hosting / on-premises installation docs — found from the homepage uptimerobot.com Checked 1 Nov 2026 Details →