Bitbucket has degraded performance

What to do

• Check whether you use Bitbucket Website, API, Git via SSH, Authentication and user management and 8 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 1h 4m it lasted.

  Anything that failed between 2025-02-11 16:12 UTC and 2025-02-11 17:16 UTC may need a replay.

• Subscribe to Bitbucket's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=bitbucket works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Bitbucket 3

1. investigatingFeb 11, 2025, 4:12 PM UTC

   We are investigating reports of intermittent errors and performance degration for some Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

   provider

2. resolvedFeb 11, 2025, 5:16 PM UTC

   Between 11/Feb/25 3:41 PM UTC and 11/Feb/25 4:26 PM UTC, some customers for Bitbucket cloud experienced degraded performance and 400 errors. We have mitigated the problem and would take steps to avoid this issue in the future. We will be publishing a public PIR on this incident in this status page, once it becomes available The issue has been resolved and all the services are operating normally.

   provider

3. postmortemMar 3, 2025, 5:02 PM UTC

   ### 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

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.