Bitbucket experienced a critical incident on January 7, 2026 affecting Website and API and 1 more component, lasting 2h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jan 07, 2026, 04:23 PM UTC
We are actively investigating reports of a partial service disruption affecting Bitbucket Cloud for some customers. We'll share updates here within the next hour or as more information is available.
- investigating Jan 07, 2026, 04:38 PM UTC
We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.
- monitoring Jan 07, 2026, 05:49 PM UTC
The issue has now been resolved, and the service is operating normally for all affected customers. We will continue to monitor closely to confirm stability.
- resolved Jan 07, 2026, 06:53 PM UTC
On Wednesday, January 7, 2026, Bitbucket Cloud 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.
- postmortem Jan 30, 2026, 04:02 PM UTC
### Summary On Jan 7, 2026, between 15:28 UTC and 17:04 UTC, Atlassian customers using Bitbucket Cloud could not load the dashboard landing page. Users also faced degraded performance and intermittent failures navigating other parts of the application or using public REST APIs. The event was caused by an unexpected load on a public API, causing long-running queries on a database which resulted in failed web and api requests. The incident was detected within three minutes by automated monitoring systems and mitigated by introducing stricter limits on the API for certain traffic, while taking manual actions on the impacted database, restoring Bitbucket to a healthy state. ### **IMPACT** Occurring on Bitbucket Cloud on Jan 7, 2026, between 15:28 UTC and 17:04 UTC, the incident caused degraded performance and intermittent failures to a subset of customers interacting with the Bitbucket web application and public APIs. Git operations over SSH and HTTPS were not impacted. ### **ROOT CAUSE** The event was caused by an unexpected load on a public API. The request volume during this period resulted in high resource utilization our central database’s read replicas, impacting website and our API performance and reliability. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know outages reduce your productivity. Although we have several testing and prevention processes, this issue went undetected because a specific request pattern on a public API was not tested against the traffic volume seen during the incident. We prioritized the following actions to prevent repeating this type of incident: * Improve rate limiting and caching capabilities at multiple points in our networking and application layers. * Apply stricter rate limits for specific public APIs to protect infrastructure health and shared application resources. * Optimize performance of specific queries and codepaths on these APIs to handle high request loads. 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