# Vendor facets — Hyperping. Uptime monitoring with hosted status pages; on the Kin Score it touches one
# pointer check, status_page_present (6 pts), and earns it in full: *.hyperping.app pages 404 unknown paths,
# so even a free-plan hosted page clears the pointer-liveness probe. Its MCP server and status.json score nothing.
vendor: hyperping
name: Hyperping
website: https://hyperping.com
areas:
- status-page
registry_keys:
- hyperping
rubric_schema_version: 0.22.0
generated: '2026-09-25'
features_refreshed: '2026-09-25'
basis: capability
summary: >-
  Hyperping moves one Kin Score check, status_page_present (6 of 38 operational-transparency points),
  once the provider declares the page as a StatusPage in apis.yml. Unlike several rivals it earns the
  check even on the free plan's hosted subdomain: *.hyperping.app returns a real 404 for nonsense paths,
  so the pointer grades live. Its status.json endpoint, subscriber feeds and MCP server are useful but
  score nothing for the provider.
features:
- id: hosted-status-page
  name: Hosted status page (hyperping subdomain free, custom domain on paid plans)
  description: >-
    Public status pages with component grouping, incidents and scheduled maintenance; free plan on a Hyperping-hosted
    subdomain, custom domains with managed HTTPS on paid plans; private pages on Pro+.
  source: https://hyperping.com/status-page
  tier: all
- id: soft-404-safe-hosting
  name: Real 404 for unknown paths (measured)
  description: >-
    Probed 2026-09-25: plans.hyperping.app and status.hyperping.app return 200 for the page and 404 for
    a nonsense path.
  source: https://plans.hyperping.app
  tier: all
- id: subscribers
  name: Subscribers via email, Slack, Teams, RSS/Atom; SMS via Twilio
  description: Subscribers can follow specific services; channels on paid plans.
  source: https://hyperping.com/status-page
  tier: paid
- id: status-json
  name: Public status.json
  description: Appending /status.json returns the page indicator and 90-day average uptime.
  source: https://hyperping.com/docs/status-page/status-page-json
  tier: all
- id: hyperping-mcp
  name: Hyperping MCP server
  description: MCP server for AI tools to work with the provider's Hyperping monitors and incidents.
  source: https://hyperping.com/status-page
  tier: unknown
maps:
- feature: hosted-status-page
  check: status_page_present
  layer: composite
  credit: 1.0
  provider_must: >-
    Declare the page in apis.yml as common[].type StatusPage; the pointer is liveness-graded and grades
    live.
  note: Binary check, cleared in full on any plan. The only check the status-page area touches.
  catalog_pass_rate: 0.125
  facet: operational_transparency
  points: 6
  baseline_pass_rate: 0.376
earns_nothing:
- feature: hyperping-mcp
  check: mcp_server
  why: >-
    It serves the provider's team their Hyperping monitoring data; the dimension reads an MCP server for
    the provider's own API, described in its mcp/ manifest.
out_of_reach:
  checks:
  - change_log_present
  - deprecation_policy
  - roadmap_present
  - rate_limits_documented
  - webhooks_advertised
  note: A status page publishes nothing about the API's changes, limits, deprecations or own webhooks.
unscored_practice:
- feature: status-json
  why: Machine-readable status and uptime an agent could poll; no check reads it.
- feature: subscribers
  why: RSS/Atom status feeds; unscored.
surface:
  operational_transparency:
    reachable: 6.0
    total: 38
  agent_readiness:
    reachable: 0
    total: 139
hard_rule: >-
  A model, not a score. Adopting this vendor changes a provider's Kin Score only when the provider publishes
  the resulting artifacts on its own surface; nothing here writes a score, and no sponsorship or partnership
  can.
method: searched
source:
- https://hyperping.com/docs/status-page/status-page-json
- https://hyperping.com/status-page
- https://plans.hyperping.app
measured:
  cohort:
    method: vendors-catalog.json detections (CNAME / header / URL shape / markup), never a name match
    detected: 0
    in_baseline: 0
  control:
    basis: providers earning contract_present + documentation_present + api_reference_present, minus the
      cohort
    n: 5216
  metric: >-
    cohort_pct / control_pct = mean share of the check's points earned (derived and platform credit weighted),
    x100
  measured_on: '2026-09-25'
  status: 'not measurable: 0 detected customers clear the baseline (need 20)'
simulation:
  simulated_on: '2026-09-25'
  rubric: 0.23.0
  population: providers publishing a contract (contract_present earned), replayable exactly
  providers: 8977
  providers_unreplayable: 987
  providers_moved: 6390
  conditional_rows: excluded (they depend on what the API already does)
  composite_lift:
    median: 2.0
    p75: 2.1
    p90: 2.1
    max: 2.1
    mean_among_movers: 1.9
  agent_readiness_lift:
    median: 0.0
    p75: 0.0
    p90: 0.0
    max: 0.0
    mean_among_movers: 0.0
  facet_lift_median_among_movers:
    operational_transparency: 15.8
  composite_band_moves:
    thin -> developing: 598
    developing -> strong: 172
    emerging -> thin: 158
    strong -> exemplar: 43
    minimal -> emerging: 1
  agent_readiness_band_moves: {}
  method: >-
    each provider's own kin/checks file, the vendor's maps at their stated credit, the scorer's composite
    formula; from -> to, nothing written