# Hyperping — Uptime Monitoring & Status Pages

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

- Vendor: Hyperping SAS (https://hyperping.com)
- 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/hyperping
- Alternatives: https://whats-best.ai/software/uptime-monitoring/hyperping/alternatives ([markdown](https://whats-best.ai/software/uptime-monitoring/hyperping/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: Hyperping SAS
- 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 [S4]

## The panel's verdict

Hyperping, the French uptime monitoring and status page service of Hyperping SAS in Paris, scored 7-8 on checks and locations, its strongest area: HTTP checks with keyword assertions, TCP, ping, DNS, SSL and domain-expiry checks, cron heartbeats and Playwright browser checks run from 18 regions as often as every 10 seconds, each failure confirmed from at least two other regions first. Status pages and sovereignty follow: pages are hosted on Vercel, separate from the Frankfurt platform, and the chain is documented down to a public subprocessor list naming US processors, while Hyperping itself holds no SOC 2 or ISO 27001. Reports and reliability is weakest at 5-6 — the lone 5, from the customer support lead, cites metric history of only 2 to 30 days by plan — and judges found no public information on a Hyperping status page, probe IP addresses or SLA credits. Alerting and on-call, automation and teams, and pricing transparency all sit at 7. No criterion split by more than one point.

**Speaks for it:**
- Every alert is double-checked from at least two other regions before it reaches your team, with the confirmation logic documented.
- Checks span HTTP with exact keyword assertions, TCP, ping, DNS, SSL and domain expiry, cron heartbeats and Playwright browser checks, from 18 regions at intervals down to 10 seconds.
- Status pages are hosted on Vercel, separately from the Frankfurt monitoring platform, so the page can outlive a platform outage.
- A public, versioned subprocessor list names each processor with its location, backed by a data processing agreement available to all customers.
- Monitors, status pages and maintenance windows are manageable through a documented REST API and an open-source Terraform provider with import support.

**Held against it:**
- Hyperping states it holds no independent SOC 2 or ISO 27001, with its infrastructure providers carrying those certifications.
- SMS arrives as plan credits of 20, 75 or 200, and judges found no public per-message or per-call price beyond the credits.
- The captured pages give different figures for the Business plan — €299 /month on one, $299 /month and $249 billed yearly on others.
- Judges found no public information on a Hyperping status page or incident history, probe IP addresses for allow-listing, or SLA credits.
- The alert, analytics and billing chain runs through named US providers including Twilio, SendGrid, Stripe, Sentry and Segment.

**Best for:**
- You run checkout flows or JavaScript-heavy pages and want browser checks with multi-region confirmation before anyone is paged.
- You manage a fleet of monitors or many client sites and want monitoring as code, with every change reviewed in a pull request.
- You are a European buyer who wants a French contracting entity, primary storage in Frankfurt and a public subprocessor list, and can accept named US providers in the alert path.
- You publish status pages for customers and want them hosted on infrastructure separate from the monitoring platform.

**Avoid if:**
- You require a vendor that holds its own SOC 2 or ISO 27001 certification — Hyperping states it holds none itself.
- You need per-component uptime percentages, response-time charts or 90-day history bars on status pages — the component documentation states components carry none.
- Your compliance regime cannot tolerate US subprocessors in the alert path — SMS and phone calls run through Twilio and email through SendGrid, both listed as US processors.
- You need EU-only probes and infrastructure as a published, self-serve edition — they are offered on request rather than as a documented plan.

## 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 | 4/5 | 3.5/5 | 4/5 | 4/5 | 4/5 | 3.5/5 |
| Alerting, escalation & on-call | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Status pages & incident communication | 3.5/5 | 4/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| API, monitoring as code & team administration | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| Uptime reports, data & the vendor's own reliability | 3/5 | 3/5 | 2.5/5 | 3/5 | 3/5 | 3/5 |
| European sovereignty | 3.5/5 | 3.5/5 | 4/5 | 4/5 | 3.5/5 | 4/5 |
| Pricing transparency | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 | 3.5/5 |
| **Weighted verdict** | **3.5/5** | **3.5/5** | **3.5/5** | **3.5/5** | **3.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**
- Audit costs: yes [S10]
- Audit frequency: 14 · 1 [S10]
- Audit reports: third-party certifications · audit reports · penetration test summaries [S10]
- Breach notification: 72 · yes [S11]
- Breach notification: 72 [S12]
- Breach notification: yes [S9]
- Breach notification: without undue delay [S10]
- CCPA: yes · no [S12]
- Cnil: CNIL [S9]
- Data subject request tools: yes [S10]
- Data subject requests: no [S10]
- Data subject rights: access · rectification · erasure · restriction · portability · objection [S11]
- DPA: yes [S8]
- DPA: all customers · yes [S12]
- DPA all plans: all customers · yes [S11]
- DPA changes: yes [S10]
- DPA GDPR: yes · yes · yes · yes [S4]
- DPA GDPR: yes · yes · yes · yes [S2]
- DPA GDPR: yes · yes [S14]
- DPA last updated: 2026-02-19 [S10]
- DPA laws covered: EU GDPR · UK GDPR · Swiss FADP · CCPA/CPRA [S10]
- DPA precedence: yes [S10]
- Encryption: LUKS, AES-256 · HTTPS/TLS 1.2+ [S10]
- Encryption at rest: LUKS + managed DB native encryption [S12]
- GDPR: yes [S1]
- GDPR: France · yes [S12]
- GDPR status: yes [S11]
- Independent certs: no · no [S12]

**Data**
- Backup retention: no · 7 [S10]
- Dashboard deletion: yes [S10]
- Deletion confirmation: yes [S10]
- Deletion SLA: 30 · 90 [S9]
- Deletion timelines: 90 · 30 [S12]
- Deletion window: 30 [S10]
- Export: yes · 30 [S8]
- Inactivity deletion: 24 [S8]
- Retention backups: daily · 7 · yes · no [S9]
- Retention billing: French accounting law · 10 [S9]
- Retention closed accounts: 90 · 30 [S9]
- Retention inactive accounts: 2 [S9]
- Retention uptime: 2 [S9]

**Hosting**
- Data region: Europe [S1]
- Locations: 18 [S1]
- Primary region: DIN ISO/IEC 27001 · Frankfurt, Germany [S11]
- Primary region: Frankfurt (FRA1), Germany · DigitalOcean [S12]
- Primary storage: EU (Frankfurt, Germany) · global [S10]
- Probe regions: 18+ · DigitalOcean · AWS · Scaleway [S12]
- Probes worldwide: EU · US · 18+ [S11]

**Integrations**
- Alert channels: Slack · PagerDuty · Opsgenie · Discord · Telegram · Email · SMS [S3]
- Alerts: Slack · Microsoft Teams · Google Chat · PagerDuty · Opsgenie · Jira Service Management · Discord · Telegram · mobile app · email · SMS · phone call · webhooks [S1]
- API: yes · yes · yes [S11]
- API: yes [S12]
- API access: yes [S8]
- API base URL: https://api.hyperping.io [S6]
- API key permissions: read_write · read_only [S6]
- API ssl settings: ssl_alert_days · ssl_reminders · ssl_notify_on_change · domain_alert_days · ssl_expiration · domain_expiration [S2]
- Auth bearer token: Bearer token in Authorization header [S6]
- Healthchecks API: yes · POST /v2/healthchecks [S3]
- Higher rate limits contact: higher rate limits available via contact [S6]
- Import atlassian instatus: Atlassian Statuspage · Instatus · yes · yes [S4]
- Mcp: Claude · Cursor · yes [S1]
- Mcp: MCP server giving Claude, Cursor and AI tools live outage context [S4]
- Mcp: yes [S3]
- Notification channels next steps: email · sms · phone_calls · slack · teams [S16]
- Pagerduty auto close: PagerDuty · Opsgenie [S3]
- Per key permissions: yes [S6]
- Rate limits: yes · 429 Too Many Requests [S6]
- Response format: JSON · yes [S6]
- Rest API: yes [S1]
- Rest API: REST API to open, update and resolve incidents from CI, deploy scripts or chat [S4]
- SSO security features: SSO · access roles [S10]
- Terraform: Develeap community provider · yes [S1]
- Terraform: hyperping_healthcheck · yes [S3]
- Terraform: yes [S12]
- Terraform API: yes · yes [S7]

**Legal**
- Address: Paris · 50 Avenue des Champs-Élysées · France · 75008 [S11]
- Address: hello@hyperping.io · 50 Avenue des Champs-Élysées, 75008 Paris, France [S10]
- Entity: Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France [S1]
- Entity: Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France [S2]
- Entity: Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France [S3]
- Entity: Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France · France [S8]
- Entity: Paris · Hyperping SAS · French/EU law [S11]
- Entity: Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France [S14]
- Entity: data controller · Hyperping SAS · 50 Avenue des Champs-Élysées, 75008 Paris, France · French law [S9]
- Entity: Hyperping SAS [S10]
- Governing law: France · Paris, France [S8]
- Governing law: courts of Paris, France · France [S10]
- Policy updated: 2026-02-19 [S9]
- Terms updated: 2026-02-19 [S8]

**Pricing**
- 500 jobs: 500 · 249 · 299 [S3]
- AI included: 10 · 3 [S1]
- Billing cycle: monthly · annual · yes [S8]
- Business: 10 · 20 · 299 · yes · unlimited · yes · yes · yes · 12 · yes [S4]
- Business includes: yes · 1000 · 10 · 20 · yes · 20 [S2]
- Business monthly: 299 · 3588 [S1]
- Business price: 299 · 2990 · 249 [S2]
- Comparison checked date: 2026-10-08 [S3]
- Currency: USD [S8]
- Essentials: 3 · 50 · 29 · 100 · 1 · yes · email · Slack · Teams · 30 · 7 [S4]
- Essentials seats: no · 3 [S3]
- Free: 1 · 20 · 0 · 1 · no · 5 · no [S4]
- Free included: yes · yes · no [S3]
- Free plan: 20 · yes · no · no [S11]
- Free plan: 20 · yes · no · no [S14]
- Free plan monitors: 20 · no [S2]
- Free tier: 20 · no [S1]
- Grace period min: 1 · 10 [S3]
- Keyword monitoring included all plans: yes · yes [S13]
- Logs alpha free: yes [S7]
- Logs plans: 20 · 50 · 5 [S7]
- Paid start: monthly · 29 [S1]
- Payment processor: Stripe [S8]
- Plan monitor counts: 250 · 20 · 1000 · 50 [S3]
- Plans: Free · Essentials · Pro · Business · Enterprise [S8]
- Price change notice: 30 [S8]
- Pro: 3 · 10 · 250 · 89 · 1000 · yes · 30 · yes · 9 · yes [S4]

**Product**
- Access MFA: yes [S12]
- Additional server agent price: 2 · 1.5 · 2 [S7]
- AI access: /hp ask [S1]
- AI availability limits: alpha · no [S1]
- AI byok: OpenAI · Anthropic · Gemini · OpenRouter · yes [S1]
- AI incident investigation: yes [S1]
- AI included: 10 · yes · 3 [S7]
- AI not on free or EU only: no · no [S7]
- Alert channels: Slack · Teams · SMS · phone call [S1]
- Alert channels: email, SMS, phone calls, Slack, Microsoft Teams, Discord, Telegram, Google Chat, PagerDuty, OpsGenie, Jira, webhooks [S8]
- Alert once per missed run: yes [S3]
- API healthchecks: Cron job and heartbeat monitoring [S6]
- API incidents: Create and manage status page incidents [S6]
- API maintenance: Schedule maintenance windows [S6]
- API monitor groups: Organise monitors into named groups [S6]
- API monitors: Create, update, and manage uptime monitors [S6]
- API outages: Track and manage detected outages [S6]
- API reports: Access uptime and performance reports [S6]
- API SSO connections: OpenID Connect sign-in for private status pages [S6]
- API status pages: Manage status pages and subscribers [S6]
- Auto incident reporting: yes · yes · yes [S4]
- Backup retention: 7 [S12]
- Backups daily: yes [S12]
- Browser checks: browser_checks_e2e · Playwright [S1]
- Browser checks: E2E browser checks · Playwright [S2]
- Browser checks: yes [S8]
- Browser checks alternative: Playwright scripts for content that only renders with JavaScript · yes [S13]

**Subprocessors**
- Analytics: Segment · Sentry [S9]
- Aws: monitoring infrastructure, S3, distributed monitoring · AWS [S9]
- Aws: Amazon Web Services, Inc. · monitoring infrastructure, S3 storage, compute · Global (primary EU and US) [S10]
- Change notice days: 14 · 7 [S10]
- Cloudflare: Cloudflare, Inc. · CDN, DDoS protection, SSL/TLS management · Global [S10]
- Communications: SendGrid (Twilio) · Twilio [S9]
- Digitalocean: DigitalOcean, LLC · primary cloud hosting, databases, object storage · EU (Frankfurt, Germany) [S10]
- Google: Google LLC · single sign-on (OAuth) authentication · United States [S10]
- Hosting: Frankfurt, Germany (EU) · DigitalOcean [S9]
- List URL: hyperping.com/subprocessors [S9]
- List URL: hyperping.com/subprocessors [S10]
- Objection remedy: terminate affected services [S10]
- Scaleway: EU · Scaleway [S9]
- Scaleway: Scaleway SAS · EU-based monitoring infrastructure · EU (Paris/Amsterdam) [S10]
- Segment: Segment (Twilio Segment) · product analytics and event tracking · United States [S10]
- Sendgrid: Twilio SendGrid · email delivery for alerts and notifications · United States [S10]
- Sentry: Sentry (Functional Software, Inc.) · error tracking and performance monitoring · United States [S10]
- SSO: Business · Enterprise · WorkOS · SAML · Okta · Azure AD [S9]
- Stripe: Stripe, Inc. · payment processing and subscription billing · United States (PCI-DSS Level 1) [S10]
- Stripe pcidss: Stripe · payment processing · PCI-DSS Level 1 [S9]
- Twilio: Twilio, Inc. · SMS and phone call alert delivery · United States [S10]
- Vercel: Vercel, Inc. · status page hosting and marketing website · Global (primary US and EU) [S10]
- Vercel cloudflare: Vercel: status pages and marketing site · Cloudflare: CDN, DDoS, SSL/TLS [S9]
- Workos: WorkOS, Inc. · enterprise SSO (SAML, Okta, Azure AD) · United States [S10]

**Support**
- Keyword logs: inspect the actual response received on failed keyword checks · yes [S13]
- Priority support: yes [S1]
- Privacy contact: hello@hyperping.io · yes [S9]
- Rights response days: 30 [S9]
- SLA exclusions: yes · yes [S8]
- SLA uptime: 99.9 · yes [S8]
- Vulnerability disclosure: hello@hyperping.io · 48 [S12]

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

## Questions

### Is Hyperping European?

Yes. whats-best.ai classifies Hyperping as EU-Made.

### Where does Hyperping store data?

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

### Does Hyperping have a free plan?

Yes. Hyperping has a free plan, per [the vendor’s page captured 1 Nov 2026](https://whats-best.ai/evidence/15426).

### What are the best alternatives to Hyperping?

As of 2 Nov 2026, the panel rates [Checkly (3.5/5)](https://whats-best.ai/software/uptime-monitoring/checkly), [openstatus (3.5/5)](https://whats-best.ai/software/uptime-monitoring/openstatus) and [Oh Dear (3.5/5)](https://whats-best.ai/software/uptime-monitoring/oh-dear) 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 [openstatus](https://whats-best.ai/software/uptime-monitoring/openstatus) (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: [Hyperping alternatives](https://whats-best.ai/software/uptime-monitoring/hyperping/alternatives).

## What this page leaves out

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

## Sources

- [S1] Vendor homepage: https://hyperping.com/ (checked 2026-11-01)
- [S2] Features page (SSL monitoring): https://hyperping.com/ssl-monitoring (checked 2026-11-01)
- [S3] Features page (cron job monitoring): https://hyperping.com/cron-job-monitoring (checked 2026-11-01)
- [S4] Features page (status pages): https://hyperping.com/status-page (checked 2026-11-01)
- [S5] Features page (on-call): https://hyperping.com/on-call (checked 2026-11-01)
- [S6] API documentation: https://hyperping.com/docs/api/overview (checked 2026-11-01)
- [S7] Pricing page: https://hyperping.com/pricing (checked 2026-11-01)
- [S8] Terms of service: https://hyperping.com/terms (checked 2026-11-01)
- [S9] Privacy policy: https://hyperping.com/privacy (checked 2026-11-01)
- [S10] Data processing agreement (dpa): https://hyperping.com/dpa (checked 2026-11-01)
- [S11] GDPR and EU data page: https://hyperping.com/gdpr (checked 2026-11-01)
- [S12] Security / trust page: https://hyperping.com/security (checked 2026-11-01)
- [S13] Checks, locations & failure confirmation — found from sitemap: https://hyperping.com/docs/monitoring/keyword-monitoring (checked 2026-11-01)
- [S14] Checks, locations & failure confirmation — found from sitemap: https://hyperping.com/guide/uptime-monitoring/check-intervals-and-thresholds (checked 2026-11-01)
- [S15] Alerting, escalation & on-call — found from sitemap: https://hyperping.com/docs/monitoring/escalation-policies (checked 2026-11-01)
- [S16] Alerting, escalation & on-call — found from sitemap: https://hyperping.com/docs/monitoring/on-call (checked 2026-11-01)
- [S17] Status pages & incident communication — found from sitemap: https://hyperping.com/docs/status-page/components (checked 2026-11-01)
- [S18] Status pages & incident communication — found from sitemap: https://hyperping.com/docs/status-page/private-status-pages (checked 2026-11-01)
- [S19] API, monitoring as code & team administration — found from sitemap: https://hyperping.com/docs/api/monitors (checked 2026-11-01)
- [S20] API, monitoring as code & team administration — found from sitemap: https://hyperping.com/docs/projects/audit-logs (checked 2026-11-01)
- [S21] Uptime reports, data & the vendor's own reliability — found from sitemap: https://hyperping.com/docs/monitoring/reports (checked 2026-11-01)
- [S22] Uptime reports, data & the vendor's own reliability — found from sitemap: https://hyperping.com/docs/api/reports (checked 2026-11-01)

---

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

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