Changes / Bitbucket / Disrupted Bitbucket availability
Bitbucket: Critical incident: Disrupted Bitbucket availability
Summary
Bitbucket reported a critical outage affecting Website, API, Git via HTTPS, Git via SSH, and Pipelines, leaving affected users unable to access services. It started at 2026-03-06 02:44 UTC and was resolved at 2026-03-06 05:11 UTC, lasting 2 h 27 min. The postmortem attributed the disruption to a hosting-provider regional provisioning API rate limit blocking application workers from handling website traffic.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Disrupted Bitbucket availability
Before: not present
After: critical
Before: not present
After: postmortem
Before: not present
After: 2026-03-06 02:44 UTC
Before: not present
After: 2026-03-06 05:11 UTC
Before: not present
After: API, Authentication and user management, Email delivery, Git LFS, Git via HTTPS, Git via SSH, Pipelines, Purchasing & Licensing, Signup, Source downloads, Webhooks, Website
Before: not present
After: We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.
Before: not present
After: We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users will experience Bitbucket being unavailable.
We'll continue to share additional updates here as more information is available, with our next update to be posted within 1 hour.
Before: not present
After: As restoration activities continue, we are now starting to see services recover for customers for Bitbucket Web and for Git HTTPS. We are continuing to work on mitigation across all remaining Bitbucket services.
Our next update will be provided within one hour or if full recovery is seen prior to that time.
Before: not present
After: Our team has now put mitigations in place across the majority of Bitbucket services and all are now actively recovering except for Pipelines, which is still being actively investigated.
We are continuing to monitor these services and we will provide further update within 1 hour or when services have fully recovered.
Before: not present
After: On 06 March 2026 UTC, Bitbucket experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Before: not present
After: ### Summary
On March 6, 2026, between 02:19 UTC and 04:00 UTC, Bitbucket Cloud experienced an incident impacting the web app, API, CLI, and Pipelines operations. This was caused by the Bitbucket application hitting a regional provisioning API rate limit with our hosting provider, preventing application workers from handling website traffic. The incident was detected within 1 minute by automated monitoring and mitigated by scaling systems down and then back up to full capacity which put Atlassian systems into a known good state.
### **IMPACT**
The incident resulted in a Bitbucket Cloud services being unavailable for 1 hour and 6 minutes on March 6, 2026 between 02:19 UTC and 03:25 UTC, followed by degraded website performance until 04:00 UTC. During this time, customers were unable to access Bitbucket services including the web app, Git operations \(clone, push, pull over HTTPS and SSH\), API, and running builds in Pipelines.
### **ROOT CAUSE**
The issue stemmed from a change to an internal deployment system that increased use of a platform credential service, hitting a quota with our hosting provider. This blocked Bitbucket services from deploying additional capacity because new application nodes request the credential service on startup and were rate limited. This caused degradation of Bitbucket experiences and more failed requests to Bitbucket Cloud’s website and public APIs.
### **REMEDIAL ACTIONS PLAN & NEXT STEPS**
The incident response team manually scaled down Bitbucket services, then gradually scaled them back up while closely monitoring our quota. We simultaneously engaged with our hosting provider to temporarily increasing this limit to unblock bringing more Bitbucket service capacity online.
We know that outages impact your productivity. While we have a number of testing and preventative processes in place, Bitbucket services lacked necessary boundaries to be resilient to upstream platform system changes. To help minimise the impact of breaking changes to our environments, we will implement additional preventative measures such as:
* Improve monitoring of shared Atlassian platform resources.
* Update Bitbucket application bootstrapping to prevent new capacity from failing during resource contention of shared platform services.
* Reduce Bitbucket’s dependency on shared hosting provider services.
* Deploy Bitbucket services across multiple regions to reduce single-region failure risk.
We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability.
Thanks,
Atlassian Customer Support
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Disrupted Bitbucket availability (this change) Bitbucket reported a critical outage affecting Website, API, Git via HTTPS, Git via SSH, and Pipelines, leaving affected users unable to access services. It started at 2026-03-06 02:44 UTC and was resolved at 2026-03-06 05:11 UTC, lasting 2 h 27 min. The postmortem attributed the disruption to a hosting-provider regional provisioning API rate limit blocking application workers from handling website traffic. | Major incident |
All Bitbucket changes → · Bitbucket profile · Markdown · JSON