Service level agreement

What the availability commitment is measured on, how, and what a customer receives when it is missed.

Awaiting counsel's text. This page shows the structure the document will have. It is not the agreement and binds no one; the published text will replace it.

The Business edition carries a 99.9% monthly availability commitment (Business Plan §7.1). This page states what that commitment is measured on, how it is measured, and what a customer receives when it is missed. The contract a customer signs is the binding version, and §11.3 puts commercial documents with legal. This page is what the product can actually measure, so the contract should not promise more than it states.

What is covered

The delivery path is covered: the one thing a customer's viewers depend on, and the Critical tier of §L10.

SurfaceCoversProbed atInternal target
Version manifest/m/{key}, the loader and the player artefacts: what every page load fetchesthe manifest service's /healthz, through the edge99.99%

The SLA commits to 99.9%, below the 99.99% the tier is run to, so the commitment sits inside what the service is built for.

What is probed

Every public name is probed, through the edge, and published on the status page under its tier. Only the Critical-tier version manifest is covered by the commitment above; the rest is measured and published so a customer can see it, not credited.

SurfaceProbed atTierInternal targetCovered
manifestcdn.<domain>/healthzCritical99.99%yes
mediamedia.<domain>/media/api/v1/delivery/healthz — mediad's readiness, under the one prefix the edge forwardsCritical99.99%not yet
media-edgethe Cloudflare Worker's same path, when PROBE_MEDIA_EDGE_URL (compose) or probe_media_edge_url (OpenTofu) names it; not on the status pageCritical99.99%not yet
ingesttelemetry.<domain>/healthzImportant99.9%no
control-planeapi.<domain>/control-plane/api/v1/health/readyStandard99.5%no
authauth.<domain>/auth/api/v1/health/readyStandard99.5%no
docsdocs.<domain>/Standard99.5%no
statusstatus.<domain>/Standard99.5%no

Hosted media delivery is Critical-tier and measured from now on, but is not yet in the commitment: adding it changes what credits are owed, which is the contract's to decide. Until then the figure is published, not promised. On a deployment whose media.<domain> points at the Worker, the media probe meets the Worker (which answers the path itself) and media-edge is the same; the origin's own health is then visible only to the orchestrator.

The following are not covered. Those with a row in the table above are published on the status page for information only; analytics is served by the control plane and licence activation by the manifest service, and neither has a row of its own:

  • Control plane, authentication, analytics, docs and this status page — the Standard tier (99.5% target). An outage there stops the dashboard, not a video (§L8.5). A cached page keeps playing.
  • Licence activation and telemetry ingest — the Important tier (99.9% target). Both degrade by design. A device licenses offline within its grace, and a player drops telemetry rather than wait for it (§18.3.4).
  • Customer-hosted media, and media delivered from a customer-chosen host. What PB Play does not serve, it cannot measure.

How availability is measured

services/prober probes each surface every 30 seconds with a 5-second timeout, from outside the stack it measures. A probe is up when it answers 2xx. Every probe is recorded per minute in uptime_minutes.

Monthly availability = probes answered 2xx ÷ probes sent, over the calendar month in UTC, for the delivery path. /public/uptime serves the same figures per UTC day, and the status page draws them. A day with no probes is shown as unmeasured, never as up.

Excluded from the calculation:

  • scheduled maintenance announced on the status page at least 72 hours ahead, to a limit of four hours a month;
  • failures caused by the customer: a revoked key, a misconfigured page, media hosted elsewhere;
  • force majeure as the contract defines it.

A probe that fails because the prober itself could not reach the network counts as unmeasured, not down. Run the prober from two places and take the better answer per minute before relying on the figure for credits.

Service credits

Monthly availabilityCredit, % of that month's subscription fee
< 99.9%10%
< 99.5%25%
< 99.0%50%

A credit is claimed within 30 days of the month's end and applied to the next invoice. Credits are the sole remedy. The contract sets the figures; these are the defaults it starts from.

What the design adds beyond the number

The delivery path fails open: a cached manifest, then the last known-good release, then the version compiled into the loader (§4.5, §R3). So a manifest outage is, for a page that has loaded before, a player on an older version, not a blank frame. The SLA measures the service. The product is built so that the service's failures seldom reach a viewer.

  1. The contract’s own terms

    Awaiting counsel's text.