• ↑↓ to navigate
  • ↵ to open
  • ⟶ to select
  • ⌘ ⌥ ↵ to open in a panel
  • ←→ to navigate
  • esc to dismiss
⌘ '
keyboard shortcuts

The Problem

Uptime guarantees need a standardized measurement to compare systems and set meaningful SLAs between providers and customers.

Core Idea

Availability is quantified by uptime percentage — “number of 9s” (99.9% = three 9s, 99.99% = four 9s). Each additional 9 represents a tenfold reduction in allowed downtime.

How It Works

  1. Availability is calculated as uptime divided by total time over a measurement period.
  2. 99.9% (three 9s) permits approximately 8 hours 45 minutes of downtime per year.
  3. 99.99% (four 9s) permits approximately 52 minutes of downtime per year.
  4. 99.999% (five 9s) permits approximately 5 minutes of downtime per year.
  5. Each additional 9 requires exponentially more redundancy and operational discipline.

Visual Explanation

availability_nines NINES Availability Nines T3 99.9% 3 nines ~8.8h/yr downtime NINES->T3 T4 99.99% 4 nines ~52min/yr downtime T3->T4 10x stricter T5 99.999% 5 nines ~5min/yr downtime T4->T5 10x stricter

Key Properties

  • Measured in “number of 9s” — 99.9%, 99.99%, 99.999%
  • Each additional 9 is a 10x reduction in allowed downtime
  • Three 9s = 99.9% uptime
  • Four 9s = 99.99% uptime
  • Five 9s = 99.999% uptime

Semantic Network

semantic_Availability_Nines THIS Availability Nines REL1 Related Concept THIS--REL1 related REL2 Builds Into THIS--REL2 builds into

Connections

Edge Cases & Gotchas

  • Nines are calculated over a full year — a single prolonged outage can blow through the entire budget
  • “Five 9s” is extraordinarily difficult in practice, requiring redundant everything (power, network, servers, data centers)
  • Partial outages (degraded but not down) are often excluded from SLA calculations, masking real availability