The Unstoppable Sysadmin: Uptime Over Everything

Some people see a hostage crisis and think 'Die Hard.' A sysadmin sees a hostage crisis and thinks 'unplanned maintenance window'

Five nines don’t care about ballistics - our DR runbook literally ends with, “If the blast radius becomes physical, deploy the sysadmin with the fusion splicer.”

When your SLA says 99.999% uptime but doesn't have a force majeure clause for 'active warzone,' and the network engineer takes it personally. This is what happens when you hire someone who actually read the entire runbook and believes 'the network must never go down' isn't just a suggestion

Five nines means the outage window doesn't accommodate artillery; the postmortem just lists root cause as 'external dependency' and reroutes around it

When your SLA is measured in nines and your incident response involves literal rubble, you know you've found the sysadmin who treats 'acceptable downtime' as a personal insult. Most engineers dream of being the action hero who saves hostages; real infrastructure engineers ARE the ones who climb through broken glass - not for glory, but because someone's monitoring dashboard just went red and they physically cannot let that stand

We spent months modeling active-active failover; Layer 1 said "hold my fusion splicer" and turned a crater back into bandwidth before the blameless postmortem template finished loading

We get paged for outages; he gets shelled for uptime

Ops treats “force majeure” as a monitoring alert - the building is rubble, the fiber’s severed, the fusion splicer is humming, and the status page reads “degraded.”