Worked for a IT managed services place that made staff pull 24+ hrs non stop regularly. I walked away from that career and spent years recovering from a 38 hr shift where I was begging my managers to get me relief. "Your the only guy that knows this well enough" is a sign you work for a failing organization pinning that shit on you. I learned that the "business" and sales dudes absolutely will trade your health/lively hood for a few extra bucks on commission.
Unless the bug being fixed was some sort of critical security failure that enabled people to game the exchange or manipulate balances. I am guessing this is more of a screw-up by amateurs than a 'take it all down until this hole is patched' situation, but there is a slim possibility that keeping it up was a bigger risk than the reputation hit of extended downtime.
Looks like these are announced improvements to the Exchange engine. Really look forward to a post-mortem on this issue.
Curious if they had issues with database migrations or such, that required recovery from backup in case of errors. Plus, for sure there were bugs in the code itself.
https://status.kraken.com
Sounds like their staff has being going without sleep for a few days now.