The tweet has been deleted as it mistakenly said 1 hour expected rather than 2!
For those of you asking, there's nothing to be concerned about with this downtime. We've already taken steps to prevent the series of events that made the Login Lockout happen from being a repeat performance, as well as more precautions beyond that.