Uptime Monitoring & Status Pages
UptimeRobot
EU-Made Report an error0–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
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
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
UptimeRobot is an uptime monitoring and status page service from UptimeRobot s. r. o. of Bratislava; across its seven criteria, low and high scores differ by a point at most. It is strongest on sovereignty: a Slovak contracting entity and governing law, a published data processing agreement version 2.2 with the Standard Contractual Clauses, named subprocessors under 30 days' notice, processing primary in the European Union with the United States as secondary — though UptimeRobot itself holds SOC 2 Type I and its providers hold ISO 27001. Checks and locations and pricing transparency follow: nine monitor types, intervals as low as 15 seconds, re-checks from a different data center before alerting, and public tiers from Free at €0 to Scale starting at €660 per year. Alerting and on-call and reports and reliability sit lowest: rotations and escalation policies are reached through third-party integrations, and the bench found no public information on probe IP addresses, percentiles or the vendor's own status page. Two judges noted the captured pages give different figures for how far back history reaches.
Speaks for it
- A failed check is re-checked from a different data center in the same region before any alert goes out.
- The contracting entity is UptimeRobot s. r. o. of Bratislava under Slovak law, with a published data processing agreement version 2.2 carrying the Standard Contractual Clauses, named subprocessors under 30 days' change notice and deletion within 90 days of termination.
- Tiers are public from Free at €0 with 50 monitors to Scale starting at €660 per year, and SMS and voice credit packs are priced from $3 for 10 SMS or voice call credits.
- Status pages run on every plan — one on Free, 3 on Solo, 100 on Team, unlimited on Scale — with a custom subdomain and automatic Let's Encrypt SSL on paid plans.
- A v3 REST API on every plan covers monitors, alert contacts, maintenance windows and public status pages, with bulk operations, published rate limits, a CLI and MCP.
Held against it
- We found no public information on browser or transaction checks that walk a login or checkout flow.
- We found no public information on native escalation policies, on-call schedules or acknowledging and resolving from the app.
- We found no public information on published probe IP addresses, response-time percentiles or the vendor's own status page and incident history.
- We found no public information on SAML single sign-on, SCIM provisioning, audit logs or client sub-accounts with their own logins.
- The custom domain must be a subdomain, and a downgrade, expired trial or failed payment immediately blocks the page on the custom domain.
Best for
- You run monitoring for many clients and want one white-label status page each — 3 pages on Solo, 100 on Team, unlimited on Scale — with per-client SLA reports.
- You need a documented chain for an auditor: a Slovak contracting entity, a published data processing agreement with Standard Contractual Clauses, named subprocessors and deletion within 90 days.
- You want to start at zero cost with 50 monitors at 5-minute intervals and no credit card required.
- You onboard monitors as code through the v3 REST API, the CLI, or Terraform and Ansible tooling.
Avoid if
- You need on-call rotations, escalation policies and acknowledge-and-resolve inside the product itself; the captured pages point to PagerDuty, ilert, Zenduty and PagerTree for that side.
- You need browser or transaction monitoring of a user flow; the nine documented monitor types stop at website, keyword, ping, port, TCP, UDP, DNS, heartbeat and third-party services.
- You must allow-list probe IP addresses or place private probes inside your own network; we found no public information on either.
- Your compliance scope depends on SAML single sign-on, SCIM provisioning or audit logs; we found no public information on them.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 3 of 5 |
| API, monitoring as code & team administration | 3 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 3.5 of 5 |
| Pricing transparency | 3.5 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
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.
The Agency Developer
Nine monitor types including keyword, ping, port, DNS and cron-job heartbeats, plus SSL and domain-expiry alerts with warning days I can set, is exactly the set I need for sixty client domains. Checks run as often as every fifteen seconds from regions I can choose per monitor, and a failed check is re-run from a different data center in the same region before anyone's phone rings — that alone would have saved me the angry certificate call. We found no public information on browser or transaction checks of a login or checkout flow, private probes inside a client's own network, or probe locations listed by city. 2 5 9 13 14
The SaaS Platform Engineer
Nine monitor types including HTTP, keyword, ping, port, DNS, TCP and heartbeat cron checks, SSL and domain expiry alerts, 15-second intervals, selectable monitoring regions, and failed checks re-checked from a different data center in the same region before an alert goes out — that confirmation logic is exactly what I want before anyone is woken. API monitoring validates JSON with all-or-any assertion logic and custom timeouts up to a minute, but we found no public information on multi-step chained checks, browser or transaction checks of a user flow, or private locations for internal services, which keeps it short of the top band. 13 14 9 2
The Customer Support Lead
Nine monitor types are documented, from HTTP(S) and keyword checks through ping, port, TCP, UDP, DNS and cron heartbeats, with SSL and domain-expiry alerts, JSON assertions on response bodies, response-time limits and a 15-second interval on the top plan. Failed checks are re-checked from a different data centre in the same region before an alert goes out, and monitoring regions can be chosen per monitor, which is the confirmation logic I want before my team answers three hundred identical tickets. We found no public information on browser-level transaction checks or private probe agents inside a customer's own network. 13 14 9 22
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
The Information Security Officer
Nine monitor types including HTTP, keyword, ping, port, TCP, DNS and heartbeat checks, intervals down to 15 seconds, selectable monitoring regions, and a documented re-check from a different data center in the same region before alerting are all described. JSON assertions, SSL and domain expiry checks, custom timeouts up to 60 seconds and maintenance windows are evidenced. We found no public information on browser or transaction checks, private locations inside the customer network, or probe locations listed by city, which is where an auditor would start. 8 9 13 14
The Skeptic
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. 8 9 13 14
Alerting, escalation & on-call
Show reasoningHide reasoning
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.
The Agency Developer
Email, SMS, phone call, mobile push and Slack with webhooks cover the channels an on-call duty rotation needs, contacts can be assigned to monitors individually or in bulk, and message pricing is published: one voice call equals two credits, with a country-by-country list for SMS. Thresholds, a three-of-five consecutive-request rule for slow responses and a configurable timeout dampen false alarms, and alerts forward to PagerDuty, PagerTree, iLert or Zenduty. We found no public information on native escalation policies, on-call schedules and rotations, or acknowledging and resolving from the app — the captured pages point to those integrations for the on-call side. 6 8 13 15 16 22
The SaaS Platform Engineer
Email, SMS, phone calls, mobile push, Slack, Teams, Telegram and webhooks plus forwarding to PagerDuty, ilert, Zenduty and PagerTree, with SMS and voice costs published in credit packs at two credits per voice call and country variation documented. But we found no public information on escalation policies when an alert is not acknowledged, on-call schedules and rotations, or acknowledging and resolving from the app in UptimeRobot's own product — the scheduling the pages mention lives in the partner tools — so it is not a replacement for a dedicated on-call setup. 8 13 16 6 22
The Customer Support Lead
Email, SMS, phone calls, mobile push, Slack, Microsoft Teams and webhooks are documented, with forwards to PagerDuty and on-call partners like ilert and Zenduty, per-monitor contact assignment, recurrence settings and maintenance windows that halt monitoring. SMS and voice credits are priced in packs, one voice call equals two credits, and a country-by-country breakdown is referenced. We found no public information on native escalation policies with timeouts, on-call rotations inside the product, acknowledge-and-resolve from the app or chat, or alert grouping. 13 15 8 16 6 14
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
The Information Security Officer
Email, SMS, voice calls, mobile push, Slack, Microsoft Teams and webhooks are documented, with forwarding to PagerDuty and on-call routing through ilert, Zenduty and PagerTree, and SMS and voice costs published as credit packs with one voice call equal to two credits and a per-country breakdown in a blog post. Maintenance windows and a 3-of-5 consecutive-request threshold before response-time alerts mute noise. We found no public information on escalation policies with timeouts, on-call schedules and rotations inside the product, or acknowledge and resolve from the app, which is what I need to evidence response times under NIS2. 6 8 13 14 16 22
The Skeptic
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. 5 6 8 14 15 16 22
Status pages & incident communication
Show reasoningHide reasoning
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.
The Agency Developer
Each client can get its own page: from three pages on Solo up to a hundred white-label pages on Team and unlimited on Scale, hosted on a custom subdomain with a certificate issued automatically via Let's Encrypt. Pages carry components fed by monitors, incident and maintenance announcements on a timeline, email subscribers, password protection, eleven languages and embeddable status badges — the agency model is well served. We found no public information on SMS, RSS or webhook subscribers, per-component subscriptions, or single sign-on for private audience pages. 4 8 17 18
The SaaS Platform Engineer
Public pages on a custom subdomain with automatic Let's Encrypt SSL, components fed by monitors, incident and maintenance announcements with a timeline, email subscribers, eleven languages, password protection, white-label and embeddable badges in iframe, Markdown or HTML. We found no public information on subscriber channels beyond email, single sign-on or IP restriction for private pages, or incident templates; the privacy page names Hetzner as hosting the status pages, but the captured pages do not document how the page stays up if the main service goes down. 4 17 18 8 10
The Customer Support Lead
The page runs on our own subdomain with an automatic Let's Encrypt certificate, lists components customers recognise (websites, servers, ports, cron jobs) with uptime bars and percentages, publishes incident and maintenance announcements on a timeline, notifies email subscribers, supports eleven languages, separate pages per audience and password protection for a single account, plus embeddable badges and whitelabel pages. We found no public information on incident templates, subscriber channels beyond email such as RSS or SMS, or single sign-on and IP restriction for private pages. 4 17 18 8 9
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
The Information Security Officer
Public status pages with custom subdomains, automatic Let's Encrypt certificates, components fed by monitors, incident and maintenance timelines, email subscribers, password protection, white-labeling, eleven languages and embeddable badges are documented with per-plan page counts. We found no public information on SMS, RSS or webhook subscribers, single sign-on or IP restriction for private pages, component groups, or how the page hosting stays up if the main service is down. 4 8 9 17 18
The Skeptic
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. 4 8 17 18
API, monitoring as code & team administration
Show reasoningHide reasoning
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.
The Agency Developer
A v3 REST API on every plan including Free covers monitors, alert contacts, maintenance windows and public status pages, with bulk operations, published rate limits, a CLI and even an MCP interface, and Ansible or Terraform can onboard hundreds of monitors as code — that is how I would set up two hundred monitors once. Teammates get read, write, notify-only and admin roles, two-factor is available and required for privileged admins, and monitors group by client so each client can have its own SLA policy. We found no public information on SAML single sign-on, SCIM, audit logs, or per-client sub-accounts with their own logins. 7 8 11 13 19 20
The SaaS Platform Engineer
A v3 REST API covering monitor create/edit/delete, alert contacts, maintenance windows and public status pages, plus a CLI, MCP, bulk operations, OAuth 2.0 and key rotation, and Ansible/Terraform mentioned on the API page for onboarding monitors as infrastructure code — that is most of my wishlist. Team roles (read, write, notify-only), two-factor authentication and seat pricing are documented, but we found no public information on SAML single sign-on, SCIM provisioning, audit logs, or client sub-accounts with their own logins. 7 20 19 8 13
The Customer Support Lead
A version-3 REST API covers creating, editing and deleting monitors, alert contacts, maintenance windows and public status pages, with published rate limits, OAuth 2.0 and key rotation, bulk operations, an official CLI and MCP, and Terraform and Ansible recipes for monitors as code. Team members come in read, write and notify-only roles with two-factor authentication. We found no public information on single sign-on via SAML, SCIM provisioning, audit logs, or sub-accounts where clients get their own logins. 7 20 19 13 6 8 11
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
The Information Security Officer
A REST API covers monitors, alert contacts, maintenance windows and status pages with JSON responses and published rate limits, alongside a CLI, MCP, bulk operations and community Terraform and Ansible tooling; team members get read, write and notify-only roles with two-factor authentication, and 2FA is required for privileged administrative access under the data processing agreement. We found no public information on single sign-on (SAML), SCIM provisioning, customer-facing audit logs or client sub-accounts, which for my ISO 27001 scope is the gap. 7 8 11 13 19 20
The Skeptic
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. 5 7 8 11 19 20
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
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.
The Agency Developer
The monthly uptime report is what I would bill clients against: overall uptime, incident counts, mean time between failures, month-over-month comparison, a response-time summary with peaks above 1,000 ms, and every monitor with daily status bars — plus per-client SLA policies that email a verdict at month or quarter end with the calculation method spelled out. The captured pages give different figures for how far back history reaches, so I checked both the plan table and the reporting article before relying on it. We found no public information on response-time percentiles, probe IP addresses for allow-listing, the vendor's own status page and incident history, or a published SLA with credits. 1 8 21
The SaaS Platform Engineer
Uptime percentage per monitor over 24 hours to 30 days, response time charts with a region selector, and a genuinely documented SLA report: a policy's uptime is the average of its monitors shown to three decimals, maintenance windows are excluded, results are emailed monthly or quarterly, and MTBF is available per monitor and account. The captured pages give different figures for data retention (12 and 24 months on the pricing page, up to 365 days in the help article), and we found no public information on response time percentiles, published probe IP addresses, or the vendor's own status page and incident history. 21 1 8 11 22
The Customer Support Lead
SLA policies calculate uptime against a target with the method stated — the average of monitor uptimes to three decimal places, maintenance windows and paused monitors excluded — and email a monthly or quarterly report with the downtime budget used, MTBF, longest incident and every monitor that had downtime, which is exactly the artefact I can put in front of a contract renewal. Retention is stated per plan at three, twelve and twenty-four months. We found no public information on response-time percentiles, published probe IP addresses, a raw export of check results, or the vendor's own public status page and incident history. 21 8 1 11
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
The Information Security Officer
The SLA feature states its calculation method (average of monitor uptimes to three decimals, maintenance windows excluded), emails monthly or quarterly reports with downtime budget, verdict, MTBF and average incident duration, and states retention of 12 to 24 months by plan; response-time summaries include average, minimum, maximum and peaks above 1000 ms. We found no public information on percentiles or per-phase breakdowns, a raw export of check results, the probe IP addresses for allow-listing, or the vendor's own public status page and incident history. 8 21 22
The Skeptic
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. 1 8 21
European sovereignty
panel opinion
Show reasoningHide reasoning
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.
The Agency Developer
The contract sits with UptimeRobot s. r. o. in Bratislava under Slovak law and the exclusive jurisdiction of the Bratislava courts, with a published data processing agreement carrying the standard contractual clauses, and processing is stated as primarily in the European Union on named infrastructure with Hetzner hosting the monitoring stack and status pages. The full sub-processor list is public — Plivo for SMS and voice, Sendgrid and Amazon SES for mail, Stripe and others for payment — with thirty days' notice of any change and deletion within ninety days of termination. The vendor's own attestation is SOC 2 Type I while the ISO 27001 certificates belong to its infrastructure providers, so I stay at this level rather than higher. 9 10 11 12
The SaaS Platform Engineer
Slovak contracting entity and governing law, a published DPA with Standard Contractual Clauses modules two and three, primary processing in the European Union on named infrastructure, subprocessors listed with their purposes and 30 days' notice of changes, and SOC 2 Type I held by UptimeRobot itself. The chain still runs partly through the United States — named as secondary processing — and through US providers such as Plivo, Sendgrid, Amazon SES, Stripe and Intercom with the SCCs as the stated safeguard, and we found no public information on an ISO 27001 certification for UptimeRobot itself. 9 11 10
The Customer Support Lead
The contracting entity is UptimeRobot s. r. o. of Bratislava under Slovak law, a data processing agreement is published with Standard Contractual Clauses, and processing is stated as primarily in the European Union with the United States as secondary. The subprocessor list names Hetzner for hosting, AWS, Digital Ocean and Limestone Networks for monitoring requests, Cloudflare, Plivo for SMS and voice, Sendgrid and Amazon SES for email, Stripe, 2Checkout, PayPal and Airwallex for payments, and Intercom for support; deletion within ninety days of termination, backup erasure within one hundred eighty days and written deletion certification are documented. The vendor itself holds SOC 2 Type I while its infrastructure providers hold SOC 2 Type II and ISO 27001. 11 10 9
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
The Information Security Officer
The contracting entity is UptimeRobot s. r. o. of Bratislava under Slovak law, with a published data processing agreement (version 2.2) carrying SCC Modules Two and Three, a subprocessor list with purposes (Hetzner, AWS, Digital Ocean, Limestone Networks, Cloudflare, Plivo, SendGrid, Stripe, Intercom and others), 30-day change notice and deletion certification within 90 days — a chain I can put in front of an auditor. Processing is stated as primarily in the European Union with a secondary United States location for the infrastructure providers, the individual subprocessors' own seats are not stated per company, and the vendor's own certification is SOC 2 Type I while the ISO 27001 certificates belong to its providers. 9 10 11
The Skeptic
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. 9 10 11
Pricing transparency
Show reasoningHide reasoning
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.
The Agency Developer
I can plan the money from public pages: the free tier's fifty monitors at five-minute intervals are stated, Scale lists 200 or 500 monitors and "Starts at €660 /y" with a fifteen-second interval, and SMS and voice alerts are priced in credit packs from $3 for 10 credits with a per-country list for SMS. Login seats add for $15/19 / mo and the included credit volume per plan is published. The Team plan's monitor count is not shown on the captured pricing page, extra monitors are sold as an upgrade without a captured unit price, and we found no public information on VAT treatment. 8 9 16 17
The SaaS Platform Engineer
Tiers are public down to the interval, monitor count, seats, status page limits and retention, SMS and voice credits are priced in five packs with two credits per voice call and country variation documented, extra seats carry a monthly price, and annual billing saves roughly 15 percent. The Solo and Scale prices are marked as starting prices without a full per-monitor scaling rule, auto-refill silently switches off if the card charge fails, and we found no public information on VAT treatment — so a buyer cannot yet compute the exact final invoice. 8 16 9
The Customer Support Lead
Tier prices are public — €0 for fifty monitors at five-minute intervals, Solo starting at €108/y, Team at €360/y and Scale starting at €660/y — with each tier's interval, status page count, seats, retention and included SMS or voice credits listed, annual billing saving roughly fifteen percent, extra login seats at $15/19 a month, and credit packs from $3 for 10 SMS or voice call credits with per-country variation referenced and the auto-refill behaviour, including what happens when a refill fails, documented. We found no public information on VAT treatment or the price of extra monitors beyond a tier, and Enterprise pricing is a custom quote. 8 16 9
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
The Information Security Officer
All tiers are public with monitor counts, intervals, seats and status pages (Free €0, Solo starts at €108/y, Team €360/y, Scale starts at €660/y, Enterprise by quote), extra login seats cost $15 or $19 a month, credit packs run from $3 for 10 to $100 for 1000 with auto-refill behavior documented, and cancellation carries a 14-day withdrawal period. The per-country SMS cost list sits in a blog post rather than the pricing page, and we found no public information on VAT treatment or the price of extra monitors and shorter intervals as standalone upgrades. 8 9 16
The Skeptic
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. 8 9 16
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| 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
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
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.
- 23 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 15 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 8 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (23)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage uptimerobot.com Checked 1 Nov 2026 Details →
- 2 Features page (SSL monitoring) uptimerobot.com Checked 1 Nov 2026 Details →
- 3 Features page (cron job monitoring) uptimerobot.com Checked 1 Nov 2026 Details →
- 4 Features page (status pages) uptimerobot.com Checked 1 Nov 2026 Details →
- 5 Features page (alerting) uptimerobot.com Checked 1 Nov 2026 Details →
- 6 Integrations page uptimerobot.com Checked 1 Nov 2026 Details →
- 7 API documentation uptimerobot.com Checked 1 Nov 2026 Details →
- 8 Pricing page uptimerobot.com Checked 1 Nov 2026 Details →
- 9 Terms of service (names the operating company) uptimerobot.com Checked 1 Nov 2026 Details →
- 10 Privacy policy uptimerobot.com Checked 1 Nov 2026 Details →
- 11 Data processing agreement (dpa) uptimerobot.com Checked 1 Nov 2026 Details →
- 12 Security / trust page uptimerobot.com Checked 1 Nov 2026 Details →
- 13 Checks, locations & failure confirmation — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
- 14 Checks, locations & failure confirmation — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
- 15 Alerting, escalation & on-call — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 16 Alerting, escalation & on-call — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 17 Status pages & incident communication — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 18 Status pages & incident communication — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 19 API, monitoring as code & team administration — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 20 API, monitoring as code & team administration — found from sitemap uptimerobot.com Checked 1 Nov 2026 Details →
- 21 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 22 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimerobot.com Checked 1 Nov 2026 Details →
- 23 Self-hosting / on-premises installation docs — found from the homepage uptimerobot.com Checked 1 Nov 2026 Details →