Bitbucket: Unable to connect to Bitbucket Cloud via SSH
Timeline of updates
- resolved
We experienced connectivity issues with Bitbucket Cloud via SSH, which only affected customers using IP allow listing. The service was unavailable for approximately 40 minutes. However, the issue was identified and resolved, and service was restored around 19:23 UTC.
- postmortem
SUMMARY
On September 10, 2024, between 6:34 PM UTC and 7:19 PM UTC, some Atlassian customers experienced an issue preventing users from connecting to Bitbucket Cloud via SSH. The issue arose from a change in how we determined IP allow lists, which inadvertently blocked access for customers with these controls enabled. The incident was promptly identified through our monitoring systems, and our teams initiated response protocols to mitigate the issue.
IMPACT
The incident only affected customers who had IP whitelisting enabled on their Bitbucket Cloud accounts. These customers experienced difficulties connecting via SSH due to the unintended blocking caused by a change in the IP allow list computation. The service interruption lasted approximately 45 minutes, during which time affected users were unable to access their repositories through SSH.
ROOT CAUSE
A change to IP allow list evaluation was incompatible with a new Bitbucket Cloud networking configuration. This inadvertently blocked SSH access for customers with specific allow lists restrictions enabled.
REMEDIAL ACTIONS PLAN & NEXT STEPS
To restore the SSH service, the team quickly rolled back the release responsible for the IP allow list issue. We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident:
- Improve monitoring coverage of IP allowlisting;
- Add additional tests and deployment validation checks for changes to IP allowlist configurations.
We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability.
Atlassian Customer Support
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
d4fdfc1c02d29889…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Bitbucket, started 2024-09-09 18:30 UTC, resolved after 0 min, 2 update(s).
- Title
- Unable to connect to Bitbucket Cloud via SSH
- Vendor
- Bitbucket
- Date
- URL
- https://rewindex.com/company/bitbucket/incidents/jfhrnk0m1jc9
Bitbucket profileRecent Bitbucket incidentsAll outages on September 9, 2024Bitbucket in September 2024MarkdownJSON