These things should never happen and we are making sure they will not happen in the future. As Katya said, we are adding more capacity. As for announcing on Twitter - this happens for a second or two during extreme server load and then goes to normal. Announcing on Twitter won't really work here.
In general, if you refresh the page, everything is back to normal.
We are sorry about this. We are growing fast and experience some "growing up" problems. We promise to fix this as soon as possible.
Hi Max,
Although I appreciate you say that the server loads only happen for a second or two, this just isn't the case again today (as it was last week), today it's not been working properly for over 3 hours now. I did send a tweet, to which someone responded to just refresh, but that doesn't help, it'll often login then fail in designer mode, usually when doing something critical like saving. (I've already suggested that perhaps you should have a close button on the save modal window so at least we have the option to retry).
I appreciate that growing pains are inevitable and that is excellent news, but nothing improves people perception that keeping them informed and twitter or the blog will be the first place people go to find out if something is wrong 
So please in the future, just a simple tweet that "we are experiencing heavy loads and looking into it" would go a long way to stop user frustration.
Thank you
The issue with posting on Twitter or blog is that these spikes happen randomly (we are trying to figure out what's exactly causing this). It would be challenging to post on Twitter, these are not planned "updates".
You see the "We are doing updates" page because when the client is making a request to the server and the server is not responding with x-number of seconds, the system thinks we are doing an update. This feature was put in to show this page when we are actually doing an update.