Is Bitbucket down?

Product match: components.

Read the provider’s incident report

1. 2026-10-21T18:01:48.404Z · resolved

   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.

2. 2026-10-21T17:51:45.265Z · monitoring

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

3. 2026-10-21T17:39:47.828Z · investigating

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are seeing some recovery, and will continue to share additional updates here as more information is available.

4. 2026-10-21T17:22:02.673Z · investigating

   We are actively investigating reports of a service disruption affecting Bitbucket. We will share updates here as more information is available.

Product match: components.

Read the provider’s incident report

1. 2026-10-28T04:28:09.749Z · postmortem

   **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 deplo

2. 2026-10-15T12:08:16.449Z · resolved

   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.

3. 2026-10-15T11:49:10.957Z · monitoring

   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.

4. 2026-10-15T10:49:13.915Z · investigating

   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.

5. 2026-10-15T10:07:21.658Z · investigating

   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.

Product match: components.

Read the provider’s incident report

1. 2026-10-09T18:24:31.196Z · postmortem

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

2. 2026-10-01T07:51:30.610Z · resolved

   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 th

3. 2026-10-01T07:01:47.831Z · identified

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

4. 2026-10-01T05:00:54.986Z · identified

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. 2026-10-01T04:03:57.515Z · identified

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

6. 2026-10-01T03:47:44.644Z · identified

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

7. 2026-10-01T02:55:55.733Z · investigating

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

Product match: components.

Read the provider’s incident report

1. 2026-09-16T10:15:54.693Z · resolved

   The incident affecting Bitbucket Pipelines has been fully resolved and the pipeline backlog has cleared. Pipeline scheduling and build executions are now operating normally. Note: If you have any older builds that were queued or stalled during the incident window and did not automatically resume, please re-run or trigger a new build.

2. 2026-09-16T09:32:05.551Z · monitoring

   We have identified and resolved the underlying issue causing delays and stuck builds in Bitbucket Pipelines. System recovery is in progress, and we are actively monitoring the pipeline queues to ensure builds are processing normally. Action Recommended: If you have pipelines or builds that remain queued or are stalled, we recommend rerunning them or triggering a new build. We will continue to monitor the service closely and provide a final update once stability is confirmed.

Product match: components.

Read the provider’s incident report

1. 2026-09-11T08:00:05.827Z · resolved

   On September 11 2026, between 5:30 UTC and 6:45 UTC, users experienced intermittent reliability issue that affected pull requests, commits view, related Bitbucket pages, and some Pipelines activity. Users may have also seen pages fail to load and timed out. The issue is now resolved and services have been restored to normal operation for all the affected customers.

2. 2026-09-11T07:27:51.971Z · monitoring

   We have identified the root cause of this incident and taken corrective steps to address it, with some improvements observed. We continue to monitor the situation to ensure stability.

3. 2026-09-11T06:31:57.241Z · investigating

   Bitbucket Cloud is experiencing an intermittent reliability issue affecting some users. The issue is impacting pull requests, commits view, related Bitbucket pages, and some Pipelines activity. Users may see pages fail to load, time out, or continue spinning without completing. We will provide further updates within an hour, or sooner if we have significant progress to share.

Product match: components.

Read the provider’s incident report

1. 2026-07-31T15:38:29.093Z · resolved

   On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.

2. 2026-07-31T14:28:12.007Z · monitoring

   A fix has been implemented and services are operating normally for all affected customers. We are continuing to monitor to confirm stability. We will provide a further update within 60 minutes.

3. 2026-07-31T13:09:55.197Z · monitoring

   Some customers experienced intermittent errors when accessing Bitbucket Cloud, including failures loading the site and associated impacts to Pipelines. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

Product match: components.

Read the provider’s incident report

1. 2026-06-12T00:14:47.526Z · resolved

   On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

2. 2026-06-11T23:58:04.429Z · monitoring

   The performance degradation of Bitbucket has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

3. 2026-06-11T23:21:26.867Z · identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.

4. 2026-06-11T22:48:41.022Z · investigating

   We are actively investigating reports of performance degradation affecting Bitbucket OAuth login. We will share updates here as more information is available.

Product match: components.

Read the provider’s incident report

1. 2026-05-19T19:07:06.954Z · postmortem

   ### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The

2. 2026-05-14T06:48:26.114Z · resolved

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

3. 2026-05-14T06:41:36.000Z · monitoring

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

4. 2026-05-14T06:40:48.489Z · monitoring

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

5. 2026-05-14T05:43:24.206Z · monitoring

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place.

6. 2026-05-14T05:34:15.431Z · identified

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue.

7. 2026-05-14T05:24:53.050Z · identified

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

8. 2026-05-14T05:11:18.609Z · identified

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

9. 2026-05-14T05:03:33.382Z · investigating

   We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T16:02:05.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-11-07T16:00:00.000Z to 2026-11-08T16:00:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Bitbucket feature.

The latest status observation was 2026-11-08T15:54:28.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Bitbucket in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.