Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

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

by Uptime.com · uptime.com

Report an error on this page Is this your product? →

Link to this page

Uptime.com: AI-assisted analysis on whats-best.ai Uptime.com: 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.

Uptime.com at a glance

Vendor
Uptime.com
Headquarters
Incorporated in the United States source, captured 17 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 17 Nov 2026
Free plan
Not stated on the vendor’s pages as of 17 Nov 2026
Panel verdict
The AI panel rates Uptime.com 2.5/5, the mean of 6 judges. Uptime.com, an uptime monitoring and status page service, scored highest on checks and locations at 6-7, for real-browser synthetic checks of critical flows, API, heartbeat and cron monitoring, private locations, and an 80+ location probe network with IPv4 and IPv6 support, with failures double-checked from multiple locations before alerting. how scores are made
As of
Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources

Uptime.com alternatives, European ones first →

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

The panel's verdict

Uptime.com, an uptime monitoring and status page service, scored highest on checks and locations at 6-7, for real-browser synthetic checks of critical flows, API, heartbeat and cron monitoring, private locations, and an 80+ location probe network with IPv4 and IPv6 support, with failures double-checked from multiple locations before alerting. Alerting scored 6 across the bench — email, SMS, voice, mobile push, Slack, Microsoft Teams, PagerDuty, Opsgenie, Splunk On-Call and webhooks — with no public information on on-call rotations, alert acknowledgement or SMS and call costs. Status pages scored 4-5 and sovereignty a uniform 4: we found no public information on custom domains, subscriber channels or per-component uptime history, and the pages describe a Delaware company, United States processing, and a subprocessor list naming AWS, Twilio, SendGrid, Zendesk and Braintree. Automation and teams and reports and reliability scored 4-5, with retention, raw export and probe IP addresses for allow-listing unpublished. The flagged splits show none; no criterion varies by more than a point. Pricing transparency scored 2-3, with no plan prices public beyond a 14-day free trial requiring no credit card.

Report an error

Speaks for it

  • Synthetic real-browser checks of critical flows, API, heartbeat and cron monitoring, and private location monitoring, on an 80+ location probe network supporting IPv4 and IPv6.
  • Web checks are double-checked from multiple locations before alerting, and maintenance windows suppress notifications to reduce false positives.
  • Alerts go out by email, SMS, mobile push and voice call, plus Slack, Microsoft Teams, webhooks, PagerDuty, Opsgenie and Splunk On-Call, with escalation by severity or seniority and 20+ integrations in all plans.
  • A documented REST API offering the functionality of the web interface plus automated reporting, with a changelog, webhooks and rate limits of 500 calls per hour and 60 per minute.
  • Customizable uptime, page speed and SLA reports shareable with anyone, scheduled by day, week, month, quarter or year, with checks grouped by service, customer and geography.

Report an error

Held against it

  • The shortest check interval is not stated, and keyword, ping, port, SSL, DNS and domain-expiry checks are left undescribed on the captured pages.
  • No public information on on-call schedules and rotations, acknowledging or resolving from the app, alert grouping, or the cost of SMS and phone alerts.
  • No public information on status page custom domains, subscriber notification channels, components fed by monitors, or uptime history per component.
  • No public information on single sign-on, two-factor authentication, SCIM, audit logs, member roles or bulk import for team administration.
  • Contracting with Uptime.com LLC, a Delaware limited liability company, with the privacy policy stating data is transferred to and processed in the United States and subprocessors for SMS and voice, email, support and payments listed with United States locations.

Report an error

Best for

  • You run an online store or SaaS and need real-browser checks on checkout and other critical flows, confirmed from multiple locations before an alert fires.
  • You owe clients or key accounts recurring SLA and uptime reports, grouped by customer or geography.
  • You already run PagerDuty, Opsgenie, Splunk On-Call, Slack or Microsoft Teams and want alerts and reporting wired in through a REST API and webhooks.
  • You monitor cron jobs and heartbeats alongside websites and APIs, including from your own private locations.

Report an error

Avoid if

  • You require European hosting or an EU contracting entity — the captured pages describe a Delaware company, United States processing, and subprocessors for SMS and voice, email, support and payments listed with United States locations.
  • You expect prepaid fees to be refundable — the terms state paid fees are non-refundable and the entire initial term may be charged on order submission.
  • You want to evaluate the API before committing — browsable API and API token access are limited to paid customers.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.

Checks, locations & failure confirmation

Show 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.

Report an error

The Agency Developer

Probe locations are listed by city — 80+ worldwide with IPv4/IPv6 and region filters — and the alerting page states web checks are double-checked from multiple locations with maintenance windows to cut false positives, which is the confirmation behaviour I want before waking a client. Website, API, synthetic browser and heartbeat or cron monitoring, plus private location monitoring, are all documented modules. I found no public information on keyword checks, SSL certificate expiry, domain expiry or DNS checks, and the shortest check interval is never stated, so the exact checks my sixty WordPress, TYPO3 and Shopware sites need are not confirmed. 1 5 6 7 10

Report an error

The SaaS Platform Engineer

Synthetic browser checks of critical user flows, API monitoring, heartbeat and cron checks and private location monitoring are all named as platform modules, with a probe network described as 80+ locations across six regions, IPv4/IPv6 shown per location and eight city-named transaction locations. Failures are double-checked from multiple locations before alerting and designated windows suppress notifications, which is exactly the false-positive control I want — but check intervals, DNS and domain expiry checks, and assertions on API responses are not described in anything I read. 1 5 6 7

Report an error

The Customer Support Lead

They run heartbeat and cron job monitoring, real-browser synthetic checks of critical flows, and an 80+ probe network listed by city with IPv4 and IPv6, and they state that a failure is double-checked from multiple locations before alerting with maintenance windows that suppress checks — that confirmation logic is what keeps my nine people off false alarms. We found no public information on keyword, ping, TCP or SSL expiry checks, on the shortest check interval, or on DNS and domain expiry checks. 1 5 6 7

Report an error

The E-Commerce Operations Manager

Synthetic monitoring with real browser tests of the website's critical flows is exactly what I want on the checkout and payment page, and private locations, heartbeat or cron checks, over 80 probe locations listed by city with IPv4 and IPv6, a second-location double-check before alerting and maintenance windows are all documented. What holds me back: the shortest check interval is not stated, and keyword, DNS, domain expiry, ping and port checks are not described on the pages we read. 1 5 6 7 10

Report an error

The Information Security Officer

Synthetic browser checks of critical flows, API monitoring, heartbeat or cron monitoring, private location monitoring and a probe network of more than 80 locations listed by city with IPv4 and IPv6 support give the breadth I look for, and the documented double-check from multiple locations before alerting is exactly the detection reliability an auditor questions. The captured pages leave the shortest check interval and the basic check types — keyword, ping, port, SSL and DNS — undescribed, which holds it below the top tier. 1 5 6 7

Report an error

The Skeptic

The breadth is real: synthetic browser checks of critical flows, heartbeat and cron monitoring with alerts on a missed signal, API monitoring, private location monitoring, and 80+ probe locations listed by city and region with IPv4 and IPv6 support, with a documented double-check from multiple locations before alerting and suppression during maintenance windows. But we found no public information on the check interval — the single number that determines how fast a failure is seen — and the classic check types (keyword, SSL expiry, DNS and domain expiry) are never itemized, so detection speed and coverage can only be taken on faith. 1 5 6 7

Report an error

Alerting, escalation & on-call

Show 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.

Report an error

The Agency Developer

Email, SMS, phone calls and mobile push are documented, alongside Slack, Microsoft Teams, PagerDuty, Opsgenie, Splunk On-Call and webhooks, with escalations set by severity or seniority and maintenance windows that suppress alerts. I found no public information on on-call schedules and rotations, acknowledging or resolving from the app, alert grouping, or what SMS and calls cost — with sixty client sites I cannot budget alerts blind. 7 12

Report an error

The SaaS Platform Engineer

Alerts go out by email, SMS, voice call, mobile push, Slack, Microsoft Teams and webhooks, forward to PagerDuty, Opsgenie and Splunk On-Call, and contacts can be designated with escalation by severity or seniority. I found no public information on escalation timeouts, on-call schedules or rotations, acknowledging and resolving from the app or chat, or what SMS and phone calls cost. 7 12

Report an error

The Customer Support Lead

Alerts go out by email, SMS, phone call and mobile push, with Slack, Microsoft Teams, PagerDuty, Opsgenie and Splunk On-Call among 20+ integrations, and contacts can be designated with escalations by severity or seniority — a real spine for an on-call rota. We found no public information on on-call schedules and rotations, acknowledging and resolving from the app, alert grouping, recovery notifications, or what SMS and phone alerts cost. 7 12 1

Report an error

The E-Commerce Operations Manager

SMS, phone calls, email and mobile push notifications are all listed, with escalation by severity or seniority and forwarding to PagerDuty, Opsgenie, Splunk On-Call, Slack and Microsoft Teams — that covers an SMS or a call to whoever is on duty at night. We found no public information on on-call schedules and rotations, acknowledging from the app, alert grouping, incident timelines, or the price of SMS and calls. 5 7 12

Report an error

The Information Security Officer

Alerts go out by email, SMS, mobile push and voice call, plus Slack, Microsoft Teams, webhooks, PagerDuty, Opsgenie and Splunk On-Call, with escalation by severity or seniority and suppression during designated maintenance windows. I found no public information on on-call schedules and rotations, acknowledging and resolving from the app, alert grouping, incident timelines, or the per-country price of SMS and calls — the parts I would need before entrusting an on-call rota to it. 7 12

Report an error

The Skeptic

The channel list is broad — email, SMS, mobile push, voice call, Slack, Microsoft Teams, webhooks, and forwarding to PagerDuty, Opsgenie and Splunk On-Call — with contacts designated per alert and escalations set by severity or seniority, plus maintenance windows that mute alerts. But we found no public information on on-call schedules and rotations, acknowledging or resolving from the app, alert grouping, recovery notifications, or what an SMS or phone call costs — the last one being exactly where 'unlimited' tends to hide a fair-use clause. 7 12

Report an error

Status pages & incident communication

Show 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.

Report an error

The Agency Developer

Public and private page types, customizable branded pages with real-time updates on outages and maintenance, and communication of third-party dependency status are all documented. I found no public information on custom domains, subscriber channels, component groups, or uptime history per component — the pieces I need to hand each of my clients their own page under our name. 1 9 13

Report an error

The SaaS Platform Engineer

Status pages exist for public and private audiences with real-time updates on outages and maintenance, branding, subscription management and interaction through the API, which covers my 3 a.m. requirement of a page that updates itself. Custom domains, components linked to monitors, subscriber channels and per-component uptime history are not described in the pages I read. 1 9 13

Report an error

The Customer Support Lead

Public and private status pages with real-time updates on outages and maintenance, subscriber management and branded pages cover the core of what my team needs during an outage, and the private page option answers my requirement for our largest accounts. We found no public information on hosting the page on our own domain, incident templates, which channels subscribers are notified through, component groups fed by monitors, or per-component uptime history I could point to at a renewal. 9 1 13

Report an error

The E-Commerce Operations Manager

Branded public and private status pages with real-time updates on outages and maintenance, subscription management, an API and third-party dependency status are documented. We found no public information on custom domains, components fed automatically by monitors, uptime history per component, subscriber channels, or how the status page itself stays online when the main service is down. 1 9 10 13

Report an error

The Information Security Officer

Branded, customizable status pages carry real-time outage and maintenance updates to both public and private audiences, with subscriber management and third-party dependency status. The captured pages do not show custom domains, components linked to monitors, uptime history per component, or which channels subscribers can be notified through. 1 9 13

Report an error

The Skeptic

Branded hosted status pages for public and private audiences are documented, with real-time updates on outages and maintenance, subscription management, and communication of third-party dependency status. But we found no public information on custom domains, components fed automatically by monitors, subscriber channels, per-component uptime history, or how the status page itself stays online when the main service is down — the question that has burned buyers before. 1 9 13

Report an error

API, monitoring as code & team administration

Show 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.

Report an error

The Agency Developer

The REST API is documented with a changelog and is described as offering the functionality of the full UI plus automated reporting, webhooks are available, and checks can be grouped by services, customers and geographies — grouping by customer is exactly how I would organise sixty sites. API access is limited to paid customers, and I found no public information on team roles, two-factor authentication, single sign-on, audit logs, bulk monitor import or monitoring-as-code. 11 12 13

Report an error

The SaaS Platform Engineer

There is a documented REST API described as offering the functionality of the full UI plus automated reporting, with a changelog, token access limited to paid customers and rate limits of 500 calls per hour, alongside webhooks, 20+ integrations and reports segmentable by users and teams. I found no public information on a Terraform provider, monitoring as code, CI/CD checks, SAML single sign-on, SCIM, audit logs, roles or two-factor authentication — and my checks would have to live outside version control. 9 11 12 13

Report an error

The Customer Support Lead

A documented REST API described as offering the functionality of the Uptime UI plus automated reporting, status pages reachable by API, webhooks, and a wide set of chat and alerting integrations would let us wire incidents into our own tooling. We found no public information on Terraform or monitoring-as-code, checks triggered from CI/CD, bulk import, single sign-on, SCIM, audit logs, two-factor authentication, or team roles beyond dashboards segmentable by users and teams. 11 12 9 13

Report an error

The E-Commerce Operations Manager

The REST API is documented as offering the functionality of the full interface plus automated reporting, with an API changelog, rate limits, webhooks and more than twenty integrations available in all plans. We found no public information on team member roles, single sign-on, SCIM provisioning, audit logs, bulk import of monitors, or a monitoring-as-code workflow. 11 12 13

Report an error

The Information Security Officer

A documented REST API offering the functionality of the web interface plus automated reporting, webhooks, an API changelog and published rate limits cover automation well, and dashboards and reports can be segmented by users and teams. For team administration I found no public information on single sign-on, audit logs, two-factor authentication, member roles or bulk import — the controls I require before anyone in my company gets a login. 9 11 12 13

Report an error

The Skeptic

A documented REST API is advertised as offering "the functionality of the Uptime UI plus automated reporting", with API docs, a changelog, published rate limits of 500 calls per hour and 60 per minute, webhooks and 20+ integrations — though API access is paid-customers-only. We found no public information on Terraform or monitoring-as-code, single sign-on, SCIM, audit logs, two-factor authentication or bulk import; teams appear only as a way to segment dashboards and reports, with no roles described. 1 11 12 13

Report an error

Uptime reports, data & the vendor's own reliability

Show 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.

Report an error

The Agency Developer

Customizable uptime, page speed and SLA reports shareable with anyone, checks grouped by customer for SLA accountability, and scheduled delivery by day, week, month, quarter or year via automated report links or API cover the monthly client reports I send out. I found no public information on how long check results are retained, raw export of results, published probe IP addresses for allow-listing, the vendor's own status page and incident history, or an SLA with credits. 5 13

Report an error

The SaaS Platform Engineer

Reports on uptime, page speed and SLA performance can be customised and shared, scheduled by day, week, month, quarter or year, delivered via automated report links or API, and checks can be grouped by service, customer and geography for SLA accountability. Retention of check results, raw export formats, published probe IP addresses for allow-listing and the vendor's own status page and SLA were not described in what I read. 5 8 13

Report an error

The Customer Support Lead

Scheduled reports by day, week, month, quarter or year delivered via automated report links or API, customizable uptime, page speed and SLA reports shareable with anyone, and checks groupable by service, customer and geography give me the SLA accountability document I take into a contract renewal. We found no public information on how long check results are kept, raw export, published probe IP addresses for allow-listing, the vendor's own status page and incident history, or an SLA with credits. 13 8

Report an error

The E-Commerce Operations Manager

Customizable uptime, page speed and SLA reports shareable with anyone, checks grouped by customer or geography for SLA accountability, and scheduled delivery by day, week, month, quarter or year come close to the report I owe the agency after an outage. We found no public information on how long check history is kept, raw result export, the probe IP addresses for allow-listing, or the vendor's own status page and service credits. 5 8 13

Report an error

The Information Security Officer

Scheduled reports at day, week, month, quarter or year intervals, uptime and SLA performance reporting shareable with anyone, checks grouped by service, customer and geography for SLA accountability, and per-check response time figures give a usable operational record. The retention period for check results, a raw export of results, the probe IP addresses for allow-listing, and the vendor's own public status page are not documented on the captured pages, so this does not yet meet my audit-grade standard. 8 12 13

Report an error

The Skeptic

Reporting is genuinely covered: customizable uptime, page speed and SLA reports, scheduled by day through year and delivered via automated report links or API, shareable, groupable by service, customer and geography. But the retention period of check results is not stated, a raw export of results beyond report delivery is not described, probe IP addresses for allow-listing are not published (only IPv4/IPv6 support flags), and we found no public information on the vendor's own status page, incident history or an SLA with credits — the warranty remedy is a refund of one month's fees, capped at twelve months' fees overall. 2 6 13

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The Agency Developer

The contracting entity is Uptime.com LLC, a Delaware company, and the privacy policy states that data is transferred to the United States and processed there; the published subprocessor list shows Amazon Web Services for hosting, Twilio for SMS and voice, SendGrid for email, Zendesk for support and Braintree for payments, with locations given as United States for nearly all of them. A GDPR page, a Data Processing Addendum link and a DPO contact at dpo@uptime.com exist, so the paperwork is there, but I found no public information on European hosting or an EU contracting entity — for a European agency this chain runs through the US end to end. 2 3 4

Report an error

The SaaS Platform Engineer

The contracting entity is Uptime.com LLC, a Delaware company with Delaware governing law and Florida venue, the privacy policy states data is transferred to and processed in the United States, and the published subprocessor list is almost entirely US-based including AWS for hosting, Twilio for SMS and voice, SendGrid for email, Zendesk for support and Braintree for payment. A Data Processing Addendum, a GDPR page, breach notification and a DPO contact exist, but the captured pages give no evidence of EU hosting or an EU contracting entity, so my on-call team's phone numbers would sit in a US chain. 2 3 4

Report an error

The Customer Support Lead

The contracting entity is Uptime.com LLC, a Delaware company, the privacy policy states data is transferred to and processed in the United States, and a published subprocessor list names AWS for hosting and Twilio, SendGrid and Zendesk for SMS, email and support, all in the United States or global. GDPR paperwork exists — a data processing addendum, a GDPR page, a DPO contact and written breach notification — but we found no public information on EU hosting, an EU contracting entity or representative, or security certifications. 2 3 4

Report an error

The E-Commerce Operations Manager

The contracting entity is a Delaware company, the privacy policy states personal data is transferred to and processed in the United States, and the published subprocessor list names hosting on AWS, SMS and voice via Twilio, email via SendGrid, support via Zendesk and payments via Braintree — United States providers — alongside a data processing addendum and a GDPR page. It is a transparent chain, but an entirely American one; we found no public information on a European hosting option, an EU contracting entity, or a self-hosted edition. 2 3 4

Report an error

The Information Security Officer

The subprocessor list is published with names and locations and updated on 20 March 2026, alongside a data processing agreement, a GDPR page with a DPO contact and written breach notification — more chain transparency than the minimum. But the contracting entity is a Delaware company, the privacy policy states all data is transferred to and processed in the United States, and every subprocessor from hosting through the Twilio SMS and voice gateway to support and payment is United States based, with no European hosting, European entity or stated ISO 27001 or SOC 2 certification, so the on-call staff's mobile numbers and status page subscribers would rest entirely with US processors. 2 3 4

Report an error

The Skeptic

The chain is consistently American: a Delaware limited liability company under Delaware law, data transferred to and processed in the United States, and a subprocessor list — published, dated, with an update-notification contact — in which hosting (AWS), SMS and voice (Twilio), email delivery (SendGrid), support (Zendesk) and payments (Braintree) are all listed as United States. A DPA, a GDPR page and a DPO contact exist, which is more transparency than many US vendors offer, but the captured pages state no EU hosting option and no EU contracting entity anywhere in the chain. 2 3 4

Report an error

Pricing transparency not rated — the vendor publishes no price

Show 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.

Report an error

The Agency Developer

A 14-day free trial with no credit card required is documented, the terms state fees are in United States Dollars excluding sales tax and VAT, and synthetic and API monitors plus 20+ integrations are said to be in all plans. Beyond that I found no public information on plan prices, per-monitor cost, check intervals per tier, seats, or SMS and call charges, so I cannot compute what two hundred monitors would cost my agency per year. 1 2 8

Report an error

The SaaS Platform Engineer

The only price-adjacent facts are a 14-day free trial with no credit card required, fees in US dollars, the entire initial term chargeable on order submission, prepaid fees non-refundable, taxes excluded from stated fees, and API access reserved for paid customers — no tier prices, per-monitor figures, seat or responder prices, or SMS and call costs are shown on any page I read, so I cannot compute an annual cost. 1 2 8 11

Report an error

The Customer Support Lead

A 14-day free trial with no credit card is public, along with the currency ("fees are stated and must be paid in United States Dollars"), tax treatment (stated fees exclude sales tax and VAT), the default one-month term, and rules on fee increases and refunds, and synthetic and API monitors and 20+ integrations are stated for all plans. We found no public information on tier prices, monitor counts or check intervals per tier, seat prices, or what SMS and phone alerts cost, so an annual cost cannot be computed from the captured pages. 8 2 1 11

Report an error

The E-Commerce Operations Manager

A 14-day free trial without a credit card, synthetic and API monitors in all plans, billing in US dollars with taxes excluded and a one-month default term are public. We found no public information on any plan price, on how cost scales with monitors, interval, seats or alert volume, or on what SMS and phone alerts cost, so I cannot compute our annual spend before the March season. 1 2 8

Report an error

The Information Security Officer

Public commercial facts are limited to a 14-day free trial without a credit card and contractual mechanics: fees in United States dollars, VAT and sales tax excluded and payable by the customer, the entire initial term chargeable on order submission, fees non-refundable, and a one-month default term. The captured pages give no plan prices, no scaling by monitors, interval or seats, and no cost for SMS or phone alerts, so a real annual cost cannot be computed from them. 1 2 8

Report an error

The Skeptic

What is public: a 14-day free trial with no credit card, "Synthetic & API monitors for all plans", "20+ integrations for all plans", and contract cost terms — the entire initial term may be charged upfront by default, fees are non-refundable, stated fees exclude sales tax and VAT, and fees may increase at renewal. But we found no public prices for any tier and no scaling rule by monitors, interval, seats or alert volume, so a buyer cannot compute an annual cost from the captured pages alone. 1 2 8

Report an error

European sovereignty — proven facts

2 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 unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Hosting options Not determined — uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Published, self-serve unverified
Why unverified?

Excerpts show only a footer link named 'Data Processing Addendum' and an in-text reference; the agreement text itself or an online conclusion mechanism is not included.

1/1 pts 4 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Uptime.com

Is Uptime.com European?

Not determined: the vendor’s pages as captured do not say where Uptime.com is based. Its vendor, Uptime.com, is incorporated in the United States, per the vendor’s page captured 17 Nov 2026.

Where does Uptime.com store data?

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

Does Uptime.com have a free plan?

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

What are the best alternatives to Uptime.com?

As of 19 Nov 2026, the panel rates Hyperping (3.5/5), Uptimia (3.5/5) and Checkly (3.5/5) highest among the other 23 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, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Uptime.com 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.

Sources (13)

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

  1. 1 Vendor page uptime.com Checked 17 Nov 2026 Details →
  2. 2 Terms of service — found from the homepage uptime.com Checked 17 Nov 2026 Details →
  3. 3 Privacy policy — found from the homepage uptime.com Checked 17 Nov 2026 Details →
  4. 4 Subprocessor list — found from the homepage uptime.com Checked 17 Nov 2026 Details →
  5. 5 Checks, locations & failure confirmation — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  6. 6 Checks, locations & failure confirmation — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  7. 7 Alerting, escalation & on-call — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  8. 8 Alerting, escalation & on-call — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  9. 9 Status pages & incident communication — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  10. 10 Status pages & incident communication — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  11. 11 API, monitoring as code & team administration — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  12. 12 API, monitoring as code & team administration — found from sitemap uptime.com Checked 17 Nov 2026 Details →
  13. 13 Uptime reports, data & the vendor's own reliability — found from sitemap uptime.com Checked 17 Nov 2026 Details →