Intermittent issues affecting Bitbucket cloud

Incident Report for Atlassian Bitbucket

Postmortem

SUMMARY

On June 13, 2025, between 08:58 UTC and 09:34 UTC, a subset of Bitbucket website and API users experienced an error page when attempting to load the website or make API requests. This was caused by high resource usage on a core Bitbucket service’s database, leading to an increase in query response times. A reoccurrence of the issue impacted website reliability again between 12:24 UTC and 14:02 UTC. The incident was detected within 6 minutes by monitoring and was fully mitigated by running scaling database capacity, running database maintenance operations, and removing a faulty read replica, which put Atlassian systems into a known good state. The total time to resolution was about 36 minutes for the first occurrence and one hour and 38 minutes for the second occurrence.

IMPACT

The total window during which we saw the impact was June 13, 2025, between 08:58 UTC and 14:02 UTC. The incident caused service disruption to customers trying to access the Bitbucket.org website and APIs. Customers may have seen a “something went wrong” error page when trying to access the website or APIs. Git operations over SSH and HTTPS were not impacted.

ROOT CAUSE

The issue originated from a problem with query plan execution time on read replica instances. This led to increased query latency, spikes in CPU usage, and ultimately resulted in longer request times. As a result, the influx of incoming requests to Bitbucket led to a saturation of connections. This resulted in Bitbucket web requests returning slowly or showing an error page.

REMEDIAL ACTION PLAN & NEXT STEPS

We fully understand that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified with existing coverage.

We are prioritizing the following improvement actions designed to avoid repeating this type of incident:

Continue to improve database resiliency and read replica routing for Bitbucket Cloud’s dependencies
Improve database monitoring and failover speed to reduce time to recovery
Run database maintenance tasks and improve process to discover and upgrade all databases to well known versions

We apologize to customers whose services were impacted during this incident; we are taking steps to improve the platform’s performance and availability.

Thanks,

Atlassian Customer Support

Posted Jun 27, 2025 - 03:12 UTC

Resolved

Between 08:15 and 14:10 UTC on June 14th, 2025, some Bitbucket Cloud customers experienced an issue loading pages and executing API requests.

We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the issue have been addressed and we’re actively working on a permanent fix. Services are now operating normally.

Once we complete our internal incident review process, we will publish a more detailed postmortem of what went wrong, along with steps we're taking to prevent this from happening again in the future.

Posted Jun 13, 2025 - 15:52 UTC

Identified

Our team continues to actively investigate and monitor the intermittent issues with Bitbucket. We are working to ensure full stability and will provide further updates as more information becomes available.

Posted Jun 13, 2025 - 14:48 UTC

Update

Our team is focused on investigating and resolving the intermittent issues with Bitbucket, and we’ll keep you posted with further updates.

Posted Jun 13, 2025 - 13:59 UTC

Investigating

We’re experiencing a recurrence of the intermittent issue affecting Bitbucket cloud.
Our team is working diligently to resolve this issue, and we’ll keep you posted with further updates.

Posted Jun 13, 2025 - 13:14 UTC

This incident affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, and Signup.