Critical impactResolvedDevOps

Bitbucket outage: Disrupted Bitbucket availability

Bitbucket reported this critical-impact incident on its official status page on Mar 6, 2026, 02:44 UTC. It was resolved after 2h 27m.

Right now Bitbucket is operational. Live Bitbucket status →

🔔 Get alerted when Bitbucket has issuesFree · email alerts · no credit card
Mar 6, 2026, 02:44 UTC
started
Mar 6, 2026, 05:11 UTC
resolved
2h 27m
duration
Critical
impact

Affected components

  • API
  • Authentication and user management
  • Email delivery
  • Git LFS
  • Git via HTTPS
  • Git via SSH
  • Pipelines
  • Purchasing & Licensing
  • Signup
  • Source downloads
  • Webhooks
  • Website
  1. postmortemMar 26, 2026, 17:09 UTC

    ### 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

  2. resolvedMar 6, 2026, 05:11 UTC

    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.

  3. identifiedMar 6, 2026, 05:00 UTC

    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.

  4. identifiedMar 6, 2026, 04:04 UTC

    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.

  5. identifiedMar 6, 2026, 03:10 UTC

    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.

  6. investigatingMar 6, 2026, 02:44 UTC

    We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Bitbucket's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Bitbucket have incidents?

Bitbucket reported 3 incidents in the last 90 days, 1 of them major or critical. A typical incident lasted 1h 28m. See Bitbucket's uptime and incident history

Bitbucket outage on Mar 6, 2026: Disrupted Bitbucket availability · APIStatus.watch