status

03/31/2016 1:30 p.m.	We’re investigating.
03/31/2016 2:05 p.m.	We’re still trying to understand why we’re having issues.
03/31/2016 2:55 p.m.	We don’t have an ETA yet, we’re still investigating.
03/31/2016 3:09 p.m.	We seem to have found a temporary workaround.
03/31/2016 4:37 p.m.	We’ll continue using the workaround for now and keep investigating for a more permanent fix.
04/01/2016 9:37 a.m.	The workaround is not as effective as yesterday, we’re observing a higher system load than usual.
04/01/2016 10:55 a.m.	We’re pretty sure the underlying issue is a MySQL bug. Upgrading to a major MySQL version with no prior notification to our clients is not something we want to do. We’re instead installing a new MySQL server (running MariaDB 10.1). Clients that want to migrate from mysql1 to this new server should contact us by opening a support ticket from their administration panel.
04/01/2016 1:45 p.m.	The new MySQL server is ready, migrations will start shortly (for clients that opened a ticket).
04/01/2016 3:02 p.m.	We’ve restarted mysql1 10 minutes ago, it’s been running smoothly since then, although we cannot explain why.
04/01/2016 5:29 p.m.	mysql1 is still running fine. Migrations have been suspended for now as some databases refuse to get reimported and we’d like to find a proper solution until we resume the process.