>The downtime isn't the issue, it's the lack of communication during the downtime.
What would that communication be?
If I'm a team of sysadmins working to find out what caused the issue and trying to fix it properly as soon as I can, the last thing I want to do is being asked by some manager type "well will it be ready".
It's not as if you can tell when a bug will be found and fixed, or if some idea you try will definitely work. The only answer is: "it will be ready when it's ready".
And in fact most other answers are BS. How many time have you heard from hosting providers for example: "We had a glitch in our network, but it's fixed now" -- and the issue persists or comes back with a vengeance a few hours later?
What would that communication be?
If I'm a team of sysadmins working to find out what caused the issue and trying to fix it properly as soon as I can, the last thing I want to do is being asked by some manager type "well will it be ready".
It's not as if you can tell when a bug will be found and fixed, or if some idea you try will definitely work. The only answer is: "it will be ready when it's ready".
And in fact most other answers are BS. How many time have you heard from hosting providers for example: "We had a glitch in our network, but it's fixed now" -- and the issue persists or comes back with a vengeance a few hours later?