Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 3 of 6 dimensions proven

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

by JJ Online GmbH · www.uptimia.com

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

Link to this page

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

Uptimia at a glance

Vendor
JJ Online GmbH
Headquarters
Incorporated in Germany source, captured 14 Nov 2026
Data hosting
In the EU source, captured 14 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 14 Nov 2026
Panel verdict
The AI panel rates Uptimia 3.5/5, the mean of 6 judges. Uptimia (JJ Online GmbH, Berlin) is strongest in checks and locations, scored 8 from minimum to maximum: failure confirmation is documented to the mechanics, with three backup probes agreeing by default from 171+ checkpoints across 70+ countries. how scores are made
As of
Vendor pages captured 1 Nov 2026 to 14 Nov 2026; evaluated by the panel 14 Nov 2026. all sources

Uptimia alternatives, European ones first →

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

The panel's verdict

Uptimia (JJ Online GmbH, Berlin) is strongest in checks and locations, scored 8 from minimum to maximum: failure confirmation is documented to the mechanics, with three backup probes agreeing by default from 171+ checkpoints across 70+ countries. Alerting and on-call and sovereignty hold at 7, with ten-step escalation ladders across twelve channels and a German contracting entity hosting on OVH in France under a self-serve DPA. The genuine splits sit in the middle categories, each spanning 6-7: status pages at five scores of 6 to the customer support lead's 7, which cites password- and IP-allowlisted pages for large accounts; automation and teams at two 6s citing no public information on Terraform, SAML or SCIM against four 7s crediting a 211-path API; and pricing transparency over the per-message SMS price beyond each plan's monthly allowance, VAT treatment, and captured pages giving different figures for the top tier. Reports and reliability sits at 6, with a 7 from the e-commerce judge for per-plan retention disclosure.

Report an error

Speaks for it

  • Three backup probes must agree by default before an incident opens, and one passing check recovers it.
  • 276 probe IP addresses and five user-agent strings are published for firewall allow-listing, across 171+ checkpoints in 70+ countries.
  • Escalation ladders of up to ten steps run across twelve alert channels, with scanner-proof one-click acknowledgement and a break-glass page to the account owner.
  • Sovereignty is documented end to end: a German contracting entity, OVH hosting in France, a self-hosted EU time-series store, and a self-serve DPA with 30-day subprocessor notice.
  • The version 2 API documents 211 paths, with bulk creation, dry-run previews and role- and group-scoped keys.

Report an error

Held against it

  • The pages state there are no voice-call alerts and that ladders page fixed people rather than rotating, pointing to PagerDuty for shift-based on-call.
  • We found no public information on a Terraform provider, SAML single sign-on, SCIM provisioning or client sub-accounts with their own logins.
  • We found no public information on the per-message SMS price beyond each plan's monthly allowance, on VAT treatment, or on overage handling.
  • The captured pages give different figures for the top tier: Enterprise at $199/mo billed annually on the pricing page against a high price of 229 in structured data.
  • We found no public information on the vendor's own status page or incident history, an SLA with credits, or response-time percentiles.

Report an error

Best for

  • You manage many client sites and want bulk rollout — onboarding sets up uptime, SSL and domain monitors from one pasted URL, and the API supports bulk creation with a dry run.
  • Your procurement requires an EU-anchored chain — German contracting entity, main hosting in France, self-serve DPA with published subprocessor locations.
  • You are paged for real outages only and want documented multi-region confirmation before an incident opens.
  • You need escalation ladders and one-click acknowledgement across many channels without per-seat billing — seats are part of the plan price.

Report an error

Avoid if

  • You need native calendar rotation for on-call shifts or voice-call alerts — the pages point to PagerDuty for rotation and state there are no voice-call alerts.
  • You need single sign-on or per-user logins on private status pages — the pages state private pages use a shared password or an IP allowlist.
  • You must pin down one authoritative top-tier price before committing — the captured pages give different figures for the top plan, and we found no public information on the per-message SMS price beyond each plan's allowance.
  • Your subscribers need notifications beyond email — the pages state email is currently the only subscriber channel.

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

Everything my sixty client sites need is documented: HTTP(S) with keyword, port, ping, DNS and mail-server checks, SSL expiry with chain, protocol and hostname validation, domain expiry, heartbeat cron pings and browser transaction replays, from every 30 seconds on paid plans out of 171+ checkpoints whose cities and IP addresses are published. A failure is confirmed from other regions first — by default three backup probes must agree, settable from one to three — and the confirmation logic and probe behaviour are documented in the help centre rather than left vague. Bulk creation and onboarding that sets up uptime, SSL and domain monitors from one pasted URL are exactly how I would roll out sixty clients. 1 3 2 4 12 13 21

Report an error

The SaaS Platform Engineer

The check catalogue reads like my weekly backlog: HTTP with keyword and status-code conditions, TCP and UDP ports, ping, DNS, mail servers, SSL with chain, protocol and hostname validation, domain expiry, heartbeats driven by five-field cron expressions, multi-step API request chains and recorded browser transactions replayed from a chosen probe, on intervals down to 30 seconds. Failure confirmation is exactly what I want before anyone is paged — one to three backup probes must agree before an incident opens, recovery needs a single passing check, and the checkpoint directory lists every location with city and IPv4 and IPv6 addresses. What holds it below the top band is that we found no public information on scripted or code-based checks kept in version control, or on alert limits tuned per location. 2 2 4 12 13 21

Report an error

The Customer Support Lead

HTTP, keyword, TCP, ping, DNS, mail-server and SSL checks sit beside browser transactions and multi-step API monitors, run from 171+ checkpoints across 70+ countries with a city-level directory, 276 published probe addresses and five listed user agents. A failure needs one to three confirming probes (three by default) with the confirmation logic documented, intervals reach 30 seconds, a lightweight agent covers internal servers, and maintenance windows pause checks. We found no public information on code-based checks kept in version control. 2 2 6 12 13 21

Report an error

The E-Commerce Operations Manager

Transaction monitoring replays a recorded browser journey and API monitors run a request chain, so the checkout and the payment endpoint can be watched and not only the homepage; uptime checks run as often as every 30 seconds with keyword, SSL, DNS and domain-expiry coverage, a failure must be confirmed by up to three regions before an incident opens, maintenance windows skip checks, and the 171+ probe locations come with a country-and-city directory and published IP addresses. I found no public information on scripted checks kept in version control. 2 12 13 7 21 6

Report an error

The Information Security Officer

The catalogue is broad and the detection method is documented well enough to reproduce: HTTP(S) with keyword and status-code rules, TCP and UDP ports, ping, DNS, mail protocols, SSL chain, protocol and hostname validation, domain expiry, cron-based heartbeats, transaction journeys and API request chains, at intervals down to 30 seconds from a published directory of checkpoints with country, city, IPv4 and IPv6. A failure must be confirmed by up to three regions before an incident opens, timeouts and per-check timing are configurable and retained, and maintenance windows skip checks. We found no public information on code-based checks kept in version control, location-specific thresholds or published probe health, which is what the top of the scale describes. 2 3 2 4 7 12 13 21

Report an error

The Skeptic

Failure confirmation is documented down to the mechanics: a configurable number of backup probes, three by default, must agree before an incident opens, one passing check recovers it, and the probe directory publishes every city with IPv4 and IPv6 addresses plus five user-agent strings. Sub-30-second intervals, browser transactions, request-chain API checks, DNS and domain expiry, cron heartbeats and an inside-the-server agent cover the breadth; I found no public information on scripted checks kept in version control or published probe health. 12 13 21 2 2

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

Twelve alert channels including email, SMS, Slack, Teams, Telegram, WhatsApp and PagerDuty, escalation ladders of up to ten steps with waits and bounded repeats, scanner-proof one-click acknowledgement without a login, alert grouping into one digest, per-person quiet hours and incident timelines with acknowledgement times — that covers how a small team like ours gets woken up. The pages state plainly that there are no voice-call alerts and no native calendar rotation for on-call, pointing instead to the PagerDuty integration for shift rotation, and we found no public information on the price of an SMS beyond the monthly allowance included in each plan. 6 6 7 14 15

Report an error

The SaaS Platform Engineer

Escalation is engineered the way a rotation needs it: reusable ladders of up to ten steps with waits from five minutes to two hours in the editor (one minute to twenty-four hours through the API), a bounded repeat, a break-glass page to the account owner when a ladder reaches nobody, one-click acknowledgment from a signed link that pauses the ladder while the incident stays open, grouping on by default, MTTA recorded, and twelve channels including PagerDuty and Twilio with quiet hours, recovery notices and delivery retries. Two things cap it for me: the pages state there are no voice-call alerts today and ladders page fixed people rather than rotating by calendar — the documented answer is to hand shift rotation to PagerDuty — and the price of an SMS beyond each plan's monthly allowance is not stated. 6 6 7 14 15

Report an error

The Customer Support Lead

Twelve channels including SMS, Slack, Teams, PagerDuty, Telegram and WhatsApp, escalation ladders of up to ten steps with waits and bounded repeats, scanner-proof one-click acknowledgement, alert grouping with storm digests, recovery notices and per-person quiet hours. Rotation by calendar is not native — the pages point shift-based teams at PagerDuty — and the captured pages state there are no voice-call alerts; monthly SMS allowances are listed per plan but we found no per-message price beyond them. 6 7 14 15

Report an error

The E-Commerce Operations Manager

Twelve channels including SMS worldwide from a built-in pool or our own Twilio account, escalation ladders of up to ten steps with waits, bounded repeats and a break-glass page to the account owner, one-click acknowledgment from a signed link without logging in, alert grouping, and incident timelines with mean time to acknowledge per incident. The pages state there are no voice-call alerts and that ladders do not rotate by calendar — they point to PagerDuty for shift-based on-call — and I found no public information on what an SMS beyond the plan's monthly quota costs. 6 6 14 15 7

Report an error

The Information Security Officer

Twelve alert channels including SMS, PagerDuty and webhooks, escalation ladders of up to ten steps with documented waits and bounded repeats, break-glass paging of the account owner, alert grouping with storm behaviour, recovery notices carrying the outage duration, and a scanner-proof one-click acknowledgment that records how long acknowledgement took — an acknowledgement trail an auditor can actually use. The pages state plainly that there are no voice-call alerts and that ladders do not rotate by calendar, with shift-based on-call delegated to PagerDuty, and the cost of SMS beyond each plan's monthly quota is not published. 6 6 7 14 15

Report an error

The Skeptic

The escalation engine is documented in convincing detail — per-step waits, bounded repeats, a break-glass rule that pages the owner, scanner-proof one-click acknowledgement, grouping with digests, held repeat outages and delivery retries — with twelve channels including PagerDuty on every plan. It stops short of full on-call: the vendor states there are no voice-call alerts and that ladders page fixed people rather than rotating, pointing at PagerDuty for shifts; SMS arrives as a per-plan monthly allowance with no stated price per message beyond it. 14 15 6 7 6

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

Client status pages are done properly: custom domain with an automatic certificate, sections grouping each client's services, automatic operational, degraded, outage and maintenance states fed by the monitors, staged incident updates, a 90-day uptime bar per service, branding with custom CSS, an embeddable widget, and password protection or IP allowlisting for per-client private pages. Email is documented as the only subscriber channel, and we found no public information on several languages or on how the status page hosting is kept separate from the main service. 5 5 16 17

Report an error

The SaaS Platform Engineer

The page updates itself from live monitor results through operational, degraded, outage and maintenance states, serves on your own domain with an automatic Let's Encrypt certificate, shows 90-day uptime bars per service with exact percentages, and carries staged incident and maintenance threads with a next-update ETA — nobody logs in at 3 a.m. to change a banner. Sections, an embeddable widget, custom CSS and custom code, and password or IP-allowlist private pages that are noindex and never cached are all documented. Email is the only subscriber channel, and we found no public information on SMS, RSS or webhook subscribers, several languages, incident templates, or how the page hosting is isolated from an outage of the monitoring service itself. 5 5 16 17

Report an error

The Customer Support Lead

Pages run on our own domain with automatic SSL, sections that group services the way customers name them, states driven live by monitors, staged incident and maintenance updates, email subscribers with double opt-in and no caps, exact 90-day uptime bars, and custom CSS with a removable logo. Password-protected and IP-allowlisted private pages would serve our largest accounts, with brute-force limits and gated views kept out of search engines. Email is the only subscriber channel, only uptime, SSL and speed monitors appear as components, and we found no public information on incident templates or page translations. 5 5 16 17

Report an error

The E-Commerce Operations Manager

Public pages on our own domain with automatic Let's Encrypt certificates, staged incident timelines, scheduled maintenance announcements, email subscribers with double opt-in, a 90-day uptime ribbon and password- or IP-allowlist-protected pages cover the customer-facing side of an outage. The pages state email is currently the only subscriber channel and that private pages have no single sign-on, and I found no public information on page languages or incident templates. 5 5 16 17

Report an error

The Information Security Officer

Custom-domain pages with automatically issued SSL, components fed by live monitor results, staged incident updates with subscriber email, scheduled maintenance, a 90-day uptime ribbon with exact percentages, password or IP-allowlist private pages served noindex, custom CSS and an embeddable widget. Email is the only subscriber channel, single sign-on for private pages is stated not to exist today, and we found no public information on several languages, incident templates or per-customer audience pages. 5 5 16 17

Report an error

The Skeptic

Custom domains with automatic certificates, sections, staged incident updates, scheduled maintenance, double-opt-in email subscribers, 90-day uptime bars, password and IP-allowlist privacy and an embeddable widget are all documented. Email is stated to be the only subscriber channel, only uptime, SSL and speed monitors can appear as components, private pages use a shared password rather than single sign-on, and I found no public information on multiple languages, incident templates, per-customer pages or hosting kept separate from the product itself. 5 5 16 17

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 API v2 reference lists 211 paths covering monitors of every family, status pages, incidents, maintenance, groups, users, roles, billing and the audit log, with bulk creation plus a dry-run preview, monitor templates, per-user API keys that inherit role and group scope, five fixed roles including editors limited to specific client groups, audit logging and two-factor authentication — scriptable client management is genuinely there. We found no public information on a Terraform provider, a CLI, SAML single sign-on or SCIM, and no client sub-accounts with their own logins; client separation runs through monitor groups and scoped seats. For pushing sixty clients' monitors from a script, that is close to everything I need. 7 18 19

Report an error

The SaaS Platform Engineer

The API is genuinely deep — version 2 with 211 paths and 305 operations that the docs say cover everything the control panel does, including bulk creation with a dry-run, monitor templates, partial updates from CI, maintenance windows and status pages, with keys that inherit their seat's role and monitor-group scope. Five fixed roles with scoped access per monitor group, two-factor authentication, a twelve-month audit log and white-label reports from Professional are all documented. The monitoring-as-code piece I care about is absent from the pages though: we found no public information on a Terraform provider or a CLI, SAML single sign-on, SCIM provisioning, or client sub-accounts with their own logins. 2 3 7 18 19

Report an error

The Customer Support Lead

An OpenAPI-documented API with 211 paths states everything in the control panel has a route — monitors across twelve families, status pages, incidents, escalations, maintenance, reports, users and the audit log — with bulk creation and dry-run previews, scoped per-user API keys, five fixed roles with enforced group scoping, a twelve-month audit log and per-person two-factor. We found no public information on a Terraform provider, SAML single sign-on, SCIM provisioning or client sub-accounts with their own logins. 4 7 18 19

Report an error

The E-Commerce Operations Manager

The version 2 API is documented across 211 paths covering monitors, incidents, status pages, contacts, users, teams, billing and audit logs, with bulk creation, a dry run and role-scoped keys, and the team model has five roles, enforced scoping to specific monitor groups, per-person two-factor authentication and a twelve-month audit log. I found no public information on a Terraform provider or command-line tool, SAML single sign-on, SCIM provisioning, or client sub-accounts with their own logins. 18 19 2 7

Report an error

The Information Security Officer

An API with 211 documented paths covers monitors, status pages, incidents, reports, users, teams and the audit log, with bulk creation and a dry-run preview; five fixed roles, enforced monitor-group scoping, per-person two-factor authentication and a twelve-month audit log of every invite, role and scope change give me the audit trail I require before anyone gets a login. We found no public information on SAML single sign-on, SCIM provisioning or a Terraform provider, which is the step above. 6 9 18 19

Report an error

The Skeptic

The v2 API is unusually deep — an OpenAPI spec with 211 paths covering monitors, status pages, incidents, maintenance, reports, templates, users, teams, billing and the audit log, with dry-run bulk creation and role- and group-scoped keys — alongside five fixed roles, enforced group scoping, an audit trail and two-factor. I found no public information on a Terraform provider or other monitoring-as-code workflow, SAML single sign-on, SCIM provisioning, or client sub-accounts with their own logins. 18 19 6

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 stated per plan — 90 days on Basic, a year on Professional, two years on Enterprise — with scheduled PDF, HTML or CSV reports from daily to yearly, branding from Professional up, shareable public links, CSV and API export of the logs, and the probe IP addresses and five user-agent strings published for firewall allow-listing. We found no public information on response-time percentiles, an SLA with credits, or the vendor's own public status page and incident history. 7 18 20 21

Report an error

The SaaS Platform Engineer

Retention is documented per plan with unusual candour — seven days on Free up to 24 months on Enterprise, response bodies cleared after seven days on every plan, and the readable window enforced as a read limit with a nightly prune — and check logs export to CSV, scheduled PDF, HTML and CSV reports exist, TLS handshake times are recorded per check, and every probe address plus all five user-agent strings are published for firewall allow-listing. What the pages do not show: response-time percentiles, an SLA calculation or credits, or the vendor's own public status page and incident history. 2 7 20 21

Report an error

The Customer Support Lead

Retention is unusually candid — 7 to 730 days readable depending on plan, explained as a read limit with nightly pruning — and scheduled PDF, HTML or CSV reports (branded from Professional), CSV export of check logs and the published probe address list give me something concrete for a renewal conversation. We found no public information on response-time percentiles, an SLA with credits, or Uptimia's own public status page and incident history. 5 7 20 21

Report an error

The E-Commerce Operations Manager

Retention is stated per plan — 90 days on Basic, twelve months on Professional, twenty-four on Enterprise — with CSV export of the check log, scheduled PDF, HTML and CSV reports on five cadences, branded client reports from Professional up, per-checkpoint reporting, mean time to acknowledge on every incident, and 276 probe IP addresses plus all five user-agent strings published for allow-listing. I found no public information on the vendor's own status page, an SLA with credits, or response-time percentiles. 20 21 7 6

Report an error

The Information Security Officer

Retention is documented per plan down to the detail that response bodies are cleared after seven days while timing, status code, probe and pass/fail remain; check logs export to CSV, probe IP addresses and all five user-agent strings are published, and incident timelines with acknowledgements are kept twelve months — a workable evidentiary record. We found no public information on response-time percentiles, an SLA with credits, or the vendor's own status page, incident history and post-mortems. 6 7 18 20 21

Report an error

The Skeptic

Retention is documented more frankly than most: per-plan readable windows from 7 to 730 days, a nightly prune an upgrade cannot reverse, response bodies cleared after seven days, CSV and API export, scheduled reports in PDF, HTML and CSV, and every probe IP published for allow-listing. I found no public information on the vendor's own status page or incident history, an SLA with credits, or response-time percentiles. 20 18 21 7

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 JJ Online GmbH in Berlin, the application, database and time-series data run on OVH in France, customer data is stated to stay in EU data centres, and the subprocessor list is unusually explicit with locations — Auth0 Ireland, Stripe Ireland, PayPal Luxembourg, easybill Germany, Google Ireland — alongside a self-serve data processing agreement with technical measures and 30-day subprocessor notice. Some legs are documented as leaving the EEA with stated safeguards: US sub-processing under DPF and SCCs, email to non-EU recipients from a US region, and Vultr probe locations without DPF covered by SCCs plus ephemeral processing, while the DPA also contemplates customer-directed routing of alert payloads to non-EEA channels. We found no public information on ISO 27001 or SOC 2 certification. 8 9 10 11

Report an error

The SaaS Platform Engineer

This chain is documented end to end: a German GmbH contracting entity in Berlin, the main application on OVH in France with a self-hosted time-series database in the EU, transactional email through AWS's Luxembourg entity in Frankfurt, a published self-serve DPA with technical and organisational measures and 30-day subprocessor change notice, and a subprocessor list with named providers, locations and transfer mechanisms — including Vultr without the EU–US Data Privacy Framework, covered by SCCs plus ephemeral probe processing that persists nothing at the probe layer. What is not evidenced: we found no public information on ISO 27001 or SOC 2 certifications, and email to non-EU recipients runs through AWS in Virginia under the Data Privacy Framework with SCC fallback. 8 9 10 11

Report an error

The Customer Support Lead

JJ Online GmbH in Berlin is the contracting entity, the application runs on OVH in France with email and storage under AWS's Luxembourg entity, the time-series database is self-hosted in the EU, and the subprocessor list names Auth0, Stripe, easybill, Google Ireland and others with locations and transfer mechanisms. The DPA is self-serve with technical measures annexed and a 30-day subprocessor notice, and the non-EU legs (AWS US for email to non-EU recipients, Vultr probes without DPF certification) carry standard clauses plus ephemeral processing that keeps nothing at the probe. We found no public information on ISO 27001 or SOC 2 certifications. 8 9 10 11

Report an error

The E-Commerce Operations Manager

The contracting entity is JJ Online GmbH of Berlin, the main application runs on OVH in France with time-series data on self-hosted EU storage, and subprocessors are listed by name, location and transfer mechanism under a self-serve data processing agreement with documented technical measures and breach notification. I found no public information on ISO 27001 or SOC 2 certification, and the agreement contemplates alert payloads routed onward to channels outside the EEA at the customer's instruction. 8 9 10 11

Report an error

The Information Security Officer

A German GmbH as contracting entity, the application and primary database on OVH in France, customer data in EU data centres, a subprocessor list with locations and transfer mechanisms, probe processing disclosed as ephemeral with no persistence at rest, and a self-serve data processing agreement with technical and organisational measures, thirty-day subprocessor notice and a free counter-signed counterpart. It stops short of the top because no ISO 27001 or SOC 2 certification is stated anywhere, and the agreement itself contemplates restricted alert channels resting on Article 49 derogations, with one probe provider carrying no Data Privacy Framework certification. 8 9 10 11

Report an error

The Skeptic

A German contracting entity, main hosting on named French infrastructure, a self-hosted EU time-series store, a published DPA applying by reference with TOMs annex and 30-day subprocessor notice, and a subprocessor list with locations and transfer mechanisms — including a probe provider listed with no Data Privacy Framework certification, relying on SCCs and ephemeral processing. Non-EU legs remain for mail to non-EU recipients, non-EU probes and restricted alert channels under Article 49 derogations, and I found no public information on ISO 27001 or SOC 2 certification. 9 10 11 8

Report an error

Pricing transparency

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

The ladder is public with its scaling rule and what counts as a monitor: Basic $9/mo. for 10 uptime checks at a one-minute interval, Professional $39/mo. for 100 at 30 seconds, Enterprise $199/mo. for 1,000 — seats, status pages and monthly SMS allowances included per plan, up to 13% off annual billing, no feature sold as an add-on, cancel anytime, and a free tier of one site checked every five minutes, so my two-hundred-monitor price is readable off the page. The gaps: we found no public information on the per-message price of SMS beyond the included allowance or on VAT treatment, anything beyond the published tiers runs through 'Talk to us' for an individual plan, and the captured pages give different figures for the top plan — $199/mo. on the pricing page against $229 in an offer summary on another page. 1 7 13 14

Report an error

The SaaS Platform Engineer

Each tier is public with its monitor count, interval, users, status pages and monthly SMS allowance — Basic $9/mo billed annually for 10 monitors at a one-minute interval, Professional $39/mo for 100 at 30 seconds — the free plan's single monitor at five minutes is spelled out, no feature is a paid add-on, there is no per-seat billing, annual billing saves up to 13%, and running subscriptions are never repriced. What I cannot compute from the pages: the cost of an SMS past the allowance, VAT treatment, and behaviour beyond plan limits apart from a custom plan on request. The captured pages also give different figures for the top tier — the plan cards say $199/mo while structured data on another page gives a high of 229. 1 5 6 7 13

Report an error

The Customer Support Lead

All tiers are public with monitor counts, check intervals, seats, status pages and history spelled out — Basic $9/mo, Professional $39/mo, Enterprise $199/mo, annual billing saves up to 13%, and the vendor states no feature is a paid add-on. SMS carries monthly allowances of 50, 150 and 500 by plan but we found no per-message price beyond them, and no public information on overage handling, VAT treatment or a monthly-only rate; the captured pages also give different figures for the top plan (199 on the pricing page, 229 in structured data elsewhere). 1 5 7 14

Report an error

The E-Commerce Operations Manager

Every tier is public with its monitor count, check interval, seats, status pages, SMS quota and history window, alongside a free tier, up to 13% annual discount, plain definitions of what counts as an uptime versus an advanced check, cancellation anytime and no repricing of a running subscription. I found no public information on the price of an SMS beyond the monthly quota, VAT treatment, or overage handling. 1 7 14

Report an error

The Information Security Officer

Every tier is public with its monitor count, interval, advanced checks, status pages, seats, SMS allowance, RUM pageviews and retention, the free tier's limits are stated, cancellation is anytime and no feature is a paid add-on. The price of SMS beyond the monthly quota, VAT treatment and the cost of seats beyond a plan's fixed count are not published, and the captured pages give different figures for the top of the price range. 1 5 7 13

Report an error

The Skeptic

Tiers are public with their monitor counts, intervals, status pages, seats, history and monthly free-SMS allowances, check definitions are spelled out, plan gates for escalation and private pages are documented, and the vendor states it never reprices a running subscription. What a buyer still cannot compute: the price per SMS beyond the allowance, VAT treatment, minimum term and overage handling — and the captured pages give different figures for the top tier, the pricing page showing Enterprise at $199/mo billed annually while structured data elsewhere lists a high price of 229. 7 1 5 6

Report an error

European sovereignty — proven facts

3 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 EU only unverified
Why unverified?

The DPA (Annex D, restricted alert channels) contemplates onward routing of alert payloads to non-EEA recipients at the customer's instruction, so not every processing leg stays in the EU even though storage is EU-only.

4/4 pts 11 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 1/1 pts 11 Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Uptimia

Is Uptimia European?

Yes. whats-best.ai classifies Uptimia as EU-Made. Its vendor, JJ Online GmbH, is incorporated in Germany, per the vendor’s page captured 14 Nov 2026.

Where does Uptimia store data?

Uptimia stores customer data in the EU, per the vendor’s page captured 14 Nov 2026.

Does Uptimia have a free plan?

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

What are the best alternatives to Uptimia?

As of 19 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (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: Uptimia 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 (21)

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

  1. 1 Vendor homepage www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  2. 2 Features page (uptime monitoring) www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  3. 3 Features page (SSL monitoring) www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  4. 4 Features page (heartbeat monitoring) www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  5. 5 Features page (status pages) www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  6. 6 Features page (alerting) www.uptimia.com Checked 14 Nov 2026 +1 earlier capture: 1 Nov 2026 Details →
  7. 7 Pricing page www.uptimia.com Checked 14 Nov 2026 Details →
  8. 8 Legal notice www.uptimia.com Checked 14 Nov 2026 Details →
  9. 9 Privacy policy www.uptimia.com Checked 14 Nov 2026 Details →
  10. 10 Data processing agreement (dpa) www.uptimia.com Checked 14 Nov 2026 Details →
  11. 11 GDPR page www.uptimia.com Checked 14 Nov 2026 Details →
  12. 12 Checks, locations & failure confirmation — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  13. 13 Checks, locations & failure confirmation — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  14. 14 Alerting, escalation & on-call — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  15. 15 Alerting, escalation & on-call — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  16. 16 Status pages & incident communication — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  17. 17 Status pages & incident communication — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  18. 18 API, monitoring as code & team administration — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  19. 19 API, monitoring as code & team administration — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  20. 20 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →
  21. 21 Uptime reports, data & the vendor's own reliability — found from sitemap help.uptimia.com Checked 14 Nov 2026 Details →