We have received an update that services with our infrastructure provider are fully restored. This issue is now 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.

Between 06:35 to 9:27 UTC, we experienced degraded performance for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

### **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](http://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

On June 13, Bitbucket Cloud experienced intermittent availability. The issue has now been resolved, and the service is operating normally for all affected users.