# Phare Uptime — Uptime Monitoring & Status Pages

Phare Uptime by Lightkeeper OÜ holds a panel rating of 3/5 from 6 AI judges (category median 3/5), as of 2026-11-02. Provenance: EU-Made; sovereignty: not determined.

- Vendor: Lightkeeper OÜ (https://phare.io)
- Category: [Uptime Monitoring & Status Pages](https://whats-best.ai/software/uptime-monitoring.md)
- Provenance (editorial classification): EU-Made
- Canonical page: https://whats-best.ai/software/uptime-monitoring/phare
- Alternatives: https://whats-best.ai/software/uptime-monitoring/phare/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/phare/alternatives.md))
- Data as of: 2026-11-06 · evaluated 2026-11-02 · oldest source captured 2026-11-01

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## 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 [S1]
- Starting price: “No artificial feature gating, starting at 5€ per month.” (vendor’s words) [S8]

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

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Developer | The SaaS Platform Engineer | The Customer Support Lead | The E-Commerce Operations Manager | The Information Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Checks, locations & failure confirmation | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Alerting, escalation & on-call | 3.5/5 | 3.5/5 | 3/5 | 3.5/5 | 0/5 | 3/5 |
| Status pages & incident communication | 3.5/5 | 3.5/5 | 3.5/5 | 3/5 | 0/5 | 3/5 |
| API, monitoring as code & team administration | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 0/5 | 3/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 3/5 | 3/5 | 0/5 | 3/5 |
| European sovereignty | 3.5/5 | 4/5 | 4/5 | 4/5 | 0/5 | 3.5/5 |
| Pricing transparency | 4/5 | 4/5 | 4/5 | 4/5 | 0/5 | 4/5 |
| **Weighted verdict** | **3.5/5** | **3.5/5** | **3.5/5** | **3.5/5** | **0.5/5** | **3.5/5** |

### The judges

- **The Agency Developer** (v1.0): Runs hosting and maintenance at a fifteen-person web agency with sixty client sites on WordPress, TYPO3 and Shopware. Has learned about an expired certificate from a client's angry phone call once and does not want a second time. Wants HTTP, keyword, SSL and domain expiry checks set up in bulk, client groups with their own status pages and monthly uptime reports, and a price per monitor that still works at two hundred monitors.
- **The SaaS Platform Engineer** (v1.0): Platform engineer at a forty-person B2B SaaS in Berlin, one of four people on the on-call rotation. Wants multi-step API checks with assertions, kept in Terraform next to the services they test, failures confirmed from a second location before anyone is woken, phone calls and escalation when an alert is not acknowledged, and a status page that updates without someone logging in at 3 a.m.
- **The Customer Support Lead** (v1.0): Leads a support team of nine at a software company whose customers are tax advisers and payroll offices. During the last outage the team answered three hundred tickets that all asked the same question. Wants a status page on the company's own domain with components customers recognise, incident templates, subscribers notified by email, a private page for the largest accounts, and an uptime history they can point to in a contract renewal.
- **The E-Commerce Operations Manager** (v1.0): Runs operations for an online shop selling garden furniture in Germany, Austria and Switzerland, with half the year's revenue between March and June. The homepage once answered 200 while the checkout threw an error for six hours. Wants the checkout and the payment page checked, not only the homepage, an SMS or call to whoever is on duty that night, and a report that shows the agency what the downtime cost.
- **The Information Security Officer** (v1.0): Information security officer at a mid-sized logistics company that falls under NIS2 and is working towards ISO 27001. Needs every outage recorded with detection time, response and resolution, in a form an auditor accepts. Reads the subprocessor list before the feature page, because the on-call staff's mobile numbers and the status page subscribers are personal data, and wants single sign-on and an audit log before anyone gets a login.
- **The Skeptic** (v1.0): Has seen "30-second checks from 20 locations" that paged the whole team for a single probe's network glitch, a status page that went down with the product it reported on, and "unlimited SMS" with a fair-use clause on page nine. Asks how a failure is confirmed, how long the history is kept and whether it can be exported, where the monitor itself publishes its own outages — and what leaving would cost.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Access controls: yes · yes · yes [S11]
- Analytics hosting: EU · no · yes [S9]
- Anonymized retention: yes [S10]
- Breach notification:  [S11]
- Carbon: 100% hydraulic energy GO · A+ · 0.02 [S1]
- Data retention: yes [S10]
- Documents: Terms of service · Privacy policy · Sub-processors · Vulnerability disclosure · DPA [S1]
- DPA available: yes [S11]
- DPA precedence: yes [S11]
- Dpia: yes [S10]
- Encryption: AES-256 or equivalent · TLS 1.2+ [S11]
- GDPR: yes · yes [S1]
- GDPR: yes [S10]
- Incident AI feedback usage: yes [S18]
- Incident AI redaction: yes · yes [S18]
- Paddle billing excluded: billing · Paddle [S11]
- Records of processing: Art. 30 GDPR · yes [S10]
- Retention extension: Privacy Manager · 60 [S10]
- Roles: Phare · customer [S11]
- Scc: yes [S10]
- Sccs incorporated: yes [S11]
- Special category data: no [S11]
- Subprocessor notice: 30 [S11]
- Trackers: 0 · no [S1]

**Data**
- Backup schedule: multi-region in Europe · multi-AZ object storage · Scaleway · 3 · 3 [S9]
- Deletion backups: immediate · 21 [S9]
- Deletion request: yes [S11]
- Failing monitor pause: Hobby · 48 [S9]
- Hobby inactivity deletion: Hobby · 14 days before · 3 days before · 4 [S9]
- Inactive account deletion: 4 [S11]
- Uptime retention: until account deleted · one year [S9]

**Hosting**
- EU: European Union [S3]
- EU made hosted: EU · EU [S2]
- No ip allowlist: Bunny.net · no [S13]
- Provider: Scaleway, France · Hetzner, Germany · Bunny.net [S11]
- Providers: Slovenia · Germany · France · Netherlands [S1]
- Residency: yes [S1]
- Residency: European Union · yes [S4]

**Integrations**
- Alert channels telegram email: telegram · email [S2]
- API: yes [S8]
- API auth: Bearer Token [S20]
- API base URL: https://api.phare.io [S20]
- API documented: yes · yes [S2]
- API key access levels: No access · Read-only · Read-write [S20]
- API key limit: unlimited [S20]
- API key role requirement: Owner · Admin [S20]
- API key scopes: yes · yes [S20]
- API purpose: API enables programmatic interaction, integration and automation for most control panel tasks [S20]
- API rate limit: organization-wide, shared across all API keys · 100 [S20]
- App connections: yes [S7]
- Auth bearer token: bearer user token [S21]
- Auth bearer token: bearer_token [S22]
- Configuration tools: Terraform · Ansible · NixOS [S7]
- Custom rate limit: yes [S20]
- Incident notification threads: Email · Discord · Slack · yes [S18]
- List status pages API: list status pages endpoint with tag parameter [S17]
- Listed: Terraform · Ansible · NixOS [S19]
- Monitor report endpoint: per-monitor report endpoint exists [S21]
- Organization scoped key headers: X-Phare-Project-Id · X-Phare-Project-Slug · organization-scoped API key [S21]
- Project headers: X-Phare-Project-Id · X-Phare-Project-Slug [S20]
- Reports default window: now · 30 days ago [S21]
- Rss atom feeds: yes [S17]
- Slack feed: yes [S17]
- Sms alerts: yes [S2]
- Status updates slack: yes [S6]
- Surface: syncs with external tools [S1]
- Terraform managed resources: projects, monitors, status pages, alert rules [S19]
- Terraform open source: MIT · yes [S19]
- Terraform provider available: first-party · yes [S19]
- Uptime alerting examples: email · Slack · Discord [S15]
- Uptime ansible: yes [S15]
- Uptime nixos: yes [S15]
- Uptime reports API: all monitors of the project · GET https://api.phare.io/uptime/reports · 1 [S21]
- Uptime terraform: yes [S15]

**Legal**
- Breach notification 72h: 72 · Supervisory Authorities [S10]
- Breach third party 24h: 24 · controllers when processing on behalf of others [S10]
- Company history: no · yes · 2022-09 · phare.io/open [S1]
- DPA available: yes · yes · yes · yes [S2]
- DPA available: yes · yes · yes [S10]
- DPA available: yes [S12]
- Dsr email: support@phare.io [S10]
- Dsr response time: one month · up to two additional months [S10]
- Entity: Lightkeeper OÜ · Tallinn, Estonia [S10]
- Entity: Lightkeeper OÜ · Tallinn, Estonia [S9]
- Entity: Lightkeeper OÜ · Phare [S11]
- Governing law: Estonia [S9]
- Jurisdiction: Estonian law and the GDPR · courts of Tallinn, Estonia [S11]
- Policy updated: October 25, 2026 [S10]
- Privacy manager: Nicolas Beauvais · Privacy Manager [S10]
- Subprocessor page: yes [S2]

**Pricing**
- Billing cycle: yes · monthly [S9]
- Fee change notice: yes · yes [S9]
- Free no credit card: yes [S8]
- Free plan: free forever, all core features · Hobby · yes · yes · no · yes [S1]
- Free tier: yes · no [S2]
- Free tier: yes [S3]
- Free tier: yes · no [S5]
- Free tier: Every feature free to use, no credit card [S4]
- Free trial: yes · no [S6]
- Hobby price: Hobby · 0 [S8]
- Incident AI credits: yes · 1 · yes [S18]
- Merchant of record: Paddle · no [S9]
- Metered billing: yes · yes [S9]
- Overage buffer: 10 · yes [S8]
- Pay per use: pay_per_use_per_request · yes [S2]
- Private status page plan: Scale · yes [S6]
- Refund policy: 30 [S8]
- Refund window: 30 · yes [S9]
- Scale AI overage: EUR · 0.01 [S8]
- Scale monitoring event overage: EUR · 1.0E-5 [S8]
- Scale price: 5 · Scale · EUR [S8]
- Scale sms overage: EUR · 0.1 [S8]
- Sms plan requirement: Scale · yes [S16]
- Starting price: 5 · EUR [S8]

**Product**
- Access control: yes · Scale [S17]
- Access password: yes [S17]
- Access token: yes · 1 [S17]
- Affiliate cookie: _klb · affiliate attribution · yes · 60 [S10]
- AI incident features: yes · yes · yes [S2]
- Alert channels: Email, SMS, Slack, Discord, Telegram, Pushover, ilert, Ntfy.sh, custom Outgoing Webhook [S4]
- Alert delivery resilience: Aggressive retry policy; emails use three different SMTP providers [S4]
- Alert quotas: SMS · voice calls · yes [S4]
- Alert rate limiting: yes · yes [S2]
- Alert rate limiting: yes · yes [S5]
- Alert rate limiting: yes · at most once every 10 minutes [S15]
- Alert rate limits: Rate limits cap notifications per timeframe to prevent alert fatigue [S4]
- Alert retry policy: yes [S2]
- Alert retry policy: yes [S5]
- Alert routing: yes [S5]
- Alert rule scope: organization · project [S15]
- Alert rules: yes [S13]
- Alert rules elements: event · scope · rate_limit · integration [S15]
- Alert scoping: organization · project · yes [S4]
- Alerting: yes · yes · yes · yes [S3]
- Alerting: yes · yes [S6]
- Alerting channels: Telegram · email [S1]
- Alerting retry: yes [S6]
- Alerting sms: yes · yes [S1]
- Analytics: yes [S1]
- API: yes · yes [S1]
- API available: yes [S7]
- API endpoint areas: Platform · Alert Rules · Integrations · Projects · Users · Uptime · Monitors · Incidents · Maintenance Windows · Status Pages · Reports [S20]
- API http methods: GET · POST · PUT · PATCH · yes [S2]
- API incident retention: 1 year [S22]
- Auth: yes [S1]
- Auth 2FA: yes [S2]
- Auto incident creation: yes · yes [S18]
- Auto recovery: yes [S18]
- Automatic incident creation: yes · yes [S5]
- Availability history display: yes · yes · yes [S17]
- Availability history window: 30 · 60 · 90 [S17]
- Billing: unified billing [S1]
- Branded status pages: yes · yes [S5]
- Cancellation channels: dashboard · Paddle customer portal · email support@phare.io [S9]
- Certificate automatic discovery: yes [S14]
- Certificate details: issuer, validity period, domain coverage [S14]
- Certificate discovered alert rule: Monitor certificate discovered [S14]
- Certificate endpoints: yes · yes [S14]
- Certificate events: uptime.monitor_certificate.discovered · uptime.monitor_certificate.expiring [S15]
- Certificate expiration alert range: 60 · 1 · days [S14]
- Certificate expiring alert single reminder: Monitor certificate expiring · 1 [S14]
- Certificate inventory: yes [S14]
- Certificate multiple per monitor: yes [S14]
- Certificate status expired: certificate is in use and has expired [S14]
- Certificate status expiring: 30 [S14]
- Certificate status in use: 2 [S14]
- Certificate status retired: 2 [S14]

**Subprocessors**
- Affiliate klibon: Klibon · affiliate code · payment amounts · Paddle identifiers · affiliate commission payment [S10]
- Brevo: Brevo · France · Newsletter and onboarding delivery + failover transactional emails · European Union · ISO 27001:2013 [S12]
- Change notice: email · 30 · yes [S12]
- Infobip: Infobip · United Kingdom · SMS and voice notifications · Global · ISO 27001:2022 [S12]
- Klibon: Klibon · No name, email, or IP address ever shared · France · Affiliate program attribution and commissions · European Union [S12]
- Last updated: October 25, 2026 [S12]
- Lettermint: Lettermint · Netherlands · Failover transactional emails · European Union [S12]
- List URL: https://phare.io/legal/sub-processors [S11]
- Mistral AI: Mistral AI · Personal data removed from payload · France · AI-generated incident summary and post-mortem · European Union · ISO 27001:2022 + SOC 2 [S12]
- Paddle: Paddle · merchant of record / payments [S9]
- Scaleway: Scaleway · France · Encrypted backup storage and transactional emails · France · ISO 27001:2022 [S12]
- Security tooling: Aikido · dependency scanning and code auditing · no [S11]
- Sentry: Sentry · Configured to not process personal data · United States · Error tracking and performance monitoring · Germany · ISO 27001:2022 [S12]
- Vemetric: Vemetric · IP anonymized via Bunny proxy; usage aggregated at organization level · Austria · Product and website analytics · European Union [S12]

**Support**
- Ask support: yes [S6]
- Dashboard link: Support · Dashboard · API Reference · Changelog · Blog · Service status [S7]
- Feedback channels: email · Discord community [S9]
- Model: same-day for most questions · yes · yes [S1]

179 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/phare

## Questions

### 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](https://whats-best.ai/evidence/15479).

### What are the best alternatives to Phare Uptime?

As of 2 Nov 2026, the panel rates [Hyperping (3.5/5)](https://whats-best.ai/software/uptime-monitoring/hyperping), [Checkly (3.5/5)](https://whats-best.ai/software/uptime-monitoring/checkly) and [openstatus (3.5/5)](https://whats-best.ai/software/uptime-monitoring/openstatus) 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](https://whats-best.ai/software/uptime-monitoring/hyperping) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Phare Uptime alternatives](https://whats-best.ai/software/uptime-monitoring/phare/alternatives).

## What this page leaves out

- 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.
- 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.
- 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.
- 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.
- 4 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown.

## Sources

- [S1] Vendor homepage: https://phare.io/ (checked 2026-11-01)
- [S2] Features page (uptime): https://phare.io/products/uptime (checked 2026-11-01)
- [S3] Features page (website monitoring): https://phare.io/products/uptime/website-monitoring (checked 2026-11-01)
- [S4] Features page (alerting): https://phare.io/products/uptime/alerting (checked 2026-11-01)
- [S5] Features page (incident management): https://phare.io/products/uptime/incident-management (checked 2026-11-01)
- [S6] Features page (status pages): https://phare.io/products/uptime/status-pages (checked 2026-11-01)
- [S7] Documentation: https://docs.phare.io/introduction (checked 2026-11-01)
- [S8] Pricing page: https://phare.io/pricing (checked 2026-11-01)
- [S9] Terms of service (names the operating company): https://phare.io/legal/terms-of-service (checked 2026-11-01)
- [S10] Privacy policy: https://phare.io/legal/privacy-policy (checked 2026-11-01)
- [S11] Data processing agreement (dpa): https://phare.io/legal/data-processing-agreement (checked 2026-11-01)
- [S12] Subprocessor list: https://phare.io/legal/sub-processors (checked 2026-11-01)
- [S13] Checks, locations & failure confirmation — found from sitemap: https://docs.phare.io/uptime/monitors (checked 2026-11-01)
- [S14] Checks, locations & failure confirmation — found from sitemap: https://docs.phare.io/uptime/certificates (checked 2026-11-01)
- [S15] Alerting, escalation & on-call — found from sitemap: https://docs.phare.io/uptime/alerting (checked 2026-11-01)
- [S16] Alerting, escalation & on-call — found from sitemap: https://docs.phare.io/integrations/sms (checked 2026-11-01)
- [S17] Status pages & incident communication — found from sitemap: https://docs.phare.io/uptime/status-pages (checked 2026-11-01)
- [S18] Status pages & incident communication — found from sitemap: https://docs.phare.io/uptime/incidents (checked 2026-11-01)
- [S19] API, monitoring as code & team administration — found from sitemap: https://docs.phare.io/integrations/terraform (checked 2026-11-01)
- [S20] API, monitoring as code & team administration — found from sitemap: https://docs.phare.io/api-reference/introduction (checked 2026-11-01)
- [S21] Uptime reports, data & the vendor's own reliability — found from sitemap: https://docs.phare.io/api-reference/uptime/reports/get-a-report (checked 2026-11-01)
- [S22] Uptime reports, data & the vendor's own reliability — found from sitemap: https://docs.phare.io/api-reference/uptime/monitors/get-a-monitor-report (checked 2026-11-01)
- [S23] Code repository (open-source licence) — found from the homepage: https://github.com/phare (checked 2026-11-01)

---

Cite as: whats-best.ai, "Phare Uptime — Uptime Monitoring & Status Pages", AI panel analysis, as of 2026-11-06. https://whats-best.ai/software/uptime-monitoring/phare

Corrections: https://whats-best.ai/correct/1349?target=page