Bitbucket has degraded performance

SUMMARY

On February 11, 2025, between 15:41 and 16:26 UTC, Atlassian customers using Bitbucket Cloud experienced workspace access errors (HTTP 404) when attempting to access the website, API, and Git over HTTPS/SSH. The event was triggered by a failure in our feature flagging service, which inadvertently blocked some users from core services. The incident was detected within eight minutes by automated monitoring and was resolved 45 minutes later once a change to a feature flag configuration had been fully deployed.

IMPACT

A subset of Bitbucket Cloud users were unable to access their workspace. When trying to access their Bitbucket cloud repository through the website, API, or CLI, these users would have seen a 404 error message.

ROOT CAUSE

An upstream failure in a feature flagging service resulted in Bitbucket’s application logic not working correctly. This resulted in access errors for a subset of customers.

REMEDIAL ACTIONS PLAN & NEXT STEPS

We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific failure scenario wasn’t identified during testing.

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

• Fixing the root cause of the bug in our feature flag service
• Improving Bitbucket’s fallback mechanisms and handling of errors in feature flags
• Improving test coverage and war gaming failures with core dependencies.

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