Author Archives: Jim Redmond

Bitbucket System Engineer

Deprecating TLSv1 and TLSv1.1

As part of our never-ending quest to secure your repositories, Bitbucket Cloud will be disabling support for TLSv1 and TLSv1.1 effective 1 December 2018. This will affect all HTTPS traffic to Bitbucket, including: Git or Mercurial traffic to bitbucket.org The bitbucket.org …

Renewing our certificates, plural

The certificate behind https://bitbucket.org is up for renewal. We’re planning to switch to our new TLS certificates – one RSA, one ECDSA – at around 00:05 UTC on Friday, 27 April 2018. (SSH traffic will not be affected by this.) What does this mean? After …

Bitbucket Cloud: now available over IPv6

Just after 18:00 UTC 19 July 2016, we published our first set of AAAA records in DNS, making bitbucket.org and its associated hostnames available to the world over IPv6. We’re taking a dual-stack approach here, so IPv4 addresses will continue to work for the foreseeable …

Renewing our certificate

It’s almost time to replace our main bitbucket.org certificate, so we’re planning to do that at 00:00 UTC on May 6 2016. Most users shouldn’t notice any difference. However, if you’re using Mercurial over HTTPS, then you might see this error message after …

Making Bitbucket’s network better, faster, and ready to grow

UPDATE 2016-01-26: All IPs have been moved, and the old IPs are no longer handling traffic. Thanks to you, Bitbucket is outgrowing its old network infrastructure. We’re going to make some upgrades that should make Bitbucket faster, more reliable, and ready for further …

What caused our service outage on Wednesday?

We owe you an explanation for the recent service interruption. On Wednesday, our users were unable to push or pull over SSH or HTTPS, access the GUI or API, or complete important tasks on time. We violated the cardinal rule of SaaS – “don’t have downtime” …