Skip to content

Instantly share code, notes, and snippets.

@ehotinger

ehotinger/availability-numbers-every-programmer-should-know.md

Created June 24, 2024 17:46
Show Gist options
  • Save ehotinger/399c5d706e7612cefc1e5aee2c5f5bd5 to your computer and use it in GitHub Desktop.
Save ehotinger/399c5d706e7612cefc1e5aee2c5f5bd5 to your computer and use it in GitHub Desktop.
Download ZIP
Availability Numbers Every Programmer Should Know
Raw
availability-numbers-every-programmer-should-know.md

https://ehotinger.com/blog/availability-numbers-every-programmer-should-know/

Rough acceptable downtime to meet SLA (easier to remember)

Availability SLA Daily Weekly Monthly Yearly
95% 1h 8h 1d 18d
99% 15m 2h 7h 3d
99.9% 1m 10m 40m 9h
99.99% 10s 1m 0.48s 4m 50m
99.999% 1s 6s 40s 5m
99.9999% 0.1s 0.6s 4s 30s

Exact acceptable downtime to meet SLA

Availability SLA Daily Weekly Monthly Yearly
95% 1h 12s 8h 24m 1d 12h 13m 27s 18d 2h 41m 28s
99% 14m 24s 1h 40m 48s 7h 14m 41s 3d 14h 56m 18s
99.9% 1m 26s 10m 4.8s 43m 28s 8h 41m 38s
99.99% 8.6s 1m 0.48s 4m 21s 52m 9.8s
99.999% 0.86s 6s 26s 5m 13s
99.9999% 0.086s 0.6s 2.6s 31s
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment