What is Uptime?

Uptime is typically expressed as a percentage of a window, or as a continuous duration since the last restart. The measurement depends entirely on what counts as up, and that definition is where the metric gains or loses its meaning.

A process that is running, a port that accepts connections, and a service returning correct responses within acceptable latency are three very different bars. Simple uptime monitoring usually checks the first or second, and users care about the third.

Its persistence comes from being immediately understandable to anyone.

• Universal legibility: non technical stakeholders understand it without explanation.
• Trivial to measure: a basic health check produces it.
• Historical continuity: long-term trends are easy to maintain and compare.
• Marketing use: a single number for status pages and sales material.

Uptime tracks the system rather than the experience. A service can report 100% uptime while returning errors to a third of requests, because the process was running the whole time.

It also ignores degradation entirely. Response times ten times normal produce perfect uptime and a service most users would describe as broken. And a single availability figure hides distribution: continuous partial failure and one long outage look identical.

The terms are used interchangeably and should not be. Uptime typically measures whether the system was running, from the system's point of view. Availability, measured properly as successful requests over total requests, measures whether users got what they asked for.

The gap between them is exactly where user affecting problems hide. A service with 99.99% uptime and 99.5% request success has a real reliability problem that the uptime figure conceals. When a number is quoted, the useful question is always which one it is and where it was measured.