Update: The migration was completed successfully.  We were down for maintenance for just over an hour, about one third of our scheduled window. If you encounter any issues, please file a helpdesk ticket.

We’ll be moving from our servers based in Dallas, Texas, to Amazon’s AWS cloud starting at 11pm EST (Click the link to view the time in major cities around the globe). This will be a 3-hour window, but we’re aiming to have the system back online within an hour.

This blog and files uploaded by users in Táve 2.9 are already in the AWS cloud and every piece of the Táve 3.0 beta has been in AWS from the start as well. Wednesday’s migration completes our transition by moving the remaining 2.9 infrastructure. We’d wait until after the 3.0 release, but having 2.9 on AWS before then will dramatically speed up the studio-initiated upgrade system and also makes it easier for us to maintain both systems, as they’ll now have similar infrastructure behind them.

If this migration announcement seems familiar, you may recall we had planned on migrating back in March but postponed it due to an issue with Amazon’s email services. That has been resolved and in fact the new email service provider means we can now send emails from your studio without listing Táve as the Sender in Táve 3.0.