Hi guys, sorry about this. Things should be back to normal now.
When you access the database via
mysql.server, it actually goes via a mysql-proxy service which runs on each of the servers. We had an AWS outage around 3AM this morning, which Giles and I were woken up by, and were hands-on to deal with. When things came back we bounced all the web servers out of caution, and when they rebooted the mysql-proxy service was restarted on each of them, and reconnected to the database. What we failed to realise was that the mysql-proxy services on the console and task servers did not automatically reconnect.
We've been through all of them this morning, so they should be working again. In short, this should only have affected console and task server processes this morning, your web apps should have been fine. In addition, mysql consoles you launch via the databases tab connect directly to the db, and bypass the proxy, so they would have been fine too.
Anyway, apologies again, we'll make a note to update our processes. Let us know if anything you've experienced doesn't seem to fit with this account.