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.