Insights · Field note · Infrastructure and resilience

Uptime as evidence

A claimed availability percentage is marketing. Measured availability with the method stated, the incidents listed and the recovery proven is evidence.

Uptime becomes evidence when it is measured by a stated method from a defined vantage point, reported per service over a defined period, accompanied by the incident list that explains every gap, and backed by recovery test records that show the service can be restored within its objectives. A percentage on a website is a claim. Customers’ auditors, insurers and enterprise buyers increasingly ask for the measurement, the incidents and the tests, because availability is a Trust Services Criterion under SOC 2 and a contractual commitment in most service agreements. Operators that publish the evidence are believed; operators that publish the number are asked for the evidence.

In detail

What the evidence shows.

Measured how

From where the measurement is taken, how often, what counts as down, whether planned maintenance is excluded and how. Two operators quoting the same percentage can mean different things. The method is stated with the number, or the number is not comparable.

The incident list

Every outage in the period with cause, duration, services affected and the control change that followed. An availability figure with no incident list invites the question of what was left out. An incident list with post-incident reviews is a sign of a program that learns.

Proven recovery

Uptime history describes the past. Recovery test records describe capability: how long it takes to restore each critical service and how much data would be lost. An operator with excellent history and no tests is reporting luck.

Publishing it

Operators that publish availability with method, incidents and testing earn trust from technical buyers and citations from engines answering questions about reliable providers. See resilience metrics boards understand, documenting resilience for insurers and the data centers and infrastructure growth edition.

By David Selakovic · Published 2026-10-16 · Revised 2026-10-16 · Reviewed every 180 days

Tell us what must not fail.

Discuss a Requirement →