Update: New IP addresses for Bitbucket Cloud

Note: This is a follow-up to a May 2023 blog post about Bitbucket Cloud IP address changes. It includes updates to the list of IP addresses, as well as to the rollout timing.

Earlier this month, we began migrating traffic to use new IP addresses for bitbucket.org. We expect to finish the migration by July 31, 2024. The old IP addresses are now deprecated, and we will begin to retire them starting August 31, 2024.

There will not be any downtime for this migration, and most users will not have to do anything differently because of this migration.

Developers, teams and organizations that use a firewall, access list, security group or other network policy to restrict outgoing access to a particular IP will need to update their rules to permit connections to our new addresses.

The change does not affect the IPs used by Bitbucket to connect to remote servers, such as for webhooks.

Why are we doing this?

Bitbucket has seen amazing growth over recent years, with millions of developers and teams using it to build better software.

Continuing our commitment to performance and reliability, we'll be making enhancements to our network edge, introducing additional points of presence in the US, Europe and Asia.

This necessitates the addition of new IP addresses to our IPv4 A and IPv6 AAAA DNS records.

How will this affect you?

Most users will not have to do anything special for this change. Your DNS servers should pick up the new IPs within a few minutes, and your systems should start using the new IPs right away. The old IP addresses are now deprecated; bitbucket.org will be served from them until August 31, 2024, from which point we will begin to retire them.

Firewall considerations

If you control access to Bitbucket from your network with a firewall, then you may need to update your configuration. Please ensure these new IPs are allowed through your firewall.

The new destination addresses for bitbucket.org, bitbucket.com, api.bitbucket.org, bitbucket.io, bytebucket.org, altssh.bitbucket.org are listed below.

IPv4:

  • 104.192.136.0/21
  • 185.166.140.0/22
  • 13.200.41.128/25

IPv6:

  • 2401:1d80:3000::/36

These ranges are completely owned and controlled by Atlassian, however they do include Atlassian products other than Bitbucket.

Deprecated IP addresses

As a result of this migration, the following IP ranges and IPs have been deprecated. Deprecated IPs will begin to be retired from August 31, 2024.

IPv4:

  • 18.205.93.0/25 (deprecated)
  • 18.234.32.128/25 (deprecated)
  • 13.52.5.0/25 (deprecated)

IPv6:

  • 2406:da00:ff00::22cd:e0db (deprecated)
  • 2406:da00:ff00::6b17:d1f5 (deprecated)
  • 2406:da00:ff00::3403:4be7 (deprecated)
  • 2406:da00:ff00::22c3:9b0a (deprecated)
  • 2406:da00:ff00::22c5:2ef4 (deprecated)
  • 2406:da00:ff00::22c2:0513 (deprecated)
  • 2406:da00:ff00::34cc:ea4a (deprecated)
  • 2406:da00:ff00::22e9:9f55 (deprecated)
  • 2406:da00:ff00::22c0:3470 (deprecated)
  • 2406:da00:ff00::34c8:9c5c (deprecated)
  • 2406:da00:ff00::12d0:47c8 (deprecated)
  • 2406:da00:ff00::22ed:a9a3 (deprecated)
  • 2406:da00:ff00::23a8:5071 (deprecated)
  • 2406:da00:ff00::36ec:9434 (deprecated)
  • 2406:da00:ff00::3416:7161 (deprecated)
  • 2406:da00:ff00::36ec:bea6 (deprecated)
  • 2406:da00:ff00::12cd:ae3d (deprecated)
  • 2406:da00:ff00::12cc:b432 (deprecated)
  • 2406:da00:ff00::1714:aa06 (deprecated)
  • 2406:da00:ff00::342d:4312 (deprecated)
  • 2406:da00:ff00::22ee:e721 (deprecated)
  • 2406:da00:ff00::34cf:03c4 (deprecated)
  • 2406:da00:ff00::3657:a859 (deprecated)
  • 2406:da00:ff00::1716:0c22 (deprecated)
  • 2406:da00:ff00::36ec:507a (deprecated)
  • 2406:da00:ff00::3448:67ee (deprecated)
  • 2406:da00:ff00::36ad:fb4d (deprecated)
  • 2406:da00:ff00::22ce:9394 (deprecated)
  • 2406:da00:ff00::12d0:5d6e (deprecated)
  • 2406:da00:ff00::3402:732e (deprecated)
  • 2406:da00:ff00::36d1:8b98 (deprecated)
  • 2406:da00:ff00::3414:6492 (deprecated)
  • 2406:da00:ff00::3437:b4cb (deprecated)
  • 2406:da00:ff00::22e2:3a76 (deprecated)
  • 2406:da00:ff00::34c9:c443 (deprecated)
  • 2406:da00:ff00::3405:6cad (deprecated)
  • 2406:da00:ff00::12ea:0a19 (deprecated)
  • 2406:da00:ff00::23a8:6621 (deprecated)
  • 2406:da00:ff00::3401:9341 (deprecated)
  • 2406:da00:ff00::3654:c786 (deprecated)
  • 2406:da00:ff00::3448:4e57 (deprecated)
  • 2406:da00:ff00::36a4:e08c (deprecated)
  • 2406:da00:ff00::36a4:f8a6 (deprecated)
  • 2406:da00:ff00::22c8:ada3 (deprecated)
  • 2406:da00:ff00::34cd:a4b9 (deprecated)
  • 2406:da00:ff00::23a8:b9b1 (deprecated)
  • 2406:da00:ff00::3402:affc (deprecated)
  • 2406:da00:ff00::12cd:d438 (deprecated)
  • 2406:da00:ff00::34ce:b43b (deprecated)
  • 2406:da00:ff00::342d:1804 (deprecated)
  • 2406:da00:ff00::36ae:07e7 (deprecated)
  • 2406:da00:ff00::3456:314c (deprecated)
  • 2406:da00:ff00::36af:42a0 (deprecated)
  • 2406:da00:ff00::3414:0248 (deprecated)

SSH considerations

Our server’s SSH key is not changing, so most SSH clients will continue to work without interruption. However, a small number of users may see a warning similar to this when they push or pull over SSH:

Warning: the RSA host key for 'bitbucket.org' differs from the key for the IP address '18.205.93.1'

The warning message will also tell you which lines in your ~/.ssh/known_hosts need to change. Open that file in your favorite editor, remove or comment out those lines, then retry your push or pull.

Additional resources

These resources have been updated with the new IP addresses: