Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: not determined

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

by Uptrends B.V. · www.uptrends.com

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

Link to this page

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

Uptrends at a glance

Vendor
Uptrends B.V.
Headquarters
Not stated on the vendor’s pages as of 10 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates Uptrends 3/5, the mean of 6 judges. Uptrends B.V., an uptime monitoring and status page service, is strongest where the bench scored it highest — checks and locations at 7-8 — with multi-step checks in real browsers covering MFA and SSO journeys from 230+ ISP-based checkpoints worldwide or private locations, and an alert raised only after a second checkpoint duplicates the error. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Uptrends alternatives, European ones first →

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

The panel's verdict

Uptrends B.V., an uptime monitoring and status page service, is strongest where the bench scored it highest — checks and locations at 7-8 — with multi-step checks in real browsers covering MFA and SSO journeys from 230+ ISP-based checkpoints worldwide or private locations, and an alert raised only after a second checkpoint duplicates the error. Alerting and on-call and automation and teams follow, backed by a documented Monitor API and a Terraform provider with Git-based version control, though Terraform is for Enterprise-level accounts. Status pages is the weakest area at 4, and we found no public information on custom domains, subscriber notifications or incident updates. The judges genuinely split on sovereignty, 0 to 3: the 3 credits the Dutch company form on record, while the 0s record no public information on data storage locations, subprocessors or a data processing agreement. Reports and reliability clusters at 6 with retention stated per plan; the captured pages give different figures — three and four — for the maximum number of escalation levels, and show no price figures.

Report an error

Speaks for it

  • Checks and locations scored the highest cluster at 7-8 for multi-step, real-browser journey checks covering MFA and SSO from 230+ ISP-based checkpoints worldwide.
  • An alert sounds only after a different checkpoint duplicates the error, and maintenance windows suppress checks.
  • A documented Monitor API with create, update, clone and delete, plus a Terraform provider with Git-based version control, manage monitors as code.
  • Retention is published per plan and data type — individual check data 14 to 90 days, statistical SLA data up to two years.
  • Alerting spans email, SMS, phone/voice, mobile push, webhooks and forwarding to PagerDuty, Opsgenie and Splunk On-Call.

Report an error

Held against it

  • Status pages drew the lowest scores at 4, with no public information found on custom domains, subscriber notifications or incident updates.
  • Protected status pages and Terraform support sit on the Enterprise plan, and SLA monitoring on Business and Enterprise.
  • Sovereignty scores split 0 to 3, with no public information on data storage locations, subprocessors or a data processing agreement.
  • The captured pages give different figures for the maximum number of escalation levels — three and four.
  • No price figures for the five named tiers appear on the captured pages, though a 30-day free trial without credit card is offered.

Report an error

Best for

  • You watch checkout, payment or MFA/SSO login journeys end to end and want alerts confirmed from a second checkpoint before anyone is paged.
  • You manage monitoring as code and want a documented Monitor API plus a Terraform provider with Git-based version control and an import workflow.
  • You need SLA evidence to hand a customer or agency, with statistical uptime and calculated SLA data kept up to two years and individual check data up to 90 days.

Report an error

Avoid if

  • Your procurement must see documented data residency, subprocessors or a data processing agreement before signature.
  • Your security sign-off depends on account-level single sign-on, SCIM provisioning or audit logs being documented up front.
  • Your customer communication during outages leans on status page subscriber notifications, custom domains or per-component uptime history.

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

The HTTP(S) monitor is documented end to end — DNS resolution, TCP connection on port 80, 443 or a custom port, status codes, page load time and content-resource loading — run from 230+ ISP-based checkpoints worldwide, with a re-test from a different checkpoint before an alert is raised, plus private monitoring locations, real-browser transaction checks, low-code multi-step checks and maintenance windows. We found no public information on SSL certificate expiry or domain expiry monitoring, keyword checks as such, cron or heartbeat monitors, the shortest check interval, or a city-level checkpoint list — and certificate expiry is exactly what once cost me an angry client call. 1 2 3 5

Report an error

The SaaS Platform Engineer

A failed check is retried from a different checkpoint and only a duplicated error raises an alarm, and that confirmation logic is spelled out step by step — exactly what I want before anyone's phone rings at 3 a.m. Multi-step checks with low-code setup, real-browser journeys that cover MFA and SSO, 230+ ISP-based checkpoints, private locations and maintenance windows are all on the record. We found no public information in the captured pages on the shortest check interval or a city-by-city checkpoint list. 1 2 3 5

Report an error

The Customer Support Lead

Multi-step low-code checks, real commercial browsers, journeys through MFA or SSO logins, 230-plus ISP-based checkpoints worldwide, private locations and maintenance windows are all documented, and the confirm-from-a-second-checkpoint policy is described step by step including DNS resolution, TCP ports and traceroute. We found no public information on the shortest check interval, SSL certificate expiry checks or cron and heartbeat monitoring, which keeps it shy of the top band. 1 2 3 5

Report an error

The E-Commerce Operations Manager

HTTP(S) checks with status codes, DNS resolution, custom TCP ports, ICMP traceroute on network errors, and multi-step low-code checks in real commercial browsers — including user journeys with MFA or SSO — cover exactly the checkout and payment flows I need watched, and an error is only alerted after a second checkpoint duplicates it. The 230+ ISP-based checkpoints worldwide plus my own private locations are strong, but the captured pages never state the shortest check interval, and certificate expiry, domain expiry and DNS record checks are not described. 1 2 3 5

Report an error

The Information Security Officer

The knowledge base documents HTTPS checks with status codes, load times and content-resource loading, TCP connections on standard or custom ports, and multi-step, real-browser transaction checks that can exercise MFA and SSO journeys end to end, run from 230+ ISP-based checkpoints worldwide or from the customer's own private locations. Failure confirmation is spelled out: a re-test from a different checkpoint must duplicate the error before an alert sounds, planned maintenance suppresses checks, and a traceroute with ICMP packets runs on network errors. We found no public information on DNS record or certificate-expiry check types, the shortest check interval, or a city-level list of checkpoint locations, which caps this short of the top marks. 1 2 3 5

Report an error

The Skeptic

The failure-confirmation story is unusually well documented: a failed check is retried, and an alert only fires when a second, different checkpoint duplicates the error, with security-protocol retries and an automatic traceroute on network errors. HTTP(S) with status codes and content checks, custom-port TCP, multi-step low-code checks, real browsers, private locations and 230+ ISP-based checkpoints worldwide are all evidenced; we found no public information on check intervals, a city-level checkpoint list, or SSL-certificate and domain-expiry checks. 1 2 3 5

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/voice, iOS and Android push, webhooks and forwarding to PagerDuty, Opsgenie, Splunk On-Call and ServiceNow are all documented, with escalation levels driven by error duration or error count, operator duty shifts, recovery alerts, alert testing and maintenance windows that suppress alerts; the captured pages give different figures for the number of escalation levels (three on one page, four on another). SMS and voice are stated to use message credits, though the credit price is not stated, and we found no public information on acknowledging and resolving from the app, alert grouping or incident timelines. 4 5

Report an error

The SaaS Platform Engineer

Email, SMS, phone and voice, mobile push and webhooks are all listed, with escalation levels triggered by error duration or error count and operator duty shifts deciding who is paged, plus routing to PagerDuty, Opsgenie and Splunk On-Call. Recovery (OK) messages, reminders and alert testing are controllable, and maintenance windows stop alerts during planned work. SMS and voice use "message credits" whose price the captured pages do not state, we found no public information on acknowledging or resolving from the app, and the captured pages give different figures for the maximum number of escalation levels (three versus four). 4 5

Report an error

The Customer Support Lead

Email, SMS, phone and voice, mobile push apps, Slack, Microsoft Teams, webhooks and forwarding to PagerDuty, Opsgenie and Splunk On-Call are documented, together with duty shifts, maintenance windows that mute alerts, recovery messages and escalation levels driven by error duration or count; the captured pages give different figures for the maximum number of escalation levels. We found no public information on acknowledging and resolving from the app, alert grouping, or the price of SMS and calls beyond a message-credits system with no stated rate. 4 5

Report an error

The E-Commerce Operations Manager

Email, SMS, phone/voice, push via the iOS and Android apps, chat, webhooks and forwarding to PagerDuty or Opsgenie are all routed by operator duty shifts so the person on call that night gets the message, with escalation levels triggered by error duration or count (the captured pages give different figures for the maximum number of levels, three versus four), plus alert testing, recovery messages and maintenance windows. What holds it back: SMS and phone alerts "use message credits" whose price is never stated, and acknowledging or resolving an incident from the app is not described. 1 4 5

Report an error

The Information Security Officer

Email, SMS and phone/voice alerts, iOS and Android push, Slack, Microsoft Teams, webhooks and forwarding to PagerDuty, Opsgenie and Splunk On-Call are documented, together with operator duty shifts, maintenance windows that suppress alerts, recovery ("OK") notifications and the ability to test that messages send. Escalation levels trigger by error duration or error count with reminders and recipient changes, though the captured pages give different figures for the maximum number of levels — three in one article, four on another — and I have not chosen between them. We found no public information on acknowledging and resolving from the app, alert grouping, or the price of SMS and phone messages beyond the statement that they "use message credits". 4 5

Report an error

The Skeptic

Email, SMS, phone and voice, mobile push apps, Slack and Microsoft Teams, webhooks and forwarding to PagerDuty, Opsgenie and Splunk On-Call are all documented, with escalation levels triggered by error duration or error count, operator duty schedules, recovery notifications, maintenance windows and a way to test alert delivery. But the price of SMS and phone is stated only as unspecified "message credits", the captured pages give different figures for the maximum number of escalation levels (three and four), and we found no public information on alert grouping or acknowledging and resolving from the app. 1 4 5

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 status pages show current monitor status with colour codes and SLA icons, let me choose which monitors appear and style the page to a brand, and login-protected status pages for a defined audience exist — precisely the per-client model I run — but they are an Enterprise-plan feature and outside access needs a Support-confirmed permission grant. We found no public information on custom domains, email or SMS subscribers, component groups, or incident updates and scheduled-maintenance announcements on the page. 6 7

Report an error

The SaaS Platform Engineer

Public status pages publish current and SLA status for the monitors you choose, with branding control, and a protected variant secured by a login stays invisible to the outside world with read-only viewer accounts — though only on the Enterprise plan. That protected page is what I would hand a single customer. We found no public information in the captured pages on custom domains, incident updates, subscriber notifications or per-component uptime history. 6 7

Report an error

The Customer Support Lead

A public page lists each monitor with its current status and SLA status, lets you choose which monitors appear and style the page to your brand, and a login-protected page exists for a defined audience with read-only access, though it is a feature of the Enterprise plan only. For what my nine-person team needed during our last three-hundred-ticket outage, we found no public information on a custom domain, incident templates, or notifying subscribers by email, and no per-component uptime history was described. 6 7

Report an error

The E-Commerce Operations Manager

Public status pages publish each monitor's current status and SLA status with brand customization and selectable monitors, and protected, login-secured pages exist but only on the Enterprise plan. The captured pages describe no subscriber notifications, no custom domain, no incident updates on the page itself and no uptime history per component, so I cannot confirm how my customers would be told when checkout is down. 6 7

Report an error

The Information Security Officer

Public status pages publish the current status and SLA status of the monitors you select, with look-and-feel customization to match your brand, and protected pages add a login for a defined audience with read-only viewers and invisibility to the outside world — an Enterprise-plan feature. An incident management workflow is mentioned but not detailed on the captured pages. We found no public information on custom domains, incident updates and maintenance announcements, subscriber notifications, uptime history per component, or several languages and templates. 5 6 7

Report an error

The Skeptic

A public status page publishes current status and SLA status per monitor with brand customization and selectable monitors, and an Enterprise-only protected page secures content behind a login for read-only outside viewers. We found no public information on custom domains, subscriber notifications by email or SMS, incident updates published to the page, component groups, or how the status page itself stays online when the main service is down. 5 6 7

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 Monitor API is documented interactively with create, read, update, delete, clone, monitor-group and maintenance-scheduling operations, and there is a genuine Terraform provider on the public registry with Git-based workflow, configuration download and import — how I would roll out two hundred monitors — alongside operator groups and administrator roles. Terraform support is restricted to Enterprise-level accounts, and we found no public information on SAML single sign-on, SCIM provisioning, audit logs, client sub-accounts with their own logins, white-label client reports or two-factor authentication. 1 8 9

Report an error

The SaaS Platform Engineer

There is a genuine Terraform provider on the public registry that manages monitors, alert definitions, operators and vault items with a GitOps workflow and an import path for existing configuration — the way I want checks to live next to the services they test, though the captured pages note it is for Enterprise-level accounts. The Monitor API covers create, update, clone, delete, check results and maintenance scheduling, documented interactively with a changelog. We found no public information in the captured pages on single sign-on, SCIM, audit logs or client sub-accounts. 8 9

Report an error

The Customer Support Lead

A documented Monitor API with create, update, clone and delete endpoints, maintenance scheduling, a changelog and deprecation notices is backed by a Terraform provider in the public registry with Git-based version control and an import workflow for existing configuration, though Terraform support is for Enterprise-level accounts. Operator groups and an administrator role appear in passing, but we found no public information on single sign-on, SCIM, audit logs, two-factor authentication or client sub-accounts. 1 8 9

Report an error

The E-Commerce Operations Manager

A documented Monitor API covers creating, updating, cloning and deleting monitors plus detailed results of individual checks, and a Terraform provider with Git version control, import and configuration download is published — though Terraform is limited to Enterprise-level accounts. Operators and operator groups with grantable permissions are described, but the captured pages say nothing about single sign-on for the account, audit logs, two-factor authentication or separate client logins. 5 8 9

Report an error

The Information Security Officer

A documented Monitor API covers full create, read, update, delete and clone of monitors with maintenance scheduling and bulk views of definitions, and a Terraform provider on the public registry manages monitors, alert definitions and operators under Git-based version control — though Terraform support is described for Enterprise-level accounts. Operator groups with distinct permissions, including a Terraform hub restricted to administrators by default, evidence role-based team administration. We found no public information on single sign-on for account logins, SCIM, audit logs, two-factor authentication or checks triggered from CI/CD, and as the person who signs off every login before ISO 27001, that is where my attention stops. 1 8 9

Report an error

The Skeptic

A documented REST API covers full create, read, update, delete and clone of monitors plus check results and monitor groups, and a Terraform provider published in the public registry manages monitors, alert definitions and operators under Git version control with configuration download and import — though only for Enterprise accounts. We found no public information on single sign-on for the account itself, SCIM provisioning, audit logs, or client sub-accounts and white-label reports; the MFA and SSO mention concerns monitored user journeys, not account login. 1 8 9

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

Retention is documented plan by plan — individual check data 14 to 90 days depending on plan, statistical uptime, load-time and SLA data one to two years, and scheduled PDF, Excel and email reports with two years of report history — and SLA reports can be viewed, recalculated and exported by download or email, though SLA monitoring belongs to the Business and Enterprise plans only. We found no public information on response-time percentiles, published probe IP addresses for allow-listing, the vendor's own status page and incident history, or a service level agreement with credits. 10 11

Report an error

The SaaS Platform Engineer

Retention is stated per plan and per data type — individual check measurements up to 90 days, statistical uptime, load time and calculated SLA data up to two years — which is more precise than most vendors manage. SLA reporting supports several definitions, a dashboard, email and download export, and scheduled PDF, Excel and email reports exist, with SLA monitoring gated to the Business and Enterprise plans. We found no public information in the captured pages on response time percentiles, published probe IP addresses, or the vendor's own status page and incident history. 8 10 11

Report an error

The Customer Support Lead

Retention is published per plan in unusual detail, with statistical data including average uptime and calculated SLA data kept up to two years on the higher plans, and scheduled PDF, Excel and email reports plus an SLA dashboard with export by download or email, which gives me the uptime history I'd point to in a renewal conversation. We found no public information on response time percentiles, published probe IP addresses for allow-listing, or the vendor's own status page, incident history and SLA credits. 8 10 11

Report an error

The E-Commerce Operations Manager

Retention is published in detail per plan — up to two years for average uptime, load time and calculated SLA statistics and up to 90 days for individual measurements — and SLA reports can be viewed on a dashboard, recalculated and exported by download or email, with scheduled PDF, Excel and email reports. That gives me a record to show the agency, but the captured pages say nothing about the vendor's own status page and incident history, an SLA with credits, or published probe IP addresses for allow-listing. 8 10 11

Report an error

The Information Security Officer

Retention is stated per plan and per data type — individual check data, screenshots and waterfall data 14 to 90 days, statistical uptime, load time and calculated SLA data up to two years — and SLA reporting includes an overview dashboard, recalculation, multiple SLA definitions and export by download or email, with PDF, Excel and email reports kept for two years. The MonitorCheck API returns detailed results of individual checks, giving a route to raw data for evidence packs. We found no public information on response time percentiles and breakdowns, the probe IP addresses for allow-listing, or Uptrends' own status page, incident history and service level agreement, so the monitor's own reliability cannot be confirmed from these pages. 8 10 11

Report an error

The Skeptic

Retention is stated with rare precision: individual check data kept 14 to 90 days and statistical uptime, load-time and SLA data one to two years, each per plan, with scheduled PDF, Excel and email reports retained two years, SLA data exportable by download or email, and a check-results API. But the monitor's own trust record is a blank — we found no public information on the vendor's own status page or incident history, probe IP addresses for allow-listing, response-time percentiles, or an SLA with credits. 8 10 11

Report an error

European sovereignty panel opinion

n/r n/r n/r n/r n/r 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 vendor appears as Uptrends B.V., a Dutch company form, and the footer references terms and privacy; that is the full extent of what the captured pages show on this criterion. We found no public information on where account data, alert contacts, status page subscribers or check results are hosted, which subprocessors carry SMS, email or payments, or a published data processing agreement — dimensions I treat as unknown rather than non-European. 1 8

Report an error

The SaaS Platform Engineer not rated — no public information

We found no public information in the captured pages on where account data, alert contacts or check results are stored, on the contracting entity and its parent's seat, or on any subprocessor, data processing agreement or certification. Nothing on this vendor's sovereignty dimensions was captured, so there is nothing here for me to score. 1 8 10

Report an error

The Customer Support Lead not rated — no public information

We found no public information on where account data and alert contacts are stored, who the subprocessors are, whether a data processing agreement is offered, or any security certifications; the captured pages, including the main site, name the vendor but say nothing on these points. 1

Report an error

The E-Commerce Operations Manager not rated — no public information

No sovereignty attributes are on record and we found no public information on where account data, alert contacts, status page subscribers or check results are stored, which subprocessors handle SMS, phone, email or payments, or any data processing agreement or certification. The only related item on the captured pages is a footer link to terms and privacy. 1 8

Report an error

The Information Security Officer not rated — no public information

We found no public information on where account data, the phone numbers of on-call operators and status page subscribers are stored and processed, on the subprocessors behind hosting, SMS and phone gateways, email delivery, support and payment, or on a published data processing agreement and certifications. This is the first page I read as a buyer under NIS2, and none of it is covered by the captured pages; the sovereignty attributes on record are empty. 1 4 5 7 8 11

Report an error

The Skeptic not rated — no public information

We found no public information on where account data, on-call contact details or check results are stored and processed, who the subprocessors are, or whether a data processing agreement is offered; the captured pages name the vendor as Uptrends B.V. with ITRS branding but state no hosting location, subprocessor list or certification. 1 8 9

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 five-tier ladder from Starter to Enterprise and a 30-day free trial with no credit card are public, and per-plan feature gating is documented — SLA monitoring on Business and Enterprise, protected status pages and Terraform on Enterprise, SMS and voice on a message-credit model. Not a single price figure appears on the captured pages: we found no public information on what any tier costs, the price per monitor at two hundred monitors, seat pricing, or what a message credit costs, so I cannot budget sixty client sites without a sales conversation. 1 4 7 9 10 11

Report an error

The SaaS Platform Engineer

The only public pricing signals are a 30-day free trial with no credit card and free tools including free website monitoring; the five plan names appear together with which tier gets SLA monitoring, protected status pages and Terraform, but no prices are stated. SMS and voice alerts are said to "use message credits" without a price. We found no public information in the captured pages on per-tier prices, monitor counts, check intervals, seat costs, VAT or minimum terms. 1 4 10 11

Report an error

The Customer Support Lead

A free 30-day trial with no credit card and five named plan tiers are public, and some gates are stated outright, such as protected status pages and Terraform on Enterprise and SLA monitoring on Business and Enterprise. The captured pages contain no price figures for any tier, no scaling by monitors, interval or seats, and SMS and phone alerts are described only as using message credits with no rate stated, so a buyer cannot compute a real annual cost from what I read. 1 4 7 9 10 11

Report an error

The E-Commerce Operations Manager

Five plan tiers are named and a 30-day free trial with no credit card required is offered, and the pages do show which features are gated — SLA monitoring on Business and Enterprise only, protected status pages and Terraform on Enterprise, SMS and phone alerts consuming "message credits" — but not a single price for any tier, credit or alert appears on the captured pages. I cannot begin to compute what a monitoring season from March to June would cost. 1 4 7 9 10 11

Report an error

The Information Security Officer

The captured pages name five plans (Starter through Enterprise) and a free 30-day trial without credit card, and they place SLA monitoring on Business and Enterprise, protected status pages and Terraform on Enterprise — but we found no price figures on these pages. SMS and phone alerts "use message credits"; we found no public information on the price of a credit. I cannot compute an annual cost from what is public here. 1 4 7 9 10 11

Report an error

The Skeptic

Five named plan tiers and a 30-day free trial without a credit card are public, and some feature gating is visible — SLA monitoring limited to Business and Enterprise, protected status pages and Terraform to Enterprise — but we found no public information on any price: no cost per tier, monitor counts, check intervals, seat prices, or what a "message credit" for SMS and phone alerts costs. 1 4 7 9 10 11

Report an error

Questions about Uptrends

Is Uptrends European?

Not determined: the vendor’s pages as captured do not say where Uptrends is based.

Where does Uptrends store data?

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

Does Uptrends have a free plan?

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

What are the best alternatives to Uptrends?

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: Uptrends 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 (11)

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

  1. 1 Vendor page www.uptrends.com Checked 10 Nov 2026 Details →
  2. 2 Checks, locations & failure confirmation — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  3. 3 Checks, locations & failure confirmation — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  4. 4 Alerting, escalation & on-call — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  5. 5 Alerting, escalation & on-call — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  6. 6 Status pages & incident communication — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  7. 7 Status pages & incident communication — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  8. 8 API, monitoring as code & team administration — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  9. 9 API, monitoring as code & team administration — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  10. 10 Uptime reports, data & the vendor's own reliability — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →
  11. 11 Uptime reports, data & the vendor's own reliability — found from sitemap www.uptrends.com Checked 10 Nov 2026 Details →