timetobail
My stack

Bitbucket · Forced move · Tracked since October 13, 2026 · Sources checked Oct 13

Time to bail on Bitbucket Cloud Git over SSH (bitbucket.org)?

Time to Bail · Boarding pass

FromBitbucket Cloud Git over SSH (bitbucket.org)
ToYour pick

Act. You can stay.

After November 12, 2026, SSH to bitbucket.org is refused. Point Git remotes to ssh.bitbucket.org.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
SSH to bitbucket.org refused after
Time left
27days
Status
Act

Bitbucket Cloud SSH moves to ssh.bitbucket.org by November 12, 2026

Bitbucket Cloud moves Git over SSH to a new host name, ssh.bitbucket.org. After November 12, 2026, SSH to bitbucket.org is refused. HTTPS is not affected.

How it is winding down

  1. May 12Posted by the Atlassian teamDone
  2. Nov 12SSH to bitbucket.org refused afterNext

What to do before November 12

Tick steps as you go. Your progress stays in this browser.

  1. Find SSH remotes

    Run git remote -v in each repo. Look for git@bitbucket.org.

  2. Switch each remote

    Run git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git and trust the new host key.

  3. Update CI and firewalls

    Change SSH URLs in CI, deploy keys and scripts. Allow ssh.bitbucket.org on port 22.

Facts we checked

Facts and their sources
SSH to bitbucket.org refused afterNovember 12, 2026[1]
New SSH hostssh.bitbucket.org[1]
HTTPS accessNot affected; bitbucket.org serves only HTTPS (web and API)[1]
Command to switch a repogit remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git[1]
FirewallsAllow ssh.bitbucket.org on port 22[1]
Posted by the Atlassian teamMay 12, 2026[1]
Repos and CI jobs that use SSH to bitbucket.orgFail after November 12, 2026 unless updated[1]

Sources

Check it yourself. Every fact above links here.

  1. Upcoming change to Bitbucket Cloud SSH access: move from bitbucket.org to ssh.bitbucket.org Atlassian · primary · checked Oct 13
Read the published editorial report

What changed

Time to bail on Bitbucket Cloud Git over SSH (bitbucket.org)? Act. You can stay. After November 12, 2026, SSH to bitbucket.org is refused. Point Git remotes to ssh.bitbucket.org.

On our scale this is Act: change a setting or plan before the date. You can stay.

Bitbucket Cloud moves Git over SSH to a new host name, ssh.bitbucket.org. After November 12, 2026, SSH to bitbucket.org is refused. HTTPS is not affected.

Here are the facts we checked:

  • SSH to bitbucket.org refused after: November 12, 2026 (Atlassian)
  • New SSH host: ssh.bitbucket.org (Atlassian)
  • HTTPS access: Not affected; bitbucket.org serves only HTTPS (web and API) (Atlassian)
  • Command to switch a repo: git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git (Atlassian)
  • Firewalls: Allow ssh.bitbucket.org on port 22 (Atlassian)
  • Posted by the Atlassian team: May 12, 2026 (Atlassian)
  • Repos and CI jobs that use SSH to bitbucket.org: Fail after November 12, 2026 unless updated (Atlassian)

You can stay on Bitbucket. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Atlassian is the main source for this page. Bitbucket has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

Repos and CI jobs that use SSH to bitbucket.org: Fail after November 12, 2026 unless updated.

The date to remember is November 12, 2026. Make the change before then.

What to do before November 12

  1. Find SSH remotes. Run git remote -v in each repo. Look for git@bitbucket.org.
  2. Switch each remote. Run git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.git and trust the new host key.
  3. Update CI and firewalls. Change SSH URLs in CI, deploy keys and scripts. Allow ssh.bitbucket.org on port 22.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Bitbucket Cloud Git over SSH (bitbucket.org) can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product