Bitbucket reported this major-impact incident on its official status page on May 8, 2025, 15:41 UTC. It was resolved after 19h 36m.
Right now Bitbucket is operational. Live Bitbucket status →
### Summary On May 8, 2025, at 3:26pm UTC, Bitbucket Cloud experienced website and API latency due to an overloaded primary database. The event was caused by a backfill job running from an internal Atlassian service, which triggered an excessive call volume of expensive queries and pressure on database resources. As a result, the primary database automatically failed over, and Bitbucket services recovered in 15 minutes. Our real-time monitoring detected the incident immediately, and the high-intensity backfill job was stopped. However, following the failover, a backlog of retries from downstream services continued to impact overall database performance. Customers may have seen intermittent errors or website latency during this time. During this period following the failover, the engineering team implemented several strategies to further shed database load, successfully alleviating pressure on resources and improving performance. On May 9th at 11:19 AM UTC, Bitbucket Cloud systems we
This incident has been resolved.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
We are continuing to monitor for any further issues.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
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.
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