Bitbucket Cloud - Service Disruption

What to do

• Check whether you use Bitbucket Website, API, Pipelines. 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 2h 1m it lasted.

  Anything that failed between 2026-10-15 10:07 UTC and 2026-10-15 12:08 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.

Root cause

Our teams are actively investigating the cause to mitigate the impact and restore service as quickly as possible.

Updates from Bitbucket 5

1. investigatingOct 15, 2026, 10:07 AM UTC

   We are actively investigating an issue affecting Bitbucket Cloud. Impacted users may experience connection errors, timeouts, or an inability to access the Bitbucket web interface and Pipelines. Our teams are actively investigating the cause to mitigate the impact and restore service as quickly as possible. We will provide our next update within 30 minutes, or sooner if there is a material update.

   provider

2. investigatingOct 15, 2026, 10:49 AM UTC

   We continue to actively investigate the issue impacting Bitbucket Cloud. Affected users may still experience errors, timeouts, or difficulty accessing the web interface, and Pipelines. Our teams are working through several recovery paths to mitigate the impact and restore full platform availability as quickly as possible. We will provide our next update in 60 minutes, or sooner.

   provider

3. monitoringOct 15, 2026, 11:49 AM UTC

   A fix has been implemented, and core services have recovered. The Bitbucket-pipelines is currently clearing backlogged builds and continuing to recover. We are monitoring performance closely before declaring full resolution. Next update in 60 minutes, or sooner.

   provider

4. resolvedOct 15, 2026, 12:08 PM UTC

   On October 15th, 2026, between 10:42 UTC to 11:14 UTC, some Bitbucket Cloud users may have experienced disruptions accessing the web interface and running Pipelines. The issue has now been resolved and the service is operating normally for all the customers.

   provider

5. postmortemOct 28, 2026, 4:28 AM UTC

   **SUMMARY** On October 15, 2026, between 9:38 and 10:14 UTC, Bitbucket Cloud customers were unable to access the web interface, API, and Pipelines. Git CLI operations over HTTPS or SSH were unaffected. The incident was triggered by a deployment that did not scale quickly enough to handle peak traffic, compounded by a capacity limit in our feature flag evaluation. Automated monitoring detected the issue within 2 minutes. We restored the web interface and API by rolling back to the previous deployment and scaling it up. Pipelines performance stayed degraded until 11:54 UTC, when all services were fully recovered. **ROOT CAUSE** The trigger for this incident was a hot fix designed to mitigate a previous performance issue that was deployed using an accelerated rollout. The website auto-scaling configuration had not been tuned for a recent infrastructure change and therefore was under provisioned following the hotfix deployment. During the incident the newly deployed web and API services could not absorb traffic, and began failing. After the rollback, a surge of queued events overloaded Pipelines, delaying the processing of Pipelines jobs. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident: - **Update scaling strategy:** Update scaling thresholds and concurrency settings so website capacity is added earlier under load during hotfix deployments. - **Improve progressive rollouts:** Add smaller rollout increments and soak periods, and pre-scale new deployments for expected traffic growth. - **Improve feature flag caching mechanisms:** Adjust caching timeouts and cold-cache behavior to improve feature flag cache hits. 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.