99.9% uptime allows 43 minutes of downtime a month. 99.99% allows four. The entire argument between those two numbers, the architecture reviews, the multi-region diagrams, the on-call rotations, is a fight over 39 minutes.
Now price the 39 minutes. The industry’s own rule of thumb says each extra nine costs roughly ten times more: redundant everything, failover that needs rehearsing, a second region you hope stays in sync, a pager that owns somebody’s weekend. The most expensive minutes in engineering, bought monthly, forever.
Then ask who would have noticed them. If you sell B2B, your customers use the product during their working hours: call it 50 of the week’s 168. They are asleep, commuting, or living their lives for the other 70%. Downtime at 3am on a Sunday costs you nothing but the uptime badge. Most of the 39 minutes you’re insuring against would land in hours when nobody’s there.
And there’s a ceiling no SLA budget can break: availability multiplies. Your app times your cloud provider times your DNS times your payment processor. You cannot out-nine your dependencies. When a big cloud region has a bad afternoon, half the internet goes down together, and customers blame the internet, not you. Inside the herd, outages are forgiven. The nine you bought above your dependencies was never reachable.
What reliability looks like at your scale is different and mostly free. An external ping that tells you you’re down before a customer does. A backup you’ve actually restored, with a stopwatch running. A status page that tells the truth, and the email that says what broke and when it will be fixed. Customers don’t remember the 20 minutes you were down. They remember whether you told them.
Some businesses earn the nines: payments, hospitals, anything with real traffic at 3am. The signal is in your access logs, not in your ambitions. Open them and look at what happens at night.
Buy the nines your customers are awake for.