In a few days we’ll flip a switch and migrate Bitbucket to a new hosting provider. During this migration Bitbucket will be unavailable up to six hours starting Sunday, July 07, 2013 at 19:00:00 UTC.
UPDATE: the migration is now complete — thanks for your patience everyone!
Scheduled downtime
Over the last several months we've put together a detailed plan that limits downtime to no more than six hours. Why so long? Bitbucket has maintained a synchronization of our filesystems and databases between the two data centers for several weeks. When we bring down Bitbucket at the current data center, it will take a few hours to finalize the replication between the two data centers before we can bring up the new location.
Once the synchronization is complete, we will bring the new location up and perform a series of integrity and performance tests to assure the new hardware is ready to go before making it publicly available.
Why we’re moving
Bitbucket has seen amazing growth since introducing free unlimited Git repositories for individuals and small teams. With over a million users now utilizing Bitbucket to build better software, moving our data center allows us to:
- link Bitbucket servers to the fastest internet connections possible
- co-locate with our Atlassian OnDemand platform for customers looking to integrate with JIRA
- co-locate with a direct link to Amazon Web Services
- scale Bitbucket’s infrastructure to 10s of millions of users
How this affects you
With the move to a new data center comes the addition of IP addresses.
Incoming IP addresses will be:
- 131.103.20.167
- 131.103.20.168
- 131.103.20.169
- 131.103.20.170
Outgoing IP addresses will be:
- 131.103.20.165
- 131.103.20.166
When pushing and pulling over SSH you’ll see a warning similar to this:
Warning: the RSA host key for ‘bitbucket.org’ differs from the key for the IP address ‘131.103.20.167’
The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, make the necessary changes, then retry your push or pull.
Stay updated
During the migration, we’ll post updates on Twitter and our status site providing the current status so you can follow our progress.
Thanks for your patience as we work to increase Bitbucket's performance and reliability. Please contact us at support@bitbucket.org if you have any questions about or during the migration.
