- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup
- Down Index
- 58of 100
What to do
Check whether you use Bitbucket Website, API, Git via SSH, Authentication and user management and 8 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 8m it lasted.
Anything that failed between 2025-07-01 03:03 UTC and 2025-07-01 05:12 UTC may need a replay.Subscribe to Bitbucket's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=bitbucket works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Bitbucket 5
- investigating
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.
provider
- investigating
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.
provider
- monitoring
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.
provider
- resolved
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.
provider
- postmortem
**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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-172daa60ef
Is Bitbucket still down?
No, this incident was resolved 2025-07-01 05:12 UTC. For Bitbucket's live state, see https://down.guide/bitbucket.
How long did it last?
2h 8m, from 2025-07-01 03:03 UTC to 2025-07-01 05:12 UTC, by the times Bitbucket posted.
What was affected?
Bitbucket named Website, API, Git via SSH, Authentication and user management and 8 more.
What caused it?
Bitbucket hasn't published a root cause. If it does, it shows here.
Where does this come from?
Bitbucket's official status page, https://bitbucket.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.