GoKawiilBlog post argues status pages should ditch uptime percentages for downtime hours
A developer's essay critiques how services report reliability using uptime percentages like 99.72% or 98.98%, arguing these numbers look deceptively similar to non-experts even though they represent vastly different amounts of actual downtime. The author references Jason Gorman's observation that reliability gains become exponentially harder near 100%, comparing uptime metrics to earthquake magnitude scales where small numeric differences hide huge real-world impact. The proposed fix: status pages should show actual downtime duration (e.g., '12 hours affected in the last 30 days') alongside or instead of raw percentages.