With respect, moderators, there was a question in my last post. It was in the second last sentence. To save you the trouble of hunting for it this time, I'll post it differently at the top.
Question: Are the Lindens looking at their development and release processes with a view to reducing the incidences of overrun downtimes?
Now, for the rest of my post, as it was before.
When someone announces a downtime to me and puts a time limit on it, I expect to see an available service soon after the announced downtime window finishes, not routine just-under-the-wire announcements as to what problem or other there is with bringing it back up. Once or twice is workable, beyond that it starts to suggest serious systemic problems with estimating and completing work to a fixed schedule. I suppose not having to enforce or adhere to any kind of SLA helps.
Really though LL, you need to get better at this. You aren't, which is why you routinely overrun your downtime windows by levels that would be unacceptable in almost any sensible technology business model. So, LL, what are you doing to fix this? It WILL catch up with you some day, and I'd hate to be you when that happens.