Uptime Monitoring & Status Pages
Oh Dear
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Immutable VOF · ohdear.app
Compare with UptimeRobot → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Oh Dear at a glance
- Vendor
- Immutable VOF
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention Belgium source, captured 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates Oh Dear 3.5/5, the mean of 6 judges. Oh Dear is an uptime monitoring and status page service from Immutable VOF in Berlaar, Belgium. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 2 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Oh Dear is an uptime monitoring and status page service from Immutable VOF in Berlaar, Belgium. The bench scored it strongest on pricing transparency, 7 to 8: tiers run from Solo at €15/mo for 2 sites to Scale at €399/mo for 200 sites, scaling only by monitored site count, with sign-on, unlimited users and status pages on every plan. Sovereignty spans 6 to 8 as judges weigh the same chain differently: primary data with Combell in Belgium, a published data processing agreement with the EU's 2021/914 Standard Contractual Clauses, against probe nodes, backups and check reports on US providers under those clauses. Alerting and on-call sits at 6: twelve channels are documented, but we found no public information on phone-call alerts, on-call rotations or escalation with timeouts, and SMS runs through the customer's Vonage account. Reports and reliability spans 5 to 7, including the bench's lowest score, 5 — the lower score weighing the vendor's statement that it offers no formal SLA with credits, plus the absence of public information on its own status page or incident history.
Speaks for it
- A failure at the primary location is re-confirmed from a second location in a different city on a different provider before any downtime notification is sent.
- Plans scale only by monitored site count — Solo at €15/mo for 2 sites to Scale at €399/mo for 200 — with single sign-on, unlimited users and unlimited status pages on every plan, plus a 10-day trial without a credit card and a 30-day money-back guarantee.
- SAML 2.0 single sign-on is on every plan and can be required for everyone except the team owner.
- A documented REST API, signed webhooks and an MIT-licensed Terraform provider support monitoring as code from version control.
- Primary monitoring data sits with Combell in Belgium, the data processing agreement with the EU's 2021/914 Standard Contractual Clauses is published and signable, and the subprocessor list is public.
Held against it
- The vendor states it offers no formal SLA with service credits, only a 99.9 percent uptime target.
- We found no public information on phone-call alerts, on-call schedules and rotations, or escalation policies with timeouts.
- Status page access is public or behind a secret URL, which the vendor itself describes as not a login and not per-user access control.
- SMS notifications run through the customer's own Vonage account, so they are not billed by Oh Dear.
- The captured pages give different figures for VAT — the pricing page shows EUR ex. VAT while the terms say prices include applicable Belgian VAT where required.
Best for
- You run an agency or studio monitoring many client sites and want per-client status pages, branded monthly reports, guest access and a reseller flow from one subscription.
- You need outside-in uptime, certificate, DNS and cron monitoring where false alarms are filtered by second-location confirmation from a different provider.
- You want monitoring as code — a REST API, signed webhooks and a Terraform provider — under SAML single sign-on that can be enforced team-wide.
- You are a European buyer who values a Belgian contracting entity, a published DPA with EU Standard Contractual Clauses and a public subprocessor list, and accepts SCC-covered US providers for probes and backups.
Avoid if
- You need native phone-call paging, rotations and escalation chains — the documented design forwards serious on-call to PagerDuty or Opsgenie instead.
- You need multi-step browser or transaction checks that walk a login or checkout, or intervals faster than the documented one-minute minimum.
- Your procurement requires a formal SLA with service credits, or ISO 27001/SOC 2 certification held by the vendor itself.
- Your status page must be private with per-user access control rather than a secret URL.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3 of 5 |
| Status pages & incident communication | 3 of 5 |
| API, monitoring as code & team administration | 3.5 of 5 |
| Uptime reports, data & the vendor's own reliability | 3 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 4 of 5 |
Checks, locations & failure confirmation
Show reasoningHide reasoning
How this is scored
What can be monitored and how reliably a failure is detected: HTTP(S) with status code and keyword checks, TCP and port, ping, DNS records, SSL certificate and domain expiry, cron jobs and heartbeats, multi-step API checks with assertions, browser or transaction checks of a login or checkout, the shortest check interval, the number and regions of probe locations, the re-check from a second location before an alert, timeouts and response time thresholds, and private locations inside the customer's own network.
0 — Runs no checks of its own; a status page or alerting tool that only receives signals from other monitors.
3 — HTTP checks of a URL at a fixed interval with an up or down result; keyword, SSL, cron and the probe locations are basic or not described.
5 — HTTP(S), keyword, TCP or port, ping and SSL expiry checks, cron or heartbeat monitoring, an interval of one minute or less, several named probe locations, a failure confirmed from a second location before alerting, and response times recorded per check.
8 — Multi-step API checks with assertions on headers and body, browser or transaction checks of a user flow, DNS and domain expiry checks, sub-minute intervals, probe locations listed by city with the confirmation logic documented, private locations or agents for internal services, and maintenance windows that pause checks.
10 — Coverage and accuracy a reliability team runs on: every check type above with code-based checks (for example Playwright or scripted tests) in version control, location-specific thresholds, false-positive handling and probe health published, and the detection method documented so a result can be reproduced.
The Agency Developer
HTTP with keyword, JSON-body and header assertions, ping, TCP ports, DNS records, domain expiry, certificate health and cron heartbeats are all documented, checked every minute by default with the failure re-run from a second city on a different provider before any alert goes out — exactly the confirmation logic I want before a client calls me about a certificate. What holds it back: we found no public information on multi-step scripted flows, browser transaction checks of a login or checkout, sub-minute intervals or private probes inside a client's own network, and the TCP check documentation itself says it is not a synthetic checkout. 2 3 4 14 15 21
The SaaS Platform Engineer
The documented set covers HTTP(S) with keyword and forbidden-string matching, JSON body assertions (up to ten, on values and response headers), custom verbs and payloads, TCP with send-string, ICMP ping, full SSL chain validation, DNS records, domain expiry and cron heartbeats with grace periods — checked every minute by default from named cities on six continents, and a failure at the primary location is re-confirmed from a second location in a different city on a different provider before anyone is alerted, which is exactly the confirmation logic I want written down. It sits below the top band because the documented assertions evaluate a single endpoint: we found no public information on multi-step request chains or scripted browser transactions of a login or checkout (Lighthouse audits on desktop and mobile from three continents are the closest documented browser-based check), the shortest documented interval is one minute, and checks are strictly outside-in with nothing installed on the monitored machine — we found no public information on private probe locations inside our own network. 2 3 4 7 14 15 21
The Customer Support Lead
Checks run every minute by default from fourteen named cities, and a failure at the primary location is re-checked from a second one in a different city on a different provider before anyone is alerted — that confirmation logic is documented in detail, which is what keeps false alarms off my rota on a payroll deadline night. JSON body assertions, header verification, DNS, domain expiry, SSL, cron heartbeats, ping and TCP ports are all evidenced; we found no public information on sub-minute intervals or probes inside a customer's own network, and the captured pages state the check is not a synthetic checkout. 2 7 14 15 20 21
The E-Commerce Operations Manager
Checks run every minute by default, a failing monitor is retried every minute, and a failure at the primary location is confirmed from a second city on a different provider before anyone is paged, with status-code, required and forbidden keyword, JSON body assertion, ping, TCP port, SSL, DNS, domain expiry and cron heartbeat checks I can aim straight at the checkout and payment URLs. Probe cities are named, including Frankfurt, Paris, London and Stockholm, and maintenance periods stop notifications during planned work. We found no public information on browser or transaction checks that walk a full checkout, and the shortest documented interval is one minute. 2 14 15 21 3 6
The Information Security Officer
Uptime checks cover HTTP with required and forbidden strings plus JSON body assertions, TCP ports with expected-port lists, ICMP ping, DNS, domain expiry, certificate health and cron heartbeats, running every minute by default with failing monitors retried every minute, and a failure at the primary location is re-confirmed from a second location in a different city on a different provider before any downtime alert — confirmation logic this clearly documented is exactly what I want reproduced in an audit file. Fifteen probe cities are named across six continents and the probe addresses are published for allow-listing. We found no public information on multi-step transaction checks of a login or checkout, sub-minute intervals or private probe locations inside our own network, which keeps this below the top band. 2 4 6 7 14 15 21
The Skeptic
Failure confirmation is documented properly: each monitor has a primary location, a failure there is re-checked from a different city on a different provider, and both must report down before a downtime notification goes out — with the probe addresses published and updated automatically. HTTP checks carry keyword, forbidden-string, header and JSON body assertions, alongside TCP, ping, DNS, domain expiry, SSL chain validation and cron heartbeats, from sixteen named cities at a shortest documented cadence of one minute. The vendor itself states the checks are strictly outside-in with no agent and that the TCP check is not a synthetic checkout, and we found no public information on multi-step or browser transaction checks. 2 7 14 15 21
Alerting, escalation & on-call
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
Twelve channels including SMS, Telegram, PagerDuty and Opsgenie, routed per team, per site, per tag or tag group with business-hours filtering, acknowledgement with hourly reminders, and recovery notifications that auto-resolve PagerDuty and Opsgenie incidents — enough to send each client's 3 AM outage to the one person who owns the fix. We found no public information on phone call alerts, escalation policies with timeouts or on-call schedules and rotations; SMS runs through the customer's own Vonage account, so its cost never appears in an Oh Dear plan. 6 14 17
The SaaS Platform Engineer
Twelve channels are documented — email, Slack, Teams, Discord, Google Chat, Telegram, SMS, Pushover and ntfy with configurable priorities, webhooks, plus forwarding to PagerDuty and Opsgenie that auto-resolve on recovery — with acknowledge carrying fixed durations, hourly reminders while a monitor stays down, routing at team, site, tag and tag-group level, business-hours filtering per destination, and maintenance periods and snooze that mute alerts. For my four-person rotation the ceiling is real: SMS runs through our own Vonage account, and we found no public information on phone-call alerts, on-call schedules and rotations, escalation that hands an unacknowledged alert to a different person, or internal incident timelines showing who did what. 4 6 14 16 17
The Customer Support Lead
Twelve channels including SMS, push through Pushover and ntfy, PagerDuty and Opsgenie forwarding, acknowledgement with a chosen duration, hourly reminders until recovery, business-hours routing and maintenance periods that mute — most of what a support team needs to stop duplicate tickets. We found no public information on phone call alerts, on-call schedules or rotations with overrides, and SMS runs through the customer's own Vonage account rather than a per-message price. 6 14 15 17
The E-Commerce Operations Manager
Twelve channels including SMS, routing per team, site, tag and tag group, acknowledgement that stops the hourly reminders, recovery notifications, snooze, maintenance periods that mute alerts, and forwarding to PagerDuty and Opsgenie with automatic resolve. For my night shift the catch is that SMS goes through your own Vonage account, and we found no public information on phone call alerts, built-in on-call schedules and rotations, or escalation to a different person after a timeout, so paging would come through the PagerDuty or Opsgenie integration instead. 6 14 16 17 15
The Information Security Officer
Twelve channels including email, SMS via the customer's own Vonage account, Slack, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover and ntfy, with routing at team, site, tag and tag-group level, acknowledgement windows, hourly reminders until recovery, throttled repeats, business-hours routing and maintenance periods that mute notifications. We found no public information on voice-call alerting, escalation policies with timeouts, or on-call schedules and rotations, so for serious on-call I would keep PagerDuty or Opsgenie in front of it. 4 6 14 16 17
The Skeptic
Twelve channels including SMS through the customer's own Vonage account, PagerDuty and Opsgenie with automatic resolve, acknowledgement with fixed durations and hourly reminders, recovery notifications, maintenance periods, throttled repeats, and per-destination event filtering with business-hours routing — the noise-reduction end is genuinely documented. We found no public information on phone call alerts, on-call schedules and rotations, or escalation chains with timeouts, and SMS costs sit with the customer's own Vonage account rather than on the vendor's price list. 6 14 16 17
Status pages & incident communication
Show reasoningHide reasoning
How this is scored
How customers and colleagues are told: public status pages on a custom domain with SSL, components and component groups fed automatically by monitors or set by hand, incident updates and scheduled maintenance announcements, subscribers notified by email, SMS, RSS or webhook, uptime history shown per component, private or password-protected pages for internal teams or single customers, branding and custom CSS, several languages, page templates, and how the status page itself stays online when the main product is down.
0 — No status page of any kind.
3 — A public status page listing monitors with their current state; custom domain, incident updates and subscribers are basic or not described.
5 — Public status pages on a custom domain, components linked to monitors, incident updates and scheduled maintenance, email subscribers, uptime history per component, the vendor's branding removable, and a password-protected or private page option.
8 — Component groups, SMS, RSS and webhook subscribers with per-component subscriptions, private pages with single sign-on or IP restriction, several languages, incident templates, embeddable status widgets, audience-specific pages for single customers, and the status page hosting kept separate from the main service and documented.
10 — Incident communication end to end: incidents drafted from monitor events and approved by a person, updates published to the page, subscribers, chat and social channels at once, a full incident archive with post-mortems, status page uptime published, and accessibility of the page stated.
The Agency Developer
Unlimited status pages on a custom domain with automatic SSL, own logo, favicon and colours, in 25 languages, fed automatically by connected monitors, with scheduled-maintenance posts, saved templates, a severity timeline and email, Slack and RSS subscribers — a workable separate page for each of my client groups. Access is the weak point: a page can sit behind a secret URL, but the vendor itself notes that secret is not a login and not per-user access control, and we found no public information on component groups, per-component subscriptions or private pages with single sign-on or IP restriction. 5 18 19 22
The SaaS Platform Engineer
Unlimited pages on every plan, custom domain with a certificate Oh Dear issues, our logo, colours and favicon, 25 languages, saved templates, an embeddable badge, email, Slack and RSS subscribers plus JSON and XML feeds — and the part I care about, the page posts automatically when a connected monitor goes down and recovers unless we switch to manual approval, with a Scheduled severity for planned work and updates stacking into a timeline. Access control is the weak point: the only documented non-public option is a secret URL, which the documentation itself says is not a login and not per-user access control, and we found no public information on component groups, per-component subscriptions, or SMS and webhook subscribers. 5 18 19 21 22
The Customer Support Lead
The pieces I fought for last outage are evidenced: a page on our own domain with automatic SSL, monitors feeding it automatically, saved incident templates, updates with severities stacking into one timeline, scheduled maintenance posts in advance, subscribers notified by email, Slack and RSS, 25 languages and unlimited pages on every plan. The privacy option is a secret URL — the captured pages state plainly that this is not a login and not per-user access control, so it will not satisfy a largest-account requirement — and we found no public information on component groups or per-component subscriptions. 2 5 18 19 22
The E-Commerce Operations Manager
Status pages on my own domain with the certificate issued for me, downtime and recovery posted automatically from connected monitors unless the team approves every post, incident severities stacking into a timeline, scheduled maintenance announced in advance, and email, Slack and RSS subscribers notified automatically, with branding, 25 languages and unlimited pages so I can run one page per shop. Access is public or behind a secret URL, which the documentation itself describes as not a login, and we found no public information on password-protected pages, single sign-on for status pages, or SMS and webhook subscribers. 5 18 19 22
The Information Security Officer
Status pages are unlimited on every plan, on our own domain with automatic SSL, self-updating from connected monitors, with incident updates at five severities stacking into one timeline, scheduled maintenance notices, saved templates, automatic subscriber notification, twenty-five languages and per-page branding, and pages can be shared per client with guest access limited to selected monitors. Subscribers can choose email, Slack or RSS and a status badge is embeddable. Page access is public or behind a secret URL — the vendor itself notes that secret is not a login — and we found no public information on private pages with single sign-on or IP restriction, or on SMS and webhook subscribers. 5 18 19 22
The Skeptic
Custom domain with a certificate the vendor issues, connected checks feeding the page automatically (with a toggle so a person can approve every post), updates with severities including Scheduled stacking into a timeline, email, Slack and RSS subscribers, twenty-five languages, saved templates and an embeddable badge — unlimited pages on every plan. Access is public or behind a secret URL, which the vendor itself says is not a login and not per-user access control. The pages are documented as hosted separately from the monitored site, but we found no public information on separation from the vendor's own service, component groups, or per-component and SMS subscriptions. 5 18 19 21
API, monitoring as code & team administration
Show reasoningHide reasoning
How this is scored
How the tool fits a team and a deployment pipeline: a documented REST API to create and read monitors, status pages and incidents, a Terraform provider, CLI or monitoring-as-code workflow, checks run from CI/CD before a deploy, bulk import of monitors, integrations with ticketing and chat tools, team members with roles, single sign-on (SAML) and SCIM, audit logs, several teams or client accounts in one organisation, white-label or client reporting for agencies, and two-factor authentication.
0 — No API, no team accounts; one login per account and monitors are set up only by hand.
3 — A web dashboard with a few team members; the API, roles and multi-client set-up are basic or not described.
5 — A documented REST API covering monitors and status pages, webhooks, team members with roles, two-factor authentication, bulk import or a CSV upload of monitors, and several projects, teams or client groups in one account.
8 — A Terraform provider or monitoring-as-code CLI with checks kept in version control, checks triggered from CI/CD, single sign-on (SAML), SCIM provisioning, audit logs, sub-accounts for clients with their own logins, and white-label client reports.
10 — Administration that scales across many teams and clients: every setting reachable by API and code with parity stated, granular roles per resource, SSO enforced with SCIM, audit logs exportable to a SIEM, and agency or reseller accounts with separate billing.
The Agency Developer
A documented REST API where one JSON payload template kept in version control creates every new client monitor with only URL, name and tags changed, a Terraform provider, SAML single sign-on that can be required for everyone except the team owner, user roles, guest access limited to a client's own monitors and status pages, and a reseller program billing every client through my own subscription. We found no public information on SCIM provisioning, audit logs or checks triggered from CI/CD before a deploy. 7 9 20 21 22
The SaaS Platform Engineer
A documented REST API covers creating and reading monitors with per-check settings, status-page updates can be posted from the API for deploy-pipeline automation, and there is a Terraform provider (community-maintained, MIT-licensed) declaring sites in versioned config, plus a documented workflow of keeping a default payload as a JSON file in version control — monitoring as code is genuinely usable here, not a marketing slide. SAML 2.0 SSO is on every plan and can be required for everyone except the team owner, alongside roles and permissions, unlimited users, two-factor, guest access limited to chosen monitors and status pages, and a reseller mode where clients never need their own login. We found no public information on SCIM provisioning, audit logs, or checks run from CI/CD before a deploy. 7 9 19 20 21 22
The Customer Support Lead
A documented REST API covering monitors, status page updates and badges, a Terraform provider with sites declared in versioned config, SAML single sign-on that can be enforced for everyone but the team owner, two-factor, unlimited users with roles and permissions, guest access limited to chosen monitors and pages, and a reseller flow where clients need no account of their own. We found no public information on SCIM provisioning, audit logs, or checks run from a deployment pipeline before a release. 7 9 19 20 21 22
The E-Commerce Operations Manager
A documented REST API over monitors and status page updates, signed webhooks, a Terraform provider that keeps monitored sites in versioned config, SAML single sign-on enforceable for everyone except the team owner, user roles, unlimited users, client grouping with read-only per-site access, guest logins and a reseller account running every client from one subscription. The branded client reports keep a small powered-by mark, and we found no public information on SCIM provisioning, audit logs or checks triggered from a deployment pipeline. 20 21 9 7 22 6
The Information Security Officer
A documented REST API with bearer-token authentication covers monitors, checks, tags and monthly-report recipients, status-page updates can be posted from a deploy pipeline, and a Terraform provider (MIT licensed, maintained by Articulate) plus JSON template payloads kept in version control give real monitoring-as-code. SAML 2.0 single sign-on is on every plan and can be enforced for everyone except the team owner, alongside two-factor, roles and unlimited users — the SSO enforcement matters to me. We found no public information on SCIM provisioning, audit logs or CSV bulk import, and client reports carry a small "powered by Oh Dear" mark. 7 9 19 20 21
The Skeptic
A documented REST API with bearer-token authentication covers monitors and status page updates, a MIT-licensed Terraform provider (maintained by a third party) and a JSON-template workflow keep check definitions in version control, and SAML single sign-on is on every plan and can be required for everyone but the team owner. Unlimited users with roles, two-factor, tags and tag groups, client grouping, guest access limited to selected monitors and status pages, and a reseller program round out the team side. We found no public information on SCIM provisioning, audit logs or bulk import, and the vendor states its reports are not fully white-labelled. 9 19 20 21 22
Uptime reports, data & the vendor's own reliability
Show reasoningHide reasoning
How this is scored
What the record is worth and whether the monitor itself can be trusted: uptime and SLA reports per monitor and period, response time charts and percentiles, scheduled reports by email, client-facing reports, how long check results and incident history are kept, export of results by CSV or API, the vendor's own public status page and incident history, its SLA, the probe IP addresses and user agent published for allow-listing, and an open-source or self-hosted edition.
0 — No history of any kind; only the current state is shown.
3 — An uptime percentage and a response time chart per monitor; retention, export and the vendor's own status are basic or not described.
5 — Uptime and response time reports per monitor and period, SLA reports, scheduled email reports, the retention period of check results stated, CSV or API export, the probe IPs published, and the vendor's own public status page.
8 — Response time percentiles and breakdowns (DNS, connect, TLS, first byte), client-ready branded reports, retention of a year or more stated per plan, a raw export of check results, the vendor's incident history and post-mortems public, and an SLA with credits published.
10 — A record that holds up in an audit: SLA calculations with their method stated, incident records suitable for ISO 27001, NIS2 or DORA evidence, full history exportable in an open format, a self-hosted or open-source edition with feature parity stated, and the vendor's own availability over several years published.
The Agency Developer
Monthly client reports carry my logo and accent colour (a small "powered by Oh Dear" mark remains), with sections chosen per site, emailed on the first of the month to up to five recipients with a browser link the client opens without an account, and every past report kept; monitoring data is retained one to two years per plan and exportable via the API, response times break down into DNS, TCP, TLS and first byte, and the probe IP addresses are published in JSON and CSV. Against that, the vendor states it offers no formal SLA with credits, and we found no public information on its own status page, incident history or post-mortems. 7 11 14 22
The SaaS Platform Engineer
Monthly client reports are branded with our logo and accent colour, emailed on the first of the month with configurable sections, and every past report stays on a browser link the recipient opens without an account; uptime history shows 7 days, 12 months and all-time, performance breaks down DNS, TCP, TLS, server processing and download per check, monitoring data is kept typically one to two years by plan, everything exports via API, and the probe addresses are published in HTML, JSON and CSV. The ceiling is the vendor's own trust record: the terms state plainly that no formal SLA with credits is offered and Oh Dear itself holds neither ISO 27001 nor SOC 2, and we found no public information on response-time percentiles or the vendor's own public status page and incident history. 2 7 10 11 14 15 22
The Customer Support Lead
For a contract renewal I can point to uptime over the past 7 days, 12 months and all-time per monitor, monthly client reports branded with our logo and accent colour that open from a browser link without an account, monitoring data retention of typically 1-2 years, API export of all monitoring data, and probe IP addresses published in HTML, JSON and CSV. The captured pages state there is no formal SLA and no service credits, and we found no public information on the vendor's own status page, its incident history, or response-time percentiles. 2 7 9 10 11 15 22
The E-Commerce Operations Manager
Uptime over 7 days, 12 months and all time, every incident with its start, end and duration, response times split into DNS, connect, TLS and first byte, monitoring data kept one to two years by plan with API export, probe addresses published for allow-listing, and a branded monthly report per client site emailed on the first of the month with a browser link the agency can open without an account. The vendor states it offers no formal SLA, only a 99.9 percent target, and we found no public information on SLA reports, response time percentiles, or the vendor's own status page and post-mortems. 2 22 11 15 14 7 10
The Information Security Officer
Each incident records start, end and duration with the response code and seeing location per run, uptime percentage is kept for seven days, twelve months and all-time, monitoring data is retained typically one to two years and exportable via API, and opt-in logo-branded monthly reports with selectable sections go to up to five recipients and stay archived on links that need no account. Response-time breakdowns cover DNS, connect, TLS and first byte, and the probe addresses are published in HTML, JSON and CSV. The vendor states it offers no formal SLA with credits (a 99.9 percent target only), and we found no public information on the vendor's own public status page, incident history or response-time percentiles. 2 10 11 14 15 22
The Skeptic
Retention is stated in plain words — monitoring data typically one to two years per plan, certificate history kept, every past monthly report kept on a browser link — export of all monitoring data is offered via the API, probe addresses are published in JSON and CSV and updated automatically, and response times break down into DNS, connect, TLS and time to first byte. Against that, the vendor itself states no formal SLA with credits is offered, only a 99.9% target, and we found no public information on the vendor's own status page, its incident history, post-mortems or response-time percentiles. 2 7 10 11 14 15 22
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where account data, alert contacts (names and phone numbers of the people on call), status page subscribers and check results are stored and processed, and who the subprocessors are (hosting, SMS and phone gateways, email delivery, support and payment tools). Independently sourced by the sovereignty pipeline. Probe locations outside Europe are part of what the product does and are not counted against it; where the data is stored and who processes it is. A self-hosted or open-source edition the customer runs on its own European servers counts as the customer's chain, whatever the vendor's seat.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (SMS and call gateways, email, support, payment) run through non-EU providers without a stated safeguard.
8 — EU hosting on named infrastructure, EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated — or a self-hosted edition documented that keeps every record on the customer's own servers.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting and every subprocessor, or a self-hosted open-source edition with no call home, data export and deletion documented, and certifications published with their scope rather than implied.
The Agency Developer
Immutable VOF in Berlaar, Belgium under Belgian law with Antwerp courts, primary data on Combell in Belgium, performance metrics in ClickHouse's EU region, a published and signable DPA with the 2021/914 Standard Contractual Clauses, and a public subprocessor list naming each provider with its location and certifications. Check reports and backups sit on AWS and probe nodes run on AWS, DigitalOcean and Vultr outside Europe under those SCCs, and the vendor itself states it holds no ISO 27001 or SOC 2 certificate of its own — only its hosting providers do. 7 12 13
The SaaS Platform Engineer
The chain is documented on the vendor's own pages: Immutable VOF in Berlaar is the contracting entity under Belgian law, primary data sits with Combell in Belgium, the data processing agreement is published and signable on every plan with EU standard contractual clauses for transfers, and a public subprocessor list names each processor with its region and certifications. It stops short of a fully European chain: the same list shows backups and check reports stored on AWS Global and notifications sent through Cloudflare Global — processing that relies on the clauses rather than EU regions — and the certifications listed are the providers', with Oh Dear holding none itself. 10 11 12 13 7
The Customer Support Lead
The chain is named end to end: a Belgian company under Belgian law and the Antwerp courts, monitoring data stored in Belgium with Combell, performance metrics in ClickHouse Cloud's EU region, a published data processing agreement with the EU standard contractual clauses, and a public subprocessor list with each provider's location and certifications. The same pages are candid that Oh Dear itself holds no ISO or SOC 2 certificate, that Combell's certificates cover hosting only, and that probe nodes, backups and check reports run on US providers under those clauses — a stated safeguard, not a silent one. 7 10 11 12 13
The E-Commerce Operations Manager
Immutable VOF in Berlaar, Belgium is the contracting entity under Belgian law and the Antwerp courts, primary data sits with Combell in Belgium, performance metrics in ClickHouse Cloud's EU region, a data processing agreement with 2021/914 SCCs is published, and the subprocessor list is public with each provider's location. The chain does run through non-EU names, AWS Global for backups and check reports, Cloudflare for sending notifications and Stripe for payments, with SCC safeguards stated, and the vendor states it holds no ISO or SOC certificate itself, with Combell's ISO 27001 covering the hosting. 7 10 11 12 13
The Information Security Officer
Immutable VOF of Berlaar, Belgium is the contracting entity, primary account and monitoring data sit with Combell in Belgium on ISO 27001-certified infrastructure, and performance metrics sit in ClickHouse Cloud's EU region. The subprocessor list is public with regions and certifications — including US providers for probes, backups and check reports — transfers outside the EU rely on Standard Contractual Clauses (Decision 2021/914) under Belgian law with Antwerp courts, and a GDPR data processing agreement with 48-hour breach notification is published. The vendor candidly states it holds no ISO 27001 or SOC 2 itself (the certificates belong to its hosting chain) and does not claim immunity from the US CLOUD Act, and we found no public information on a self-hosted edition. 7 11 12 13
The Skeptic
Immutable VOF in Berlaar, Belgium is the contracting entity under Belgian law, primary data sits with Combell in Belgium, a data processing agreement with the EU's 2021 standard contractual clauses and a thirty-day subprocessor objection window is published, and the subprocessor list is public with each processor's location and certifications. The vendor is frank that probe nodes, backups and check reports run on US providers, that it claims no CLOUD Act immunity, and that the ISO 27001 certificate belongs to the host rather than to Oh Dear itself. That honesty earns the level, but backups and check reports on US providers and no documented self-hosted edition keep it short of sovereign end to end. 7 10 11 12 13
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by number of monitors, check interval and status pages, team seats and on-call responders, what SMS and phone alerts cost, which features (multi-step or browser checks, SSO, longer retention, private locations, white-label) cost extra, the free tier and its limits, overage handling, minimum term and VAT.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with monitors, intervals, seats or alerts is unclear.
5 — Tiers are public with their monitor count, interval and main inclusions, but at least one commonly needed piece (SMS or call alerts, extra seats, extra status pages, SSO, longer retention) is unpriced or "on request".
8 — Every tier priced publicly with its scaling rule (monitors, interval, seats, responders, status pages), SMS and call costs stated, add-ons priced, overage handling stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given number of monitors, interval, team size and alert volume, with every add-on, overage and support fee and the cancellation and data-return terms published.
The Agency Developer
A public ladder from fifteen euros a month for two sites up to three hundred ninety-nine euros for two hundred, scaling only by monitored sites with every feature — unlimited users, unlimited status pages, SSO, DPA — on every plan, no setup fees and cancel anytime, so the annual cost at my two hundred monitors is computable from the pricing page alone. The gaps: above two hundred sites the Enterprise tier is priced on request, overage handling is not described, SMS costs sit in the customer's own Vonage account, and the captured pages give different figures for VAT — the pricing page shows EUR ex. VAT while the terms say Belgian VAT is included where required. 5 6 9 10
The SaaS Platform Engineer
Ten public tiers from Solo at two sites for €15/mo to Scale at 200 sites for €399/mo scale by exactly one dimension, the number of monitored sites, and SSO, two-factor, unlimited users, unlimited status pages with custom domains, every notification channel, monthly reports and the DPA are on every plan — so there is almost nothing to price separately, with Enterprise above 200 sites quoted as custom. Billing monthly or annually in advance, prorated plan changes at any time, a 10-day trial without a credit card, a 30-day money-back guarantee and 30 days' notice on price rises are all published; SMS is not billed by Oh Dear because it runs through the customer's own Vonage account, and the captured pages give different statements on VAT — prices shown ex. VAT on the pricing page, with the terms saying Belgian VAT is included where required. 5 6 7 9 10 22
The Customer Support Lead
Ten tiers are priced publicly from €15/mo for 2 sites to €399/mo for 200, scaling only by monitored site count, with every feature — status pages, custom domains, single sign-on, two-factor, unlimited users and unlimited notification destinations — included on every plan and no feature tiers, so the real annual cost is derivable from the page alone. SMS runs through the customer's own Vonage account and we found no public information on overage handling; the captured pages also give different figures for VAT treatment, one showing prices ex. VAT and another stating they include applicable Belgian VAT where required. 6 9 10 15
The E-Commerce Operations Manager
Every tier is public from Solo, two sites at €15/mo, up to Scale, 200 sites at €399/mo, scaling only by number of monitored sites, with status pages, all notification channels, single sign-on, two-factor and unlimited users on every plan, no setup fees, cancel anytime, monthly or annual billing in advance, a ten-day trial without credit card, and VAT treatment stated on both the pricing page and the terms. What I cannot compute from these pages is SMS, which runs through my own Vonage account, and we found no public information on overage handling beyond prorated plan changes. 9 10 6 7 22
The Information Security Officer
Ten named tiers from €15/month for two sites up to €399/month for 200, scaling only by monitored sites, with single sign-on, two-factor, unlimited users, unlimited status pages and all checks on every plan, no setup fees, monthly or annual billing in advance, cancel anytime, a 30-day money-back guarantee, 30 days' notice of price rises, EU payment methods, and SMS priced through the customer's own Vonage account rather than per message. The Enterprise tier above 200 sites is quoted on request, and there is a 10-day trial without credit card but we found no public information on a permanent free tier. The pricing page states prices in EUR excluding VAT while the terms state prices include applicable Belgian VAT where required — the captured pages give different figures for VAT treatment, so a buyer should confirm which applies before signing. 5 9 10 22
The Skeptic
Nine tiers from Solo at €15/mo for two sites to Scale at €399/mo for two hundred are public, and the only dimension that scales is the number of monitored sites — every feature, unlimited users, single sign-on and unlimited status pages sit on every plan, billed monthly or annually, cancel anytime, with a thirty-day money-back guarantee and thirty days' notice of price increases. SMS runs through the customer's own Vonage account so no per-message price appears on these pages, no overage handling is described, Enterprise at 200+ sites is custom, and the captured pages give different figures for VAT — the pricing page says EUR ex. VAT while the terms say prices include applicable Belgian VAT where required. 6 7 9 10 22
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined ⚠ unverified | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Oh Dear
Is Oh Dear European?
Yes. whats-best.ai classifies Oh Dear as EU-Made.
Where does Oh Dear store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention Belgium as hosting location, per the vendor’s page captured 1 Nov 2026.
Does Oh Dear have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to Oh Dear?
As of 2 Nov 2026, the panel rates Hyperping (3.5/5), Checkly (3.5/5) and openstatus (3.5/5) highest among the other 14 Uptime Monitoring & Status Pages products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Hyperping (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Oh Dear alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Open source, Hosting location, Legal entity. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 6 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 5 subprocessors facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (24)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage ohdear.app Checked 1 Nov 2026 Details →
- 2 Features page (uptime monitoring) ohdear.app Checked 1 Nov 2026 Details →
- 3 Features page (certificate monitoring) ohdear.app Checked 1 Nov 2026 Details →
- 4 Features page (cron and scheduled task monitoring) ohdear.app Checked 1 Nov 2026 Details →
- 5 Features page (status pages) ohdear.app Checked 1 Nov 2026 Details →
- 6 Features page (notifications) ohdear.app Checked 1 Nov 2026 Details →
- 7 Features page (GDPR) ohdear.app Checked 1 Nov 2026 Details →
- 8 API documentation ohdear.app Checked 1 Nov 2026 Details →
- 9 Pricing page ohdear.app Checked 1 Nov 2026 Details →
- 10 Terms of service (names the operating company) ohdear.app Checked 1 Nov 2026 Details →
- 11 Privacy policy ohdear.app Checked 1 Nov 2026 Details →
- 12 Data processing agreement (dpa) ohdear.app Checked 1 Nov 2026 Details →
- 13 Subprocessor list ohdear.app Checked 1 Nov 2026 Details →
- 14 Checks, locations & failure confirmation — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 15 Checks, locations & failure confirmation — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 16 Alerting, escalation & on-call — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 17 Alerting, escalation & on-call — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 18 Status pages & incident communication — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 19 Status pages & incident communication — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 20 API, monitoring as code & team administration — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 21 API, monitoring as code & team administration — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 22 Uptime reports, data & the vendor's own reliability — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 23 Uptime reports, data & the vendor's own reliability — found from sitemap ohdear.app Checked 1 Nov 2026 Details →
- 24 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →