Atlassian Bitbucket Incident History

1. resolvedOct 21 · 18:01 UTC

   On October 21, 2026, Bitbucket 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.

Reported by Atlassian Bitbucket on their status page.

1. postmortemOct 28 · 04:28 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

Reported by Atlassian Bitbucket on their status page.

1. ResolvedOct 15 · 12:08 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.

Reported by Atlassian Bitbucket on their status page.

1. postmortemOct 9 · 18:24 UTC

   Summary

   On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhelming our shared job scheduling platform. Automated monitoring detected the incident within three minutes. Recovery began around 03:45 UTC as engineering scaled capacity and the platform worked through the backlog, with full resolution reached in 6 hours and 25 minutes.

   IMPACT

   Most scheduled tasks stopped running at 01:00 UTC and resumed from about 03:45 UTC. Most delayed work had caught up by about 06:00 UTC, and the remaining delays had cleared by 07:25 UTC. Across affected products:

   • Recurring scheduled tasks skipped or delayed runs due during the incident; skipped runs were not automatically re-run, and tasks resumed at their next scheduled time.
   • Most one-time scheduled tasks ran late; a small number may not have run.
   • Automation rules, including scheduled rules, ran normally, except as noted below.

   Bitbucket Cloud

   Scheduled pipelines due between 01:00 and about 03:50 UTC did not run. If a scheduled pipeline did not run during the incident, you can wait for the next scheduled execution or trigger it manually. Other pipeline runs were not affected.

   Confluence

   Some calendar event reminders due between 01:00 and about 03:45 UTC were not sent.

   Forge apps

   Scheduled triggers stopped at 01:00 UTC and resumed from about 04:00 UTC; missed invocations were not replayed.

   Goals

   Start of the month email reminders to update goals could be delayed.

   Jira and Jira Service Management

   Incoming emails stayed in their mailboxes and were processed automatically after recovery. Scheduled notifications, such as filter subscriptions, were delayed. In some service projects, automation rules and notifications triggered by SLAs or time in status ran late. SLA timer data remained intact.

   Atlassian Support

   Until 07:25 UTC, issues with our support tools may have slowed some of our responses.

   Based on our investigation to date, we have not identified any loss of work items, pages, repositories, or incoming emails.

   ROOT CAUSE

   Our shared job scheduling platform operates at high scale under normal conditions. One of the platform consumers scheduled an abnormally high volume of tasks to be executed at the same time on October 1st at 01:00 UTC. This order-of-magnitude surge exceeded our architectural and scaling limits, creating a processing backlog across dependent services. Engineering manually increased capacity to handle the abnormal load, enabling the service to process the backlog and return to normal operations.

   REMEDIAL ACTIONS PLAN & NEXT STEPS

   We know that delayed and missed work affects your productivity. We are prioritizing these actions to help reduce the likelihood and impact of similar incidents:

   • Enhance workload isolation: Implement fair scheduling guardrails so volume surges from a single source do not starve or delay tasks across other products.
   • Strengthen surge controls: Add operational capabilities to quickly throttle or pause scheduled workloads from specific sources during unexpected traffic spikes.
   • Improve system scaling and recovery: Enhance platform capacity and optimize scaling processes to handle extreme demand spikes and recover more rapidly.

   We apologize to customers whose services were impacted during this incident.

   Thanks,

   Atlassian

Reported by Atlassian Bitbucket on their status page.

1. ResolvedOct 1 · 07:51 UTC

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery.Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually.

Reported by Atlassian Bitbucket on their status page.