# updown.io — Uptime Monitoring & Status Pages

updown.io by Adrien Rey-Jarthon (EI) 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: Adrien Rey-Jarthon (EI) (https://updown.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/updown-io
- Alternatives: https://whats-best.ai/software/uptime-monitoring/updown-io/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/updown-io/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: Adrien Rey-Jarthon (EI)
- 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: Not stated on the vendor’s pages as of 1 Nov 2026

## The panel's verdict

updown.io is a bootstrapped uptime monitoring and status page service from Adrien Rey-Jarthon (EI), a French sole proprietorship since 2012. Strongest are pricing transparency, from 7 to 9, and checks and locations, from 6 to 7: 1 credit = 1 check, credit packs from 5 € for 200,000 credits to 500 € for 60,000,000 credits, first 100,000 credits free, and a downtime confirmed after three down checks from at least two of ten locations. That spread reflects the status-page price, on which we found no public information. Sovereignty sits at 7 on an Article 28 data processing agreement in force for every account and a subprocessor list naming locations and safeguards, with US providers in the chain under SCCs or the EU-US Data Privacy Framework; no ISO 27001 or SOC 2 certification is documented. Weakest is automation and teams at a flat 4: accounts are single-user, team accounts in progress. Alerting and on-call and status pages, from 5 to 6, trail: escalation is an open feature request, and we found no public information on incident updates or subscriber notifications.

**Speaks for it:**
- A downtime is confirmed only after three down checks from at least two of ten named locations, with recovery requiring the same two-location logic.
- Pricing is computable from the public pages: 1 credit = 1 check, credit packs from 5 € for 200,000 credits to 500 € for 60,000,000 credits, SMS at 7500 credits (≈ 0.10€) per message, excluding VAT, no commitment, and the first 100,000 credits free.
- An Article 28 data processing agreement is already in force for every account, with deletion or return at your choice, audit rights and 30 days' notice of subprocessor changes.
- A documented REST API covers checks, downtimes, metrics, recipients, status pages and nodes, with a read-only key and client libraries in ten languages.
- Every check keeps a ten-year performance chart and monthly and yearly uptime numbers, with weekly reports to multiple email addresses and probe IPs published for allow-listing.

**Held against it:**
- Notification acknowledgement and escalation exist only as an open feature request, and we found no public information on phone-call alerts or on-call schedules.
- Accounts are single-user today, with the captured pages giving different signals on shared access — team accounts marked in progress, while the operator writes that permissions, audit logs and SSO are not planned in the near future.
- We found no public information on incident updates, scheduled maintenance announcements or how status page subscribers are notified.
- DNS record checks sit under review as a feature request, and we found no public information on browser or multi-step transaction checks or private in-network locations.
- The terms give no warranty on the correctness of collected data, and monthly and yearly reports remain under review, with reporting today limited to the last 24 hours and 7 days.

**Best for:**
- You want to compute the exact monitoring cost before committing — the credit model, every pack price and the SMS rate are published, with the first 100,000 credits free.
- You need false-positive-resistant downtime alerting — a downtime is confirmed by three down checks from at least two of ten locations before you are notified.
- You need a documented GDPR chain — a French sole proprietorship under French law, an Article 28 data processing agreement in force for every account, and a subprocessor list with locations and safeguards.
- You report uptime history to clients or in contract renewals — each check carries a ten-year performance chart and monthly and yearly uptime numbers.

**Avoid if:**
- You rely on alert acknowledgement and escalation for on-call coverage — both exist only as an open feature request on the vendor's pages.
- Your team needs multiple users, roles or SSO today — accounts are single-user, team accounts are in progress, and the operator writes that permissions, audit logs and SSO are not planned in the near future.
- You need multi-step or browser-flow checks of a checkout or login journey — the documented check types are HTTP(S), TCP, ICMP and pulse.
- You must treat uptime data as warranted evidence — the terms give no warranty on the correctness of collected data.

## 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 | 3.5/5 | 3.5/5 |
| Alerting, escalation & on-call | 3/5 | 2.5/5 | 3/5 | 2.5/5 | 3/5 | 2.5/5 |
| Status pages & incident communication | 3/5 | 3/5 | 3/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| API, monitoring as code & team administration | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Pricing transparency | 4/5 | 4.5/5 | 4/5 | 4/5 | 3.5/5 | 3.5/5 |
| **Weighted verdict** | **3/5** | **3/5** | **3/5** | **3/5** | **3/5** | **3/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**
- Based on: Automattic (WordPress) Creative Commons policy [S8]
- DPA: DPA document published [S3]
- DPA: yes · yes · no [S7]
- DPA audit: once per 12 months on written request [S9]
- DPA audit independent: each party bears its own · 30 · yes [S9]
- DPA available: yes [S19]
- DPA breach notification: yes [S9]
- DPA customer obligations: yes [S9]
- DPA delete or return: yes [S9]
- DPA dsar assistance: yes [S9]
- DPA encryption in transit: yes [S9]
- DPA excludes controller data: yes [S9]
- DPA GDPR article28: 28 [S9]
- DPA in force: yes [S9]
- DPA inactive data purge: 3 [S9]
- DPA instant deletion: yes · 7 [S9]
- DPA international transfers: SCCs 2021/914 · EU-US Data Privacy Framework · other lawful basis [S9]
- DPA liability: liability subject to Agreement's limitations [S9]
- DPA log retention: 1 month [S9]
- DPA negotiation: negotiation not offered; signed PDF copy available on request via support@updown.io [S9]
- DPA precedence: SCCs · DPA · rest of Agreement [S9]
- DPA processing details: availability/performance monitoring, downtime diagnosis, alerts, reports, status pages [S9]
- DPA retention duration: for as long as your account is active [S9]
- DPA return format: commonly used electronic format · yes [S9]
- DPA roles: updown.io · customer [S9]
- DPA scc module: 3 [S9]
- DPA scope of law: GDPR · UK GDPR · Swiss FADP [S9]
- DPA security measures: yes [S9]
- DPA special categories: no [S9]
- Processor role: processor · Article 28 [S8]
- South africa transfer: Article 49(1)(b) · South Africa · LNX Solutions · POPIA [S8]
- Supervisory authority: France · CNIL [S8]
- Transfer mechanisms: Standard Contractual Clauses (Implementing Decision (EU) 2021/914) · EU-US Data Privacy Framework · Chapter V [S8]

**Data**
- Account deletion: instant from service database · gone after up to one week [S8]
- Cookie purpose: identify · authenticate [S8]
- Deletion: anonymous authentication id · yes [S7]
- Inactivity purge: 3 [S8]
- Log retention: one month [S8]
- Metrics compaction: per hour initially, by day after 3 days, by months after 2 months · 3 [S8]
- No marketing emails: no [S8]
- Payment data handling: no [S8]

**Hosting**
- Company origin: 2012 · Paris, France [S5]
- Ip whitelist dns: ips.updown.io [S6]
- Monitoring node count: 10 [S6]
- Node locations: Los Angeles US · Miami US · Toronto Canada · Roubaix France · Frankfurt Germany · Cape Town South Africa · Helsinki Finland · Singapore · Tokyo Japan · Sydney Australia [S6]
- Pulse endpoint dns: 2025-02-25 · pulse.updown.io · 178.63.21.176 · 91.121.222.175 · 2001:41d0:2:85af::1 · 2a01:4f8:141:441a::2 [S4]

**Integrations**
- API: yes · yes [S7]
- API: Site footer links to an API [S16]
- API auth: url query param ?api-key= · HTTP header X-API-KEY [S5]
- API available: yes [S11]
- API docs: API documentation available [S3]
- API endpoints: /api/checks · /api/checks/:token · /api/checks/:token/downtimes · /api/checks/:token/metrics · /api/recipients · /api/status_pages · /api/nodes [S5]
- API throttling: yes [S7]
- API webhooks: REST · yes [S1]
- Client libraries: Ruby · Python · Node.js · Go · PHP · Elixir · Rust · Raku · Java · .NET [S5]
- Dns API: yes · ips.updown.io [S5]
- Downtimes paging: 100 [S5]
- Gzip: yes [S5]
- Ip format: json · txt [S5]
- Multiple API keys available: open feature request · no [S17]
- Multiple API keys requester: 2025-09-17 · Cyrille Derche [S17]
- Nodes API: /nodes [S6]
- Nodes API: yes [S5]
- Open source: github.com/jarthod · yes [S7]
- Pulse API creation: yes · type=pulse [S4]
- Pulse endpoint security: yes [S4]
- Pulse third party client: yes [S4]
- Readonly API key: yes [S5]
- Readonly get only: GET endpoints only [S5]
- Recipient channels: email · sms · slack · telegram · webhook · zapier [S5]
- Recipient types API: slack · telegram · zapier · statuspage · email · sms · webhook · slack_compatible · msteams [S5]
- Rest API: REST · https JSON · yes [S5]
- Slack: Documentation page for Slack integration [S3]
- Webhook events: check.down · check.up · check.ssl_invalid · check.ssl_valid · check.ssl_expiration · check.ssl_renewed · check.domain_expiration · check.performance_drop [S5]
- Webhook removal: 1000 [S5]
- Webhook retry: 25 [S5]
- Webhooks: yes [S5]
- Zapier: Documentation page for Zapier integration [S3]

**Legal**
- Company location: Paris, France [S6]
- Company location: 2012 · Paris, France [S9]
- Company origin: Product made in Paris, France since 2012 [S2]
- Company origin: 2012 · Paris, France [S11]
- Company origin: 2012 · Paris, France [S16]
- Company origin: 2012 · Paris, France [S18]
- Company origin: 2012 · Paris, France [S19]
- DPA available: yes [S11]
- DPA changelog: Sept 7th, 2026 [S9]
- DPA governing law: France [S9]
- DPA in force: yes · no [S8]
- Entity: Adrien Rey-Jarthon (EI) · 383 route de Choudans, 01630 St-Jean-de-Gonville, France [S7]
- Footer documents: Footer links to Terms of Service, Privacy Policy, DPA [S2]
- Governing law: France [S7]
- Made in: Paris · 2012 · France [S10]
- Made in: 2012 · Paris, France [S15]
- Made in paris: 2012 · Paris, France [S4]
- Origin: Made in Paris, France since 2012 [S3]
- Origin: Paris · 2012 · France [S13]
- Origin: Paris · 2012 · France [S8]
- Since: 2012 · Paris, France [S7]

**Pricing**
- Auto charge: no [S7]
- Billing model: pay-as-you-go · no · no [S7]
- Credit model: credit-based pay as you go · 1 [S1]
- Example range: 10 · 5.49 · 1.83 · 2 [S1]
- Free trial: yes · 100000 [S7]
- No commitment: no [S1]
- Pack 10m: 100 · 10000000 [S1]
- Pack 1 5m: 25 · 1500000 [S1]
- Pack 200k: 5 · 200000 [S1]
- Pack 3m: 40 · 3000000 [S1]
- Pack 500k: 10 · 500000 [S1]
- Pack 60m: 500 · 60000000 [S1]
- Payment methods: credit cards · Paypal · SEPA · cryptocurrencies [S1]
- Pulse credit cost: 1 · 1 [S4]
- Pulse daily example: 0.009 · 365 [S4]
- Pulse deleted check cost: 404 · yes [S4]
- Pulse disabled check cost: yes [S4]
- Pulse minute example: 1.1 [S4]
- Refunds: email support@updown.io · yes [S7]
- Sms alert cost: per message · 0.1 · 7500 [S1]
- VAT excluded: no [S1]

**Product**
- Affiliate program: Affiliate Program request is marked COMPLETED [S2]
- Alert channels: Slack · Teams · Telegram · Email · SMS · Zapier · custom webhooks [S6]
- Alerting sms: SMS alerts documented [S3]
- Apdex thresholds: 0.125 · 0.25 · 0.5 · 1 · 2 · 4 · 8 [S5]
- API key revocation: Allow API key revocation request is marked COMPLETED [S2]
- Check contains field: The check portal has a 'contains' field to check for required data [S11]
- Check frequency: 3600 · 15 [S1]
- Check intervals: 15 · 30 · 60 · 120 · 300 · 600 · 1800 · 3600 · 15 sec to 1 month [S5]
- Check types: Five check types including HTTP(S), TCP(S), ICMP [S1]
- Check types: https · http · icmp · pulse · tcp · tcps [S5]
- Cron monitoring: yes [S1]
- Cron monitoring: Pulse/cron monitoring supported [S3]
- Cron monitoring: Periodic task (cron) monitoring request is marked COMPLETED [S2]
- Cron monitoring: yes [S6]
- Custom domain ssl: Custom domain page with SSL request is marked COMPLETED [S2]
- Custom domain status page: Status page on own domain request is marked COMPLETED [S2]
- Custom domain status page: CNAME to own subdomain · yes [S14]
- Custom headers: yes [S5]
- Dns check planned: no [S11]
- Dns record checks status: DNS record checks is a feature request with status UNDER REVIEW, not an implemented feature [S11]
- Dns via tcp http checks: TCP/HTTP checks rely on DNS to reach the monitored target [S11]
- Domain expiration alert: yes · 14 · 7 · 1 [S5]
- Domain expiration alerts: yes [S1]
- Domain expiration check: Check domain expiration request is marked COMPLETED [S2]
- Domain expiry warning: Warn about expiring domain names request is marked COMPLETED [S2]
- Double check: yes · 2 [S1]
- Downtime confirmation checks: 2 · yes · 3 [S12]
- Downtime notification guarantee: interval * 1.5 [S12]
- Dual stack: yes [S1]
- Escalation status: open feature request · notification acknowledgement and escalation · 15 min, or parametrable [S13]
- Founded year: 2012 · 1 · yes [S6]
- History chart: 10 · status page · yes [S18]
- History duration: Longer History request is marked COMPLETED [S2]
- Http verb options: GET/HEAD · POST · PUT · PATCH · DELETE · OPTIONS [S5]
- Ip change notification: yes [S6]
- Latency export: Export detailed history of check latency request is marked COMPLETED [S2]
- Latency export request: Export detailed history of check latency [S19]
- Liability cap: amount paid by user [S7]
- Localization: Localized public status page request is marked COMPLETED [S2]
- Metrics API: GET /api/checks/:token/metrics · yes [S19]

**Subprocessors**
- Hosting: hosting the website, storing data and monitoring requests · OVH · France, EU · Hetzner · Germany, EU · DigitalOcean · US · DPF & SCCs [S8]
- List location: sub-processor list maintained in Privacy Policy [S9]
- Monitoring: monitoring requests only (no data stored) · Vultr · US · SCCs · Akamai Cloud · US · DPF & SCCs · LNX Solutions · South Africa · POPIA [S8]
- Notice period: 30 · terminate affected part with pro-rata refund of unused prepaid credits [S9]
- Payments: payments · Stripe · Ireland, EU · Paypal · Luxembourg, EU · CoinGate · Lithuania, EU [S8]
- Sms: sending SMS notifications · Vonage · US · DPF & SCCs · SMSalert.mobi · Romania, EU · Twilio · US · DPF & SCCs [S8]

**Support**
- Docs faq: Footer links to Documentation & FAQ, Support, System Status, Twitter, API [S2]
- Documentation faq: yes [S11]
- Status page: Public system status page linked [S3]
- Status page: yes [S19]
- Twitter: twitter · yes [S3]

65 more facts on the canonical page: https://whats-best.ai/software/uptime-monitoring/updown-io

## Questions

### Is updown.io European?

Yes. whats-best.ai classifies updown.io as EU-Made.

### Where does updown.io store data?

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

### Does updown.io have a free plan?

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

### What are the best alternatives to updown.io?

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: [updown.io alternatives](https://whats-best.ai/software/uptime-monitoring/updown-io/alternatives).

## What this page leaves out

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

## Sources

- [S1] Vendor homepage (with pricing): https://updown.io/ (checked 2026-11-01)
- [S2] Features page: https://updown.io/features (checked 2026-11-01)
- [S3] Documentation: https://updown.io/doc (checked 2026-11-01)
- [S4] Documentation (cron monitoring): https://updown.io/doc/how-pulse-cron-monitoring-works (checked 2026-11-01)
- [S5] API documentation: https://updown.io/api (checked 2026-11-01)
- [S6] About page (monitoring nodes): https://updown.io/about (checked 2026-11-01)
- [S7] Terms of service (names the operator): https://updown.io/tos (checked 2026-11-01)
- [S8] Privacy policy (with subprocessors): https://updown.io/privacy_policy (checked 2026-11-01)
- [S9] Data processing agreement (dpa): https://updown.io/dpa (checked 2026-11-01)
- [S10] Checks, locations & failure confirmation — found from sitemap: https://updown.io/features/select-ping-locations (checked 2026-11-01)
- [S11] Checks, locations & failure confirmation — found from sitemap: https://updown.io/features/dns-record-checks (checked 2026-11-01)
- [S12] Alerting, escalation & on-call — found from sitemap: https://updown.io/doc/how-alerting-works (checked 2026-11-01)
- [S13] Alerting, escalation & on-call — found from sitemap: https://updown.io/features/add-notification-escalation (checked 2026-11-01)
- [S14] Status pages & incident communication — found from sitemap: https://updown.io/features/status-page-on-own-domain (checked 2026-11-01)
- [S15] Status pages & incident communication — found from sitemap: https://updown.io/features/let-customers-subscribe-to-status-page (checked 2026-11-01)
- [S16] API, monitoring as code & team administration — found from sitemap: https://updown.io/features/team-accounts (checked 2026-11-01)
- [S17] API, monitoring as code & team administration — found from sitemap: https://updown.io/features/multiple-api-keys (checked 2026-11-01)
- [S18] Uptime reports, data & the vendor's own reliability — found from sitemap: https://updown.io/features/monthly-yearly-reports (checked 2026-11-01)
- [S19] Uptime reports, data & the vendor's own reliability — found from sitemap: https://updown.io/features/export-detailed-history-of-check-latency (checked 2026-11-01)

---

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

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