Bitbucket incident
Users experiencing errors attempting to load Bitbucket
Bitbucket experienced a major incident on July 1, 2025 affecting Website and API and 1 more component, lasting 2h 8m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 01, 2025, 03:03 AM UTC
We are aware of some users experiencing issues when attempting to load Bitbucket. Our team is investigating with urgency and will provide an update as soon as possible.
- investigating Jul 01, 2025, 04:03 AM UTC
We are continuing to investigate issues that are being experienced by users attempting to load Bitbucket. We apologize for any inconvenience this has caused and we will provide further updates as soon as possible.
- monitoring Jul 01, 2025, 04:44 AM UTC
Our team has identified a network configuration error that was causing the issues relating to Bitbucket being unavailable for some users. This error has now been rectified. We will continue to monitor services closely. Additional updates will continue to be shared here.
- resolved Jul 01, 2025, 05:12 AM UTC
Between 02:36 UTC to 04:45 UTC 1 July 2025, we experienced a network configuration error for Atlassian Bitbucket, resulting in the product being unavailable for most users during this time. The issue has been resolved and the service is operating normally.
- postmortem Aug 19, 2025, 08:02 AM UTC
**Incident Narrative** On July 1, 2025, at 02:36 UTC, a service disruption occurred leaving Atlassian customers unable to access Bitbucket. The primary issue was identified as an inconsistent network access control list \(ACL\) rule, which inadvertently blocked certain IP ranges necessary for file system access. This network misconfiguration caused a service outage until the rule was corrected at 04:35 UTC, restoring normal service operations. **Root Cause** The root cause of the incident was traced to a network ACL misconfiguration during a routine update. A race condition in the deployment software led to an inconsistent state. This left a gap in network traffic management, disrupting essential services and resulting in inaccessibility of Bitbucket functionalities. **Mitigators** To restore service, the team repaired the inconsistent network ACL configuration, recreated the missing network ACL rule, re-establishing connections to the affected file systems. **Actions** In response to the incident, we have implemented additional mechanisms to help prevent the inconsistent network configuration and better ensure the expected network ACL rules remain intact, including during deployment.