Uptime Monitoring & Status Pages
Phare Uptime
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Lightkeeper OÜ · phare.io
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.
Phare Uptime at a glance
- Vendor
- Lightkeeper OÜ
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Starting price
- “No artificial feature gating, starting at 5€ per month.” (vendor’s words) source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Phare Uptime 3/5, the mean of 6 judges. Phare Uptime, an uptime monitoring and status-page service from Lightkeeper OÜ in Estonia, scores highest on pricing transparency — five of six judges gave 8 — on published tiers (Hobby free forever, Scale at 5€ /mo plus usage), published per-unit overages and unlimited team members and projects. 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
Phare Uptime, an uptime monitoring and status-page service from Lightkeeper OÜ in Estonia, scores highest on pricing transparency — five of six judges gave 8 — on published tiers (Hobby free forever, Scale at 5€ /mo plus usage), published per-unit overages and unlimited team members and projects. Checks and locations sits at 7 across the bench: HTTP(S), TCP and ICMP checks from twelve named regions, down to every 30 seconds, with a documented rule for how many regions must fail before an incident is confirmed. Sovereignty split 7 versus 8, with the SMS gateway Infobip's listed Global data location and the absence of public information on an ISO 27001 or SOC 2 certification for Phare itself cited in rationales on both sides. Alerting, status pages and automation split 6 versus 7 on the same class of gap: no public information on on-call rotations, escalation policies or in-app acknowledgement; email or SMS subscribers; SCIM provisioning or audit logs. Reports and reliability tops out at 6. One judge, the security officer, scored 0 on six of seven criteria (weighted total 0.8), against 6.6-7.0 for the rest.
Speaks for it
- Checks from twelve named regions down to every 30 seconds, with a documented rule for how many regions must fail before an incident is confirmed.
- Both public tiers priced exactly — Hobby free forever with no credit card required, Scale at 5€ /mo plus usage — with per-unit overages published, unlimited team members, projects, status pages and subscribers, and a 30-day refund.
- A first-party, MIT-licensed Terraform provider and a documented REST API cover monitors, status pages, incidents, maintenance windows, alert rules and reports.
- A published data processing agreement incorporates standard contractual clauses by reference, with hosting at Hetzner in Germany, encrypted backups at Scaleway in France, and a subprocessor list naming each provider's location and certifications.
- Per-notification delivery logs record whether each alert arrived, backed by retries spread across three email providers.
Held against it
- We found no public information on escalation policies with timeouts, on-call schedules and rotations, or acknowledging and resolving an alert from the app.
- We found no public information on browser or multi-step transaction checks, DNS record or domain-expiry checks, or cron and heartbeat monitoring.
- The vendor states fixed probe IP addresses cannot be provided because monitoring traffic comes from Bunny.net shared ranges.
- The SMS and voice subprocessor Infobip is listed as a United Kingdom company with data location Global, and we found no public information on an ISO 27001 or SOC 2 certification for Phare itself.
- VAT treatment is not stated, and the Custom plan with on-premise monitoring is priced only on request.
Best for
- You monitor websites, APIs and servers with HTTP, TCP and ping checks and want a configurable number of regions to confirm a failure before anyone is paged.
- You manage many clients or projects and want monitors, status pages and alert rules managed as code through a first-party Terraform provider and a documented REST API.
- You need a European legal and hosting setup for procurement: an Estonian contracting entity, Hetzner hosting in Germany, Scaleway backups in France and a published DPA with standard contractual clauses.
- You want costs you can compute in advance: published tiers, published per-unit overages, unlimited team members and projects, and a 30-day refund.
Avoid if
- You rely on IP allowlisting to admit monitoring traffic — the vendor states fixed probe IP addresses cannot be provided because checks come from Bunny.net shared ranges.
- You need the platform itself to run on-call rotations, escalation with timeouts and alert acknowledgement — the documented alerting is channel delivery with rate limits, quiet hours and delivery logs.
- You need SMS or voice alerts on the free tier — they require the Scale plan, which includes 20 SMS/voice alerts and bills additional ones at.1€ per unit.
- Your status-page audience subscribes by email or SMS — the documented subscriber channels are RSS, Atom and Slack.
The scores
| Criterion | Panel median |
|---|---|
| Checks, locations & failure confirmation | 3.5 of 5 |
| Alerting, escalation & on-call | 3.5 of 5 |
| Status pages & incident communication | 3.5 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(S), TCP and ICMP ping checks with status-code, header and body assertions, a 30-second minimum interval and twelve named regions where a configurable number of regions must fail before an incident is confirmed — exactly the false-alarm protection I want across sixty client sites. SSL certificates are automatically discovered with expiry warnings one to sixty days ahead, a private agent and Web Bot Auth cover protected backends, and maintenance windows are first-class objects in the API. We found no public information on DNS record checks, domain expiry monitoring, cron or heartbeat checks, or browser and transaction checks, and fixed probe IP addresses cannot be provided because checks run on shared Bunny.net ranges. 2 3 13 14
The SaaS Platform Engineer
HTTP(S) checks with status-code and response-body assertions, custom headers and bodies, TCP with TLS, ICMP ping, and a certificate suite with discovery, inventory and expiry alerts, running as often as every 30 seconds from twelve regions listed by city. The confirmation logic I care about is documented — an incident is only created after a configurable number of regions or consecutive checks fail — and a private agent plus the Web Bot Auth standard covers internal services. We found no public information on multi-step request chains, browser or transaction checks, DNS record or domain expiry checks, or cron and heartbeat monitoring. 2 3 5 13 14
The Customer Support Lead
HTTP(S), TCP and ping checks run as fast as every 30 seconds from twelve named regions, with documented confirmation logic: a configurable number of failing regions or consecutive failures must occur before an incident is created. Assertions on status code, response headers and body, custom headers and request bodies, SSL certificate discovery with expiry alerts, maintenance windows and a private monitoring agent are all documented. We found no public information on browser or multi-step user-journey checks, or on DNS record and domain-expiry monitoring. 2 3 13 14
The E-Commerce Operations Manager
The documentation shows HTTP(S) checks with status-code, header and body assertions, TCP with plain or TLS, ICMP ping, SSL expiry alerts 1 to 60 days ahead, intervals down to 30 seconds, twelve regions named by city, a documented rule for how many regions must fail before an incident is confirmed, a private monitoring agent, and maintenance windows — enough to watch the checkout endpoint with assertions, not just the homepage. We found no public information on browser or transaction checks that walk a real checkout flow, or on heartbeat, DNS-record and domain-expiry checks; the documentation also states monitoring traffic comes from shared ranges so fixed probe IPs cannot be provided, though the user agent string is published. 2 3 5 13 14
The Information Security Officer
HTTP(S) with status-code, header and body assertions, TCP with TLS, ICMP ping, SSL certificate discovery with expiry alerts from 1 to 60 days ahead, and checks as often as every 30 seconds from named city locations across four continents, with multi-region confirmation logic documented before an incident is created. A private monitoring agent and the Web Bot Auth standard (RFC 9421) cover protected internal infrastructure, and the monitoring user agent string is published. We found no public information on DNS record or domain expiry checks, cron or heartbeat monitoring, multi-step sequences, or browser-level transaction checks, which keeps this below the top band. 2 3 13 14
The Skeptic
Twelve regions named down to the city, checks as fast as every thirty seconds, and the confirmation logic written down: I can require several regions to fail at once before an incident exists, which is exactly the false-alarm control I look for. Status-code, header and body assertions, redirect following, SSL certificate expiry alerts configurable one to sixty days ahead, a private agent option, and a published user agent. I found no public information on DNS or domain-expiry checks, cron or heartbeat monitoring, or browser and multi-step transaction checks, so I stop below the top band. 2 3 5 13 14
Alerting, escalation & on-call
panel disagrees
Show reasoningHide reasoning
How this is scored
How the right person learns about a failure: alert channels (email, SMS, phone call, push app, Slack, Microsoft Teams, Telegram, webhooks), alerts to PagerDuty, Opsgenie or similar tools, escalation policies when an alert is not acknowledged, on-call schedules and rotations, acknowledge and resolve from the app, alert grouping and noise reduction, recovery notifications, maintenance windows that mute alerts, and whether SMS and calls are included or charged per message.
0 — No alerting at all; results can only be viewed in the dashboard.
3 — Email alerts and one or two chat integrations; escalation, phone calls and schedules are basic or not described.
5 — Email, SMS, a mobile push app, Slack, Microsoft Teams and webhooks, alerts forwarded to PagerDuty or Opsgenie, per-monitor alert contacts, recovery notifications, a delay or threshold before alerting, and maintenance windows that mute alerts.
8 — Phone call alerts, escalation policies with timeouts, on-call schedules and rotations with overrides, acknowledge and resolve from the app or chat, alert grouping, incident timelines with who did what, and the price of SMS and calls stated per country or included in the plan.
10 — On-call that replaces a separate incident tool: follow-the-sun schedules, escalation across teams, alert routing by service and severity, post-incident reviews generated from the timeline, and delivery of every alert channel monitored and reported.
The Agency Developer
Email, SMS, Telegram, Slack, Discord, Pushover, ilert, Ntfy.sh and custom outgoing webhooks are all documented, driven by alert rules with event, scope, rate limiting and quiet hours, an aggressive retry policy that spreads email over three SMTP providers, and notification logs that show whether each alert actually arrived. Smart incident merging groups related failures into one evolving incident with automatic recovery and partial-recovery notifications. SMS and voice sit behind the Scale plan with twenty included alerts, additional alerts at.1€ per unit and a published country list; we found no public information on escalation policies with timeouts, on-call schedules and rotations, or acknowledging and resolving from the app or chat. 4 8 15 16 18
The SaaS Platform Engineer
Incident alerts go out over email, SMS and voice, Slack, Discord, Telegram, Pushover, Ntfy.sh, ilert and custom webhooks, with recovery events, rate limits, quiet hours, smart merging of related failures, an event timeline, and per-notification delivery logs backed by aggressive retries across three mail providers. Twenty SMS / voice alerts are included on the Scale plan with extras billed at.1€ per unit and the supported country list published. We found no public information on escalation policies with timeouts, on-call schedules and rotations, or acknowledging an alert from the app or chat, so an unanswered 3 a.m. page needs ilert or similar to reach a second person. 4 8 12 15 16 18
The Customer Support Lead
Alerts go out by email, SMS, voice, Slack, Discord, Telegram, Pushover, ilert and outgoing webhook, with rate limits, quiet hours, recovery notices, smart merging of related failures, delivery retries across three email providers, and notification logs showing whether each message arrived; the Scale plan includes 20 SMS/voice alerts with additional ones billed at.1€ per unit. We found no public information on escalation policies with timeouts, on-call rotations and overrides, or acknowledging an incident from the app or chat, which my nine-person team would still need a separate arrangement for. 4 8 15 16 18
The E-Commerce Operations Manager
SMS and voice alerts reach Germany, Austria and Switzerland on the paid plan, with twenty included and additional alerts billed at.1€ per unit, and channels span email, Slack, Discord, Telegram, Pushover, ilert, ntfy and webhooks, with rate limiting, quiet hours, an aggressive retry policy using three email providers and delivery logs for every notification. What decides it: we found no public information on escalation policies with timeouts, on-call schedules or rotations, or acknowledging from the app — a night-duty phone that sleeps through the SMS wakes nobody else. 4 8 15 16 18
The Information Security Officer
Alerts go out over email, SMS, Slack, Discord, Telegram, Pushover, ilert, Ntfy.sh and custom outgoing webhooks, with rate limiting, quiet hours, retries across three email providers, per-notification delivery logs, smart incident merging and automatic recovery notifications, and the SMS integration documents supported countries, phone verification and a 100-member limit. Voice and SMS are quota-based on the Scale plan with overage at.1€ per unit. We found no public information on escalation policies with timeouts, on-call schedules and rotations, or acknowledging and resolving an alert from the app, so this cannot stand in for a dedicated on-call tool. 4 8 15 16 18
The Skeptic
Email, SMS and voice, Slack, Discord, Telegram, Pushover, ilert, ntfy and outgoing webhooks, with an aggressive retry across three SMTP providers and per-notification logs recording whether each alert actually arrived — that delivery record is rare and I value it. Rate limits, quiet hours, smart incident merging, recovery events and maintenance windows are documented, and SMS and voice are priced at.1€ per extra alert with the covered countries listed. I found no public information on escalation policies, on-call schedules and rotations, or acknowledging and resolving from the app, which is what would carry this into real on-call territory. 4 8 15 16 18
Status pages & incident communication
panel disagrees
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 custom domains with SSL or a provided subdomain, monitor groups with aggregated status, and a bar-per-day availability history over 30, 60 or 90 days — enough to give every client group its own page. Incident updates in four states publish to connected pages automatically, scheduled maintenance is broadcast, subscribers get RSS, Atom and Slack feeds at no extra cost, and private pages work through password, token or IP allowlist. We found no public information on email or SMS subscribers, per-component subscriptions, multiple languages, or incident templates. 5 6 8 17
The SaaS Platform Engineer
Status pages run on your own domain with SSL, monitors appear as components with collapsible groups and per-day availability bars, monitor-triggered incidents publish updates automatically to connected pages with impact levels, and scheduled maintenance can be broadcast; subscribers get RSS, Atom and Slack feeds with unlimited subscribers, and privacy via password, access token or IP allowlist. We found no public information on email or SMS subscribers to the page itself, per-component subscriptions, several languages, incident templates, or documentation of hosting kept separate from the main service. 5 6 8 17 18
The Customer Support Lead
Branded status pages on our own domain with SSL, monitors grouped into collapsible groups showing aggregated status, unmonitored components displayed by hand, a per-day availability history with an overall percentage over a 30, 60 or 90 day window, incident updates in four states published automatically, scheduled maintenance broadcast to the page, and private pages behind a password, token or IP allowlist for our largest accounts, with unlimited subscribers at no extra cost via RSS, Atom and Slack. We found no public information on email subscribers to status pages or saved incident templates, which matters after three hundred identical tickets. 5 6 8 17 18
The E-Commerce Operations Manager
Custom domains with SSL, monitor groups with aggregated availability, one bar per day of history over a 30, 60 or 90-day window, incident updates published automatically, scheduled maintenance broadcast, private pages by IP, token or password, embeddable badges and unlimited subscribers through RSS, Atom and Slack. For a shop selling to German customers the gap is subscriber channels: we found no public information on email or SMS notifications to status-page subscribers, on several languages, on incident templates, or on how the page stays online if the main service is down. 5 6 8 17 18
The Information Security Officer
Status pages run on unlimited custom domains with SSL, monitor groups with aggregated status and combined history, daily availability bars over a 30, 60 or 90 day window, incident updates in defined states published straight from the incident, scheduled maintenance broadcasts, RSS, Atom and Slack feeds, embeddable badges, and private pages behind password, token or IP allowlist on the Scale plan, with unlimited subscribers at no extra cost. Incident summaries and post-mortems can be AI-generated. We found no public information on email or SMS subscribers, per-component subscriptions, multiple languages, incident templates, or how the status page itself stays available if the main service is down. 5 6 8 17 18
The Skeptic
Custom domain with SSL, monitors grouped into collapsible components with per-monitor daily availability bars, incident updates with states published to the page automatically, scheduled maintenance broadcast, and unlimited pages and subscribers. Private access via password, token or IP allowlist, branding with logo and themes, and embeddable Shields.io badges. The subscriber channels documented are RSS, Atom and Slack — I found no public information on email or SMS subscribers, several languages, incident templates, or how the page itself stays online when the platform is down. 5 6 8 17 18
API, monitoring as code & team administration
panel disagrees
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 reaches monitors, status pages, incidents, alert rules, maintenance windows and reports with project- or organization-scoped bearer keys in read-only or read-write levels, and a first-party open-source (MIT licence) Terraform provider manages projects, monitors, status pages and alert rules — the route I would take to roll out two hundred monitors. Two-factor authentication, unlimited team members and projects, and OIDC single sign-on with Okta, Entra ID and Google Workspace are documented, along with Ansible and NixOS. We found no public information on SCIM provisioning, audit logs, checks triggered from CI/CD, or white-label client reports. 7 8 19 20
The SaaS Platform Engineer
A first-party Terraform provider under an MIT licence manages projects, monitors, status pages and alert rules, so checks can live in version control next to the services they test, and a documented REST API covers monitors, incidents, maintenance windows, status pages and reports with project- or organization-scoped keys in read-only or read-write levels. Two-factor authentication and OIDC single sign-on with Okta, Entra ID and Google Workspace are shown. We found no public information on SCIM provisioning, audit logs, client sub-accounts with their own logins, white-label client reports, bulk import, or checks triggered from CI/CD. 1 8 19 20
The Customer Support Lead
A documented REST API covers monitors, incidents, maintenance windows, status pages and reports, with bearer-token keys scoped to a project or the whole organisation at read-only or read-write level, and a first-party open-source Terraform provider manages projects, monitors, status pages and alert rules as code, with Ansible and NixOS also listed. Unlimited team members and projects, two-factor login and single sign-on via Okta, Entra ID or Google Workspace are documented. We found no public information on SCIM provisioning, audit logs, client sub-accounts or white-label reports. 1 8 19 20
The E-Commerce Operations Manager
A first-party, open-source Terraform provider manages projects, monitors, status pages and alert rules, with Ansible and NixOS listed too, a documented REST API covering monitors, incidents, status pages, maintenance windows and reports with project- and organisation-scoped keys, two-factor authentication, OIDC single sign-on with Okta, Entra ID and Google Workspace, and unlimited team members across unlimited projects. We found no public information on SCIM provisioning, audit logs, client sub-accounts with their own logins, white-label client reports or bulk import of monitors. 1 2 8 19 20
The Information Security Officer
A documented REST API covers monitors, status pages, incidents, maintenance windows and reports, with bearer-token keys at project or organization scope, read-only or read-write access levels and Owner/Admin control over key creation; a first-party open-source Terraform provider manages projects, monitors, status pages and alert rules, with Ansible and NixOS alongside, and single sign-on is OIDC-based (Okta, Entra ID, Google Workspace) with two-factor authentication. Before I would let logins loose, though, I need more: we found no public information on an audit log of user actions, SCIM provisioning, client sub-accounts with their own logins, or white-label reporting, and bulk import is likewise undocumented. 2 8 19 20
The Skeptic
A first-party, MIT-licensed Terraform provider managing projects, monitors, status pages and alert rules, plus a documented API spanning incidents, maintenance windows and reports with project- and organization-scoped keys and granular access levels. Owner and Admin roles, two-factor authentication and OIDC single sign-on with Okta, Entra ID and Google Workspace are evidenced. I found no public information on SCIM provisioning, audit logs, bulk import of monitors, checks run from CI/CD, client sub-accounts or white-label reporting. 8 11 19 20
Uptime reports, data & the vendor's own reliability
panel disagrees
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
Report endpoints return downtime seconds, availability percent, MTTR, MTBF and highest impact per monitor and per project over windows up to a year, response times are tracked at P75, P90 and P99, and SLA targets can be reported with planned maintenance excluded from downtime. The captured pages give different figures for how long results are kept — uptime monitoring data kept for one year, and reporting tracked for up to 90 days — while the monitoring user agent is published but fixed probe IP addresses cannot be provided. We found no public information on scheduled email reports, CSV export, a public incident history with post-mortems, or an SLA with credits, though a Service status link exists in the dashboard. 3 7 9 13 21 22
The SaaS Platform Engineer
Availability, downtime, MTTR and MTBF are reported per monitor and per project over windows up to a year, response-time trends come in P75, P90 and P99, check results are kept one year, planned maintenance can be excluded from SLA figures, and reports are retrievable by API. The vendor states fixed probe IP addresses can't be provided because monitoring runs from Bunny.net shared ranges, though the user agent is published and Web Bot Auth covers authenticated endpoints. We found no public information on scheduled email reports, a raw export of check results, a published SLA with credits, or the vendor's own incident history and post-mortems. 3 9 13 21 22
The Customer Support Lead
Uptime statistics per monitor and per project — availability, downtime seconds, MTTR, MTBF and highest incident impact — come back from the API for windows up to a year, with P75/P90/P99 response-time trends, SLA reporting sliced by region, planned maintenance and individual incidents excludable from downtime, and uptime data kept for one year. A service status link appears in their navigation, but we found no public information on the vendor's own status history, an SLA with credits, or scheduled email reports. The pages state that fixed probe IP addresses cannot be provided because checks come from shared ranges, though the monitoring user agent is published. 3 7 9 13 21 22
The E-Commerce Operations Manager
Reports give downtime seconds, availability percentage, MTTR, MTBF and highest incident impact per monitor and per project over windows up to a year — matching the stated one-year retention and exactly what I need to show the agency what six hours of dead checkout cost — plus response-time percentiles at P75, P90 and P99 and maintenance excludable from SLA numbers. We found no public information on scheduled email reports, branded client-ready reports, CSV or raw export of results, or the vendor's own incident history and post-mortems, and the documentation states fixed probe IPs cannot be provided; a service-status link exists in the navigation. 3 7 9 13 21 22
The Information Security Officer
Per-monitor and per-project reports expose availability percentage, downtime seconds, MTTR and MTBF over windows up to a year, with P75/P90/P99 response-time quantiles, SLA targets that exclude planned maintenance, and uptime data retention of one year, all retrievable through the API — enough structure to evidence detection and resolution times for NIS2 or ISO 27001. The monitoring user agent is published, but the vendor states fixed probe IP addresses cannot be provided because traffic comes from Bunny.net shared ranges. We found no public information on scheduled email reports, raw check-result export, a published SLA with credits, or the vendor's own incident history and post-mortems, and the on-premise option exists only as an enterprise enquiry on a custom plan. 3 8 9 13 21 22
The Skeptic
Retention is stated outright — uptime data kept one year — and reports are reachable by API for windows up to a year with availability, downtime, MTTR and MTBF per monitor, P75/P90/P99 response times, and SLA figures that can exclude planned maintenance and specific incidents. The user agent is published, but fixed probe IPs are explicitly not available since checks come from Bunny.net shared ranges. I found no public information on raw check-result export, the vendor's own incident history or post-mortems, or a standard SLA with credits — on-premise appears only as an on-request enterprise line. 3 7 9 13 21 22
European sovereignty
panel opinion
panel disagrees
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
Lightkeeper OÜ in Estonia is the contracting entity, the data processing agreement is governed by Estonian law with exclusive jurisdiction in Tallinn, application and database hosting runs at Hetzner in Germany with encrypted backups at Scaleway in France, and the agreement incorporates standard contractual clauses by reference. The subprocessor list names every provider with its location — Brevo, Lettermint, Scaleway, Mistral AI, Klibon and Vemetric in the EU, Paddle for billing, Sentry as a US company with data in Germany — while Infobip handles SMS and voice with its data location given as Global. Certifications like ISO 27001 and SOC 2 are stated for the subprocessors, but we found no public information on such a certification for Phare itself. 9 11 12
The SaaS Platform Engineer
Lightkeeper OÜ of Tallinn contracts under Estonian law, applications and databases sit on Hetzner in Germany with encrypted backups at Scaleway in France, a DPA is published with SCCs incorporated and breach-notification commitments, and the subprocessor page names every provider with location and certifications — Brevo, Lettermint, Scaleway, Mistral AI and Vemetric in the EU, Sentry's data in Germany — with 30 days' notice and an objection right on changes. Infobip, the SMS and voice gateway, lists its data location as Global, and Paddle acts as merchant of record under its own terms. We found no public information on certifications for Phare itself or on a generally available self-hosted edition; on-premise appears only as a custom enterprise arrangement. 1 9 10 11 12
The Customer Support Lead
The contracting entity is Lightkeeper OÜ in Estonia under Estonian law with the courts of Tallinn; the platform runs on Hetzner in Germany with encrypted backups at Scaleway in France, and the published sub-processor list names each provider with its location and certifications — email via Brevo, Lettermint and Scaleway, SMS and voice via Infobip (UK company, global data location), analytics via Vemetric, error tracking via Sentry (US company, data in Germany), payments via Paddle. A data processing agreement with standard contractual clauses incorporated by reference and 30 days' notice on sub-processor changes is published. The global data location of the SMS and voice gateway is a stated weak link in the chain, and we found no public information on a certification for Phare itself. 1 9 11 12
The E-Commerce Operations Manager
The contracting entity is Lightkeeper OÜ in Estonia under Estonian law with exclusive jurisdiction in Tallinn, application and database hosting runs at Hetzner in Germany with encrypted backups at Scaleway in France, a data processing agreement is published with standard contractual clauses incorporated by reference, and a sub-processor list names each provider with country, data location and certifications. One chain element to know before handing over duty phone numbers: the SMS and voice gateway Infobip is listed with country United Kingdom and data location Global, and Sentry is a United States company processing in Germany. 1 9 11 12
The Information Security Officer
The contracting entity is Lightkeeper OÜ in Estonia under Estonian law with exclusive jurisdiction in Tallinn; application and database hosting is Hetzner in Germany with encrypted backups on Scaleway in France, and a published DPA incorporates standard contractual clauses by reference, sets breach-notification duties and grants 30 days notice with objection rights on subprocessor changes, while the subprocessor list names Brevo, Lettermint, Mistral AI, Vemetric, Klibon, Scaleway, Sentry, Aikido and Infobip with locations and certifications. Two things hold it below the top step for me: Infobip, which carries my on-call staff's phone numbers for SMS and voice, is UK-incorporated with its data location given as Global, and we found no public information on the vendor's own ISO 27001 or SOC 2 certification or a self-hosted edition open to all customers. 9 11 12
The Skeptic
Lightkeeper OÜ under Estonian law with Tallinn courts, application and database on Hetzner in Germany, encrypted backups on Scaleway in France, email infrastructure in France, CDN in Slovenia, and a subprocessor page with locations, certifications, thirty days' change notice and a published DPA with standard contractual clauses incorporated by reference. Two links in the chain wobble: SMS and voice run through Infobip, a United Kingdom company whose data location is stated as Global, and error tracking through Sentry, a United States company hosting in Germany. The certifications shown belong to the subprocessors — I found no public information on an ISO 27001 or SOC 2 certification for Phare itself. 1 9 11 12
Pricing transparency
panel disagrees
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
Both tiers are public — Hobby free forever with 100,000 monitoring events and no credit card, and Scale at 5€ /mo + additional usage with 500,000 events — metered per check event with a worked example, additional events at.00001€ per unit, additional alerts at.1€ per unit and AI generations at.01€ per unit. Overage handling is explicit: a 10% buffer, warnings before and at exhaustion, then automatic pause until the next billing period, on monthly cycles with cancel-anytime and a 30-day no-questions refund; SMS and voice require the Scale plan with twenty included alerts. We found no public information on VAT treatment, and the Custom tier with on-premise monitoring and custom SLAs is available only on request. 8 9 16
The SaaS Platform Engineer
Hobby is free with 100 000 monitoring events and Scale is 5€ /mo + additional usage with 500 000 events, 20 SMS / voice alerts and 100 AI summaries, and the metered model is fully spelled out: an event is one HTTP, TCP or ICMP check with a worked example, extras at.00001€ per event,.1€ per alert and.01€ per AI generation, a 10% overage buffer with notice before exhaustion and monitoring paused rather than surcharged. Team members, projects and integrations are unlimited on every plan, terms are monthly with three cancellation channels and a 30-day refund. We found no public information on VAT treatment, and the Custom tier is priced on request. 8 9 16
The Customer Support Lead
Both public plans are priced plainly — Hobby free forever with 100,000 events and no credit card, and Scale at 5€ per month with 500,000 events, 20 SMS/voice alerts, unlimited private status pages and single sign-on — and the metered model is explained down to the arithmetic: roughly 90,000 events if two regions check every minute, with additional usage at.00001€ per event,.1€ per unit for alerts and.01€ per unit for AI generations, a 10% overage buffer with notice before monitoring pauses, monthly cycles and cancellation at any time. We found no public information on VAT treatment, and the Custom plan is quoted on requirements rather than priced. 2 8 9
The E-Commerce Operations Manager
Hobby is free forever with 100,000 monitoring events and unlimited team members and projects, Scale is 5€ /mo plus additional usage with 500,000 events, 20 SMS / voice alerts, private status pages and SSO, and overages are published — events at.00001€ per unit, SMS at.1€ per unit, AI generations at.01€ per unit — with a 10% overage buffer, pause on exhaustion, monthly billing and a 30-day no-questions refund, plus a worked example of how events accumulate. VAT treatment is the one piece we found no public information on; seat count never enters the price because team members are unlimited. 8 9 16
The Information Security Officer
Both public tiers are priced exactly — Hobby free forever and Scale at 5€ per month plus usage — with the metering rule published (one event per HTTP, TCP or ICMP check, including a worked example of roughly 90,000 events for two regions at one-minute checks), overage unit prices for events at.00001€, alerts at.1€ and AI generations at.01€, a 10% overage buffer with automatic pause, 20 SMS or voice alerts and 100 AI summaries included on Scale, monthly billing, a 30-day refund and named cancellation channels. Unlimited team members, projects, status pages and subscribers remove most seat-count surprises. VAT treatment is not stated and the enterprise plan is a requirements enquiry, which is what keeps this from full computability. 8 9 18
The Skeptic
Hobby is free with its quota spelled out, Scale is 5€ per month plus usage, and the scaling rule is public: events at.00001€ each, extra SMS or voice at.1€ each, AI generations at.01€ each, with a worked example of roughly ninety thousand events, a ten percent overage buffer with automatic pause, thirty-day refunds and cancel-anytime monthly billing. The remaining gaps: VAT treatment is not stated, and the Enterprise tier is priced only on request. 8 9 16
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined ⚠ unverified | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Phare Uptime
Is Phare Uptime European?
Yes. whats-best.ai classifies Phare Uptime as EU-Made.
Where does Phare Uptime store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Phare Uptime have a free plan?
Yes. Phare Uptime has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Phare Uptime?
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: Phare Uptime 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 — Hosting location, Hosting options, Legal entity, Data processing agreement. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 7 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
- 6 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
- 3 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
- 2 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
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (23)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage phare.io Checked 1 Nov 2026 Details →
- 2 Features page (uptime) phare.io Checked 1 Nov 2026 Details →
- 3 Features page (website monitoring) phare.io Checked 1 Nov 2026 Details →
- 4 Features page (alerting) phare.io Checked 1 Nov 2026 Details →
- 5 Features page (incident management) phare.io Checked 1 Nov 2026 Details →
- 6 Features page (status pages) phare.io Checked 1 Nov 2026 Details →
- 7 Documentation docs.phare.io Checked 1 Nov 2026 Details →
- 8 Pricing page phare.io Checked 1 Nov 2026 Details →
- 9 Terms of service (names the operating company) phare.io Checked 1 Nov 2026 Details →
- 10 Privacy policy phare.io Checked 1 Nov 2026 Details →
- 11 Data processing agreement (dpa) phare.io Checked 1 Nov 2026 Details →
- 12 Subprocessor list phare.io Checked 1 Nov 2026 Details →
- 13 Checks, locations & failure confirmation — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 14 Checks, locations & failure confirmation — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 15 Alerting, escalation & on-call — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 16 Alerting, escalation & on-call — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 17 Status pages & incident communication — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 18 Status pages & incident communication — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 19 API, monitoring as code & team administration — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 20 API, monitoring as code & team administration — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 21 Uptime reports, data & the vendor's own reliability — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 22 Uptime reports, data & the vendor's own reliability — found from sitemap docs.phare.io Checked 1 Nov 2026 Details →
- 23 Code repository (open-source licence) — found from the homepage github.com Checked 1 Nov 2026 Details →