API reference

Human-readable error message.

Slug-style identifier from the registry.

Human-readable service name.

Provider region for regional services. Omitted for global services (CDNs, DNS resolvers, payment APIs).

Brand or parent company behind the service. Editorial rather than derived from id or name: every aws-* service reports "Amazon Web Services" whatever the product is called, and linode reports "Akamai / Linode" for the parent company. Omitted when the registry row carries no provider.

Whether the service appears on public ranking surfaces. true, the default, lists it on the leaderboard and the services index. false keeps it probed and queryable through /v1/services/{id} and /v1/services/{id}/uptime but off those rankings, which is how a newly onboarded service is held back until it has enough history to rank fairly.

Always present, never omitted: an absent field would read as "the API does not know" rather than "hidden".

Public landing page for the service. Always present.

The provider's own status page, where it publishes one. Omitted rather than empty when it does not, so a client never has to special-case "".

Carried on the list endpoint as well as the detail one, so rendering a directory of services needs a single request.

Number of active checks measuring this service. Checks registered but not yet active are excluded, so the count matches what the fleet is really executing. 0 for a newly registered service whose checks have not landed yet.

Availability percent over the rolling trailing 24 hours, computed from the per-minute consensus aggregate, with unknown minutes excluded from the denominator.

Measured directly rather than derived from the per-day rollup, whose buckets are anchored to UTC midnight: averaging a partial today against yesterday would bias against a service that was unhealthy hours ago. null when the window has no measurements yet.

Availability percent over the trailing 7 days, derived from the per-day rollup (same source as availability_30d / availability_90d). null when the window has no measurements yet.

Availability percent over the trailing 30 days, derived from the per-day rollup (excludes unknown minutes from the denominator). null when the window has no measurements yet.

Same as availability_30d, over 90 days.

Slug-style identifier from the registry.

Human-readable service name.

Provider region for regional services. Omitted for global services (CDNs, DNS resolvers, payment APIs).

Brand or parent company behind the service. Editorial rather than derived from id or name: every aws-* service reports "Amazon Web Services" whatever the product is called, and linode reports "Akamai / Linode" for the parent company. Omitted when the registry row carries no provider.

Whether the service appears on public ranking surfaces. true, the default, lists it on the leaderboard and the services index. false keeps it probed and queryable through /v1/services/{id} and /v1/services/{id}/uptime but off those rankings, which is how a newly onboarded service is held back until it has enough history to rank fairly.

Always present, never omitted: an absent field would read as "the API does not know" rather than "hidden".

Public landing page for the service. Always present.

The provider's own status page, where it publishes one. Omitted rather than empty when it does not, so a client never has to special-case "".

Carried on the list endpoint as well as the detail one, so rendering a directory of services needs a single request.

Number of active checks measuring this service. Checks registered but not yet active are excluded, so the count matches what the fleet is really executing. 0 for a newly registered service whose checks have not landed yet.

Availability percent over the rolling trailing 24 hours, computed from the per-minute consensus aggregate, with unknown minutes excluded from the denominator.

Measured directly rather than derived from the per-day rollup, whose buckets are anchored to UTC midnight: averaging a partial today against yesterday would bias against a service that was unhealthy hours ago. null when the window has no measurements yet.

Availability percent over the trailing 7 days, derived from the per-day rollup (same source as availability_30d / availability_90d). null when the window has no measurements yet.

Availability percent over the trailing 30 days, derived from the per-day rollup (excludes unknown minutes from the denominator). null when the window has no measurements yet.

Same as availability_30d, over 90 days.

Active checks for this service. Always an array, never null, and empty for a newly registered service whose checks have not landed yet.

Each vantage point's current view of the service, taken from the most-recent minute that probe reported on, within a 5-minute lookback. A probe that has not reported inside that window is absent from the array rather than listed as unknown. Always an array, never null, and empty for a service with no recent measurements.

Stable check identifier, formed from the service id, the check type and the target it covers.

Probe type. Currently one of http, tls, storage, dns. Typed as a string rather than an enum so adding a probe type stays a non-breaking change.

What the probe hits: a URL, an IP and port, a hostname. The format depends on check_type.

Where the real target embeds a private identifier, such as a storage bucket name, the API substitutes a redacted placeholder of the same shape (for example https://redacted.s3.eu-west-1.amazonaws.com/probe.bin). The check is still described, down to the operation and the region, without publishing the identifier. Only the public wire shape is substituted; the probe hits the real target.

Probe cadence in seconds.

Stable probe identifier from the fleet registry, e.g. hzr-fsn1. Use it as the key when joining probes against probe metadata such as location and provider.

Per-probe consensus across the service's checks within the most-recent reported minute. unknown is not valid here: a probe with no recent report is absent from the array entirely.

p50 latency this probe observed in the most-recent minute, taken as the maximum across the service's checks, so a service whose HTTPS check is fast and TLS check is slow reports the slower number.

null when every measurement in that minute failed, which is a different case from the probe not reporting at all: that probe is absent from the array.

Timestamp at the start of the bucket, UTC, RFC 3339.

Percent of measured minutes in the bucket that were classified up. 0 when the bucket has no measured minutes (in which case status is unknown).

Count of minutes in the bucket with consensus down.

Count of minutes in the bucket with consensus degraded.

Success-count-weighted p50 (median) response time, in milliseconds, across every check and probe pair inside the bucket. null when the bucket contained no successful measurement, so a chart should break the latency line there rather than plot a zero.

100 * total_up / (total_up + total_down + total_degraded) across every measured minute in the period. 0 when no minute had measured data.

Sum of down_minutes across every point.

Sum of degraded_minutes across every point.

Success-count-weighted p50 response time, in milliseconds, across every successful measurement in the period. null when the period contained zero successful measurements. Useful as the headline "Average response time" for a service detail page.

Echoed back from the path parameter.

Buckets in ascending bucket-time order. Always renders as a JSON array (never null); empty [] is valid for a service with no measurements yet.

1-based, dense rank within this response. Tie-breaker is name ASC. Clients should NOT recompute rank; the server's tie-breaker is part of the methodology.

Slug-style identifier; cross-references /v1/services/{id}.

Human-readable service name.

Average availability percent over the requested period. Services with no measurements collapse to 0 (paired with current_status: unknown).

Rank movement against the previous publication, positive for an improvement and negative for a decline. Always absent in v1, because historical leaderboard state is not persisted yet. The field appears once it is.

Echoed when a ?category= filter was applied; absent on the unfiltered call.

Ranked rows, ordered by rank ASC. Always renders as a JSON array (never null); empty [] is valid after a category filter that matches no services.

Server wall-clock at response build time, UTC, RFC 3339. Useful for cache debugging, and for rendering an "as of" line alongside a ranking.