Bitbucket

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup, Packages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-21 17:22 UTC

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

2. investigating 2026-10-21 17:39 UTC

   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.

3. monitoring 2026-10-21 17:51 UTC

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

4. resolved 2026-10-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.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-10-15 10:07 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...

2. investigating 2026-10-15 10:49 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...

3. monitoring 2026-10-15 11:49 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.

4. resolved 2026-10-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.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 02:55 UTC

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

2. identified 2026-10-01 03:47 UTC

   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.

3. identified 2026-10-01 04:03 UTC

   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.

4. identified 2026-10-01 05:00 UTC

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

5. identified 2026-10-01 07:01 UTC

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

6. resolved 2026-10-01 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...

7. postmortem 2026-10-09 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...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-09-16 09:32 UTC

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

2. resolved 2026-09-16 10:15 UTC

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

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Git via HTTPS, Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 06:31 UTC

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

2. monitoring 2026-09-11 07:27 UTC

   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. resolved 2026-09-11 08:00 UTC

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

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup, Packages

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-07-31 13:09 UTC

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

2. monitoring 2026-07-31 14:28 UTC

   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. resolved 2026-07-31 15:38 UTC

   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.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup, Packages

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-11 22:48 UTC

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

2. identified 2026-06-11 23:21 UTC

   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.

3. monitoring 2026-06-11 23:58 UTC

   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.

4. resolved 2026-06-12 00:14 UTC

   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.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup, Packages

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-14 05:03 UTC

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

2. identified 2026-05-14 05:11 UTC

   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.

3. identified 2026-05-14 05:24 UTC

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

4. identified 2026-05-14 05:34 UTC

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

5. monitoring 2026-05-14 05:43 UTC

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

6. monitoring 2026-05-14 06:40 UTC

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

7. monitoring 2026-05-14 06:41 UTC

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

8. resolved 2026-05-14 06:48 UTC

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

9. postmortem 2026-05-19 19:07 UTC

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

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 01:31 UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. identified 2026-05-08 02:15 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. identified 2026-05-08 03:00 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

4. identified 2026-05-08 03:00 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

5. identified 2026-05-08 04:10 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

6. identified 2026-05-08 04:10 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

7. identified 2026-05-08 04:10 UTC

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each...

8. monitoring 2026-05-08 05:53 UTC

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation...

9. monitoring 2026-05-08 08:03 UTC

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

10. monitoring 2026-05-08 11:12 UTC

    Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We...

11. resolved 2026-05-08 19:45 UTC

    On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

12. postmortem 2026-05-20 06:56 UTC

    All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-16 20:23 UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Pipelines customers. We mitigated an issue preventing new pipelines from starting, and have scaled up services are processing a backlog. Customers should see recovery shortly.

2. monitoring 2026-04-16 20:44 UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Pipelines customers. We mitigated an issue preventing new pipelines from starting, and have scaled up services are processing a backlog. Customers should see recovery shortly.

3. resolved 2026-04-16 20:44 UTC

   On April 16 at 8:00PM UTC Bitbucket Pipelines users may have experienced performance degradation running new pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-13 07:29 UTC

   Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we...

2. monitoring 2026-04-13 08:33 UTC

   Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

3. resolved 2026-04-13 10:17 UTC

   On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

4. postmortem 2026-04-21 02:32 UTC

   ### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 08:48 UTC

   We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

2. investigating 2026-03-12 09:40 UTC

   We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.

3. investigating 2026-03-12 10:52 UTC

   Our engineers are actively working to resolve the Bitbucket Cloud disruption. No new updates at this moment. We will share more details within the next hour or as soon as we more information is available.

4. investigating 2026-03-12 12:05 UTC

   Our engineers continue to work actively to identify the root cause. Meanwhile, the affected service is now stable and the error rate has decreased. We will share more details within the next hour, or sooner if more information becomes available.

5. resolved 2026-03-12 12:33 UTC

   We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-03-06 02:44 UTC

   We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

2. identified 2026-03-06 03:10 UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users will experience Bitbucket being unavailable. We'll continue to share additional updates here as more information is available, with our next update to be posted within...

3. identified 2026-03-06 04:04 UTC

   As restoration activities continue, we are now starting to see services recover for customers for Bitbucket Web and for Git HTTPS. We are continuing to work on mitigation across all remaining Bitbucket services. Our next update will be provided within one hour or if full...

4. identified 2026-03-06 05:00 UTC

   Our team has now put mitigations in place across the majority of Bitbucket services and all are now actively recovering except for Pipelines, which is still being actively investigated. We are continuing to monitor these services and we will provide further update within 1 hour...

5. resolved 2026-03-06 05:11 UTC

   On 06 March 2026 UTC, 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.

6. postmortem 2026-03-26 17:09 UTC

   ### Summary On March 6, 2026, between 02:19 UTC and 04:00 UTC, Bitbucket Cloud experienced an incident impacting the web app, API, CLI, and Pipelines operations. This was caused by the Bitbucket application hitting a regional provisioning API rate limit with our hosting...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-01-28 16:49 UTC

   We received reports of a partial service disruption affecting Bitbucket in eu-west-1 for some customers. We have identified the cause of the issue and our teams have applied mitigations and we are seeing signs of recovery. We'll continue to monitor closely to confirm stability.

2. resolved 2026-01-28 20:00 UTC

   On January 28, 2026, affected Bitbucket Cloud users in eu-west-1 may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Traffic surge or denial-of-service attack. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-01-07 16:23 UTC

   We are actively investigating reports of a partial service disruption affecting Bitbucket Cloud for some customers. We'll share updates here within the next hour or as more information is available.

2. investigating 2026-01-07 16:38 UTC

   We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.

3. monitoring 2026-01-07 17:49 UTC

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

4. resolved 2026-01-07 18:53 UTC

   On Wednesday, January 7, 2026, Bitbucket Cloud 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.

5. postmortem 2026-01-30 16:02 UTC

   ### Summary On Jan 7, 2026, between 15:28 UTC and 17:04 UTC, Atlassian customers using Bitbucket Cloud could not load the dashboard landing page. Users also faced degraded performance and intermittent failures navigating other parts of the application or using public REST APIs....

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-07 06:05 UTC

   Users of Bitbucket Cloud currently face difficulties when trying to invite new users to their workspaces. This issue is resulting in a '400 Client Error: Bad Request' message, which stems from a recent change in the invitation flow. The team is actively working on a resolution...

2. resolved 2026-01-07 06:40 UTC

   We have successfully mitigated the incident and the affected service is now fully operational. Our teams have verified that normal functionality has been restored. Thank you for your patience and understanding while we worked to resolve this issue.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Email delivery, Signup

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2025-12-27 04:42 UTC

   We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional...

2. resolved 2025-12-27 05:20 UTC

   We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.

3. postmortem 2026-01-30 04:08 UTC

   ### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-11-11 16:59 UTC

   We are actively investigating reports of performance degradation affecting Bitbucket Cloud and git services. We'll share updates here as more information is available.

2. investigating 2025-11-11 17:55 UTC

   We are continuing to investigate a service disruption affecting Bitbucket Cloud. We'll share updates in 60 minutes, or sooner as things progress.

3. investigating 2025-11-11 19:01 UTC

   Our teams are continuing to address a service disruption affecting Bitbucket Cloud. We are now seeing signs of recovery, however, affected users may experience intermittent performance degradation. We'll share additional updates here in 60 minutes, or sooner as as more...

4. monitoring 2025-11-11 19:35 UTC

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

5. resolved 2025-11-11 21:10 UTC

   On November 11th, 2025, Bitbucket Cloud 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. We are committed to transparency and will publish our public post...

6. postmortem 2025-12-05 17:36 UTC

   ## Summary On November 11, 2025, between 16:25 and 19:13 UTC, Atlassian customers were unable to access Bitbucket Cloud services. Customers experienced a period of 1 hour and 16 minutes where performance was degraded and a period of 1 hour and 32 minutes where the Bitbucket...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:56 UTC

   We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.

2. investigating 2025-10-20 08:24 UTC

   Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.

3. investigating 2025-10-20 09:23 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

4. investigating 2025-10-20 09:25 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

5. identified 2025-10-20 09:58 UTC

   We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

6. identified 2025-10-20 11:07 UTC

   We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

7. identified 2025-10-20 12:06 UTC

   Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

8. identified 2025-10-20 13:07 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

9. identified 2025-10-20 13:56 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

10. identified 2025-10-20 13:58 UTC

    Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

11. identified 2025-10-20 14:02 UTC

    We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide...

12. identified 2025-10-20 15:20 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

13. identified 2025-10-20 15:21 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

14. identified 2025-10-20 16:35 UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...

15. identified 2025-10-20 16:36 UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...

16. identified 2025-10-20 17:27 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

17. identified 2025-10-20 17:43 UTC

    We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and...

18. monitoring 2025-10-20 18:38 UTC

    There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS....

19. monitoring 2025-10-20 21:26 UTC

    Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and...

20. monitoring 2025-10-20 22:58 UTC

    Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.

21. monitoring 2025-10-21 00:03 UTC

    Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message...

22. monitoring 2025-10-21 01:07 UTC

    We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is...

23. monitoring 2025-10-21 03:24 UTC

    The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue...

24. resolved 2025-10-21 05:24 UTC

    Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the...

25. postmortem 2025-10-24 17:44 UTC

    ### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-09-16 04:00 UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Cloud Pipelines customers. We will provide more details within the next hour. We have mitigated the impact on self-hosted runners but cloud users are continuing to see delays on pipelines starting.

2. identified 2025-09-16 04:13 UTC

   We continue to work on resolving the delayed Pipelines for Atlassian Bitbucket. We have identified the root cause and expect recovery shortly.

3. monitoring 2025-09-16 04:19 UTC

   We have identified the root cause of the Pipelines delays and have mitigated the problem. We are now monitoring closely.

4. resolved 2025-09-16 04:30 UTC

   Between 03:30 UTC to 03:50 UTC, we experienced delyas in running pipelines for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-08-26 15:06 UTC

   We are currently investigating this issue.

2. investigating 2025-08-26 15:07 UTC

   Core daily job run id : scheduled__2025-08-24T04:00:00+00:00 has been running for over 30 hrs and all the downstream jobs have failed core daily Aug 25th run has not started yet.

3. resolved 2025-08-27 15:25 UTC

   issue resloved pipeline is completed.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Git via SSH, Git via HTTPS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-20 07:30 UTC

   - Bitbucket Cloud is investigating an incident affecting Git clone reliability. - The team is investigating the root cause and will update as soon as possible.

2. monitoring 2025-08-20 13:24 UTC

   A root cause has been identified and a mitigation has been implemented; we're monitoring the situation.

3. resolved 2025-08-20 15:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-19 14:27 UTC

   We are currently investigating the issue further.

2. monitoring 2025-08-19 14:41 UTC

   Website functionality has recovered and we are monitoring to ensure no further regressions

3. resolved 2025-08-19 15:22 UTC

   Bitbucket Cloud is fully recovered.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-08-05 15:03 UTC

   Today, between 13:55 and 14:35 UTC, we experienced a degradation on Bitbucket cloud, which impacted access to the website. This issue has been resolved, and services are now operating normally for all affected customers. We will monitor it closely to ensure stability

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Git via SSH, Git via HTTPS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-01 08:16 UTC

   We are investigating reports of intermittent errors for some Atlassian Bitbucket Cloud customers. We will provide more details once we identify the root cause.

2. resolved 2025-08-01 09:22 UTC

   Between 08:00UTC to 09:00UTC, we experienced degraded performance with push and clone operations for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-03 01:23 UTC

   We are aware of some customers currently experiencing issues relating to build pipelines in Bitbucket. Our team is investigating with urgency and will provide an update as soon as possible.

2. monitoring 2025-07-03 02:00 UTC

   The cause of Bitbucket pipeline issues has been connected to an infrastructure provider. We have received an update from their team that services should now be returning to normal. We are monitoring recovery at this time and will update further when we believe services are fully...

3. resolved 2025-07-03 02:12 UTC

   We have received an update that services with our infrastructure provider are fully restored. This issue is now resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-07-01 03:03 UTC

   We are aware of some users experiencing issues when attempting to load Bitbucket. Our team is investigating with urgency and will provide an update as soon as possible.

2. investigating 2025-07-01 04:03 UTC

   We are continuing to investigate issues that are being experienced by users attempting to load Bitbucket. We apologize for any inconvenience this has caused and we will provide further updates as soon as possible.

3. monitoring 2025-07-01 04:44 UTC

   Our team has identified a network configuration error that was causing the issues relating to Bitbucket being unavailable for some users. This error has now been rectified. We will continue to monitor services closely. Additional updates will continue to be shared here.

4. resolved 2025-07-01 05:12 UTC

   Between 02:36 UTC to 04:45 UTC 1 July 2025, we experienced a network configuration error for Atlassian Bitbucket, resulting in the product being unavailable for most users during this time. The issue has been resolved and the service is operating normally.

5. postmortem 2025-08-19 08:02 UTC

   **Incident Narrative** On July 1, 2025, at 02:36 UTC, a service disruption occurred leaving Atlassian customers unable to access Bitbucket. The primary issue was identified as an inconsistent network access control list \(ACL\) rule, which inadvertently blocked certain IP ranges...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-25 07:52 UTC

   We are investigating cases of degraded performance for Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

2. identified 2025-06-25 09:31 UTC

   We continue to work on resolving the degraded performance and intermittent failures (due to slow loading times) for Atlassian Bitbucket. We have identified the root cause and taken mitigations to handle the increased load and expect recovery shortly.

3. monitoring 2025-06-25 09:50 UTC

   We have identified the root cause of the degraded performance and have mitigated the problem. We are now monitoring closely.

4. resolved 2025-06-25 10:11 UTC

   Between 06:35 to 9:27 UTC, we experienced degraded performance for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-13 13:14 UTC

   We’re experiencing a recurrence of the intermittent issue affecting Bitbucket cloud. Our team is working diligently to resolve this issue, and we’ll keep you posted with further updates.

2. investigating 2025-06-13 13:59 UTC

   Our team is focused on investigating and resolving the intermittent issues with Bitbucket, and we’ll keep you posted with further updates.

3. identified 2025-06-13 14:48 UTC

   Our team continues to actively investigate and monitor the intermittent issues with Bitbucket. We are working to ensure full stability and will provide further updates as more information becomes available.

4. resolved 2025-06-13 15:52 UTC

   Between 08:15 and 14:10 UTC on June 14th, 2025, some Bitbucket Cloud customers experienced an issue loading pages and executing API requests. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The conditions that cause the issue have...

5. postmortem 2025-06-27 03:11 UTC

   ### **SUMMARY** On June 13, 2025, between 08:58 UTC and 09:34 UTC, a subset of Bitbucket website and API users experienced an error page when attempting to load the website or make API requests. This was caused by high resource usage on a core Bitbucket service’s database,...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-13 09:14 UTC

   We are currently experiencing intermittent issues with Bitbucket. Our team is working diligently to resolve this issue, and we'll keep you posted with further updates.

2. investigating 2025-06-13 09:53 UTC

   Our team is still investigating the intermittent issues with Bitbucket, and we’ll keep you posted with further updates.

3. monitoring 2025-06-13 10:31 UTC

   The issues causing intermittence in Bitbucket have been mitigated, and services are now operating normally for all affected users. We will monitor it closely to ensure stability.

4. resolved 2025-06-13 11:21 UTC

   On June 13, Bitbucket Cloud experienced intermittent availability. The issue has now been resolved, and the service is operating normally for all affected users.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-04 17:17 UTC

   We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and...

2. resolved 2025-06-04 20:59 UTC

   Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-30 13:42 UTC

   We are investigating an issue affecting Bitbucket, where steps are queued and delayed from starting. Our team is working diligently to resolve this issue and restore services as quickly as possible. We'll keep you posted with further updates.

2. identified 2025-05-30 14:08 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-05-30 14:44 UTC

   The Bitbucket issues, where steps were queued and delayed, have been mitigated. Services are now functioning normally for all affected customers. We will monitor it closely to ensure stability.

4. resolved 2025-05-30 15:00 UTC

   On May 30th, there was an issue where Bitbucket pipeline steps were queued and delayed from starting. This problem has now been resolved, and the service operates normally for all customers.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-25 23:45 UTC

   We are aware of some users experiencing issues loading Bitbucket and may be receiving errors such as '500 internal server error'. Our team is investigating this issue with urgency and will provide an update as soon as possible.

2. monitoring 2025-05-26 00:24 UTC

   Our team has mitigated the issue that caused error messages when loading Bitbucket. We are continuing to monitor at this time to ensure performance has been restored, and resolve the root cause.

3. resolved 2025-05-26 00:56 UTC

   Our team has mitigated the issue that caused error messages when loading Bitbucket. Bitbucket should now function correctly for all previously impacted users.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Pipelines

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-08 15:41 UTC

   We are currently investigating this issue.

2. identified 2025-05-08 15:45 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-05-08 15:57 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2025-05-08 18:48 UTC

   We are continuing to monitor for any further issues.

5. monitoring 2025-05-08 21:11 UTC

   We are continuing to monitor for any further issues.

6. monitoring 2025-05-08 23:25 UTC

   We are continuing to monitor for any further issues.

7. monitoring 2025-05-09 01:21 UTC

   We are continuing to monitor for any further issues.

8. monitoring 2025-05-09 04:33 UTC

   We are continuing to monitor for any further issues.

9. monitoring 2025-05-09 07:20 UTC

   We are continuing to monitor for any further issues.

10. resolved 2025-05-09 11:17 UTC

    This incident has been resolved.

11. postmortem 2025-05-19 16:42 UTC

    ### Summary On May 8, 2025, at 3:26pm UTC, Bitbucket Cloud experienced website and API latency due to an overloaded primary database. The event was caused by a backfill job running from an internal Atlassian service, which triggered an excessive call volume of expensive queries...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-05-07 20:40 UTC

   We are investigating an issue with pipeline builds not triggering that is impacting some Bitbucket customers. We will provide more details within the next hour.

2. identified 2025-05-07 21:28 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-05-07 22:00 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-05-07 22:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-21 20:10 UTC

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

2. investigating 2025-03-21 21:13 UTC

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

3. investigating 2025-03-21 22:38 UTC

   We are still investigating reports of performance degradation for some Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

4. monitoring 2025-03-21 23:54 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-03-22 00:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-20 06:11 UTC

   We are aware of an issue where users are receiving an error message when running a build. Although we believe builds are still running successfully our team is investigating with urgency and an update will be provided when available.

2. resolved 2025-03-20 07:01 UTC

   The issue where users running builds would receive an error message should now be resolved. This issue was impacting only those using self-hosted runners. It is expected that builds should have still run as expected despite this error message in the meantime.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Git via HTTPS, Webhooks, Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-19 13:13 UTC

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

2. monitoring 2025-03-19 13:36 UTC

   We have mitigated the problem and currently monitoring the results.

3. monitoring 2025-03-19 13:49 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-03-19 14:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-03-11 23:34 UTC

   Some customers are experiencing issues with our web and git operations. We are investigating.

2. investigating 2025-03-11 23:35 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-03-12 00:03 UTC

   We are monitoring an identified fix and seeing signs of recovery.

4. resolved 2025-03-12 00:28 UTC

   Between 11/Mar/25 23:02 UTC and 11/Mar/25 23:59 UTC, some Bitbucket Cloud customers experienced issues accessing our website, API, and git services. We have mitigated the problem and will take steps to avoid this issue in the future.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-02-20 11:52 UTC

   We are currently investigating an issue impacting some customers who are seeing intermittent errors accessing the Bitbucket.org website.

2. identified 2025-02-20 12:57 UTC

   We've identified an issue with some customers DNS configuration that can be blocking some Bitbucket assets. We are still investigating and will update statuspage with more information shortly.

3. identified 2025-02-20 14:05 UTC

   We've identified an issue with some customers DNS configuration not resolving Atlassian domains correctly. If you are experiencing errors accessing Bitbucket, we advise allowlisting the following domains in your DNS configuration:...

4. monitoring 2025-02-20 18:44 UTC

   We have rolled out a fix for this issue and are seeing recovery for Bitbucket users. Please refresh the page and it should fix the issue. We are currently monitoring the fix and further investigating root cause.

5. resolved 2025-02-20 22:00 UTC

   After monitoring, this incident is now resolved. If you continue to see issues, please ensure you are not using a stale / old tab and are loading a fresh version of Bitbucket in your browser.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-02-11 16:12 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.

2. resolved 2025-02-11 17:16 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...

3. postmortem 2025-03-03 17:02 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...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website, API, Git via SSH, Authentication and user management, Git via HTTPS, Webhooks, Source downloads, Pipelines, Git LFS, Email delivery, Purchasing & Licensing, Signup

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-01-21 15:30 UTC

   We are investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

2. investigating 2025-01-21 15:58 UTC

   We are still investigating an issue with Bitbucket Web and Git operations that is impacting Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.

3. investigating 2025-01-21 17:07 UTC

   We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next hour.

4. investigating 2025-01-21 17:49 UTC

   We are investigating an issue with saturated Bitbucket database that impacts all Bitbucket operations. We will provide more details within the next 30 minutes.

5. monitoring 2025-01-21 18:02 UTC

   We have identified the root cause of the database issue and have mitigated the problem. We are now monitoring closely.

6. monitoring 2025-01-21 19:28 UTC

   We have identified the root cause of the database issue that impacted Bitbucket website and Git operations; this has been mitigated now. We are experiencing Pipelines degradation that we are working to resolve.

7. monitoring 2025-01-21 20:08 UTC

   All Git, Web, API and Pipelines services are now operational. We are continuing to monitor database and Pipelines reliability.

8. resolved 2025-01-22 00:08 UTC

   Earlier we experienced database contention on high traffic tables, which resulted in website, API, and Pipelines outages. All Bitbucket services are now operational. A full post mortem will be published.

9. postmortem 2025-01-28 18:13 UTC

   ### Summary On January 21, 2025, between 14:02 and 17:49 UTC, Atlassian customers using Bitbucket Cloud were unable to use the website, API, or Pipelines. The event was triggered by write contention in a high traffic database table. The incident was detected within eight...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: API

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-12-31 11:41 UTC

   Bitbucket Cloud support has observed a small increase in errors with all Bitbucket cloud APIs, we are investigating the issue and looking into root cause.

2. monitoring 2024-12-31 13:14 UTC

   A solution has been implemented, and we're monitoring the fix to confirm resolution.

3. resolved 2025-01-02 01:40 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Git LFS

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2024-12-18 12:51 UTC

   We have identified the issue and we are working to fix the issue.

2. identified 2024-12-18 12:53 UTC

   We are continuing to work on a fix for this issue.

3. monitoring 2024-12-18 13:15 UTC

   A fix has been implemented and we are monitoring the result.

4. resolved 2024-12-18 13:35 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Authentication and user management

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-11-04 09:37 UTC

   We are investigating reports of intermittent errors for some Atlassian customers when they are trying to invite users using their admin panels (admin.atlassian.com) We will provide more details once we identify the root cause.

2. identified 2024-11-04 11:49 UTC

   We continue to work on resolving the invitation workflow in admin.atlassian.com We have identified the root cause and performed changes in the environment to mitigate the issue.

3. resolved 2024-11-04 12:02 UTC

   Between 08:00 UTC to 11:54 UTC, we experienced problems with the invitation of new users for Cloud customers on admin.atlassian.com. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Signup

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-12 02:08 UTC

   Users attempting to sign up are encountering reCaptcha errors that are preventing a successful signup.

2. monitoring 2024-09-12 02:40 UTC

   We have identified the root cause and the issue appears to be resolved.

3. resolved 2024-09-12 03:28 UTC

   This issue has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. resolved 2024-09-09 18:30 UTC

   We experienced connectivity issues with Bitbucket Cloud via SSH, which only affected customers using IP allow listing. The service was unavailable for approximately 40 minutes. However, the issue was identified and resolved, and service was restored around 19:23 UTC.

2. postmortem 2024-09-13 17:20 UTC

   ### **SUMMARY** On September 10, 2024, between 6:34 PM UTC and 7:19 PM UTC, some Atlassian customers experienced an issue preventing users from connecting to Bitbucket Cloud via SSH. The issue arose from a change in how we determined IP allow lists, which inadvertently blocked...

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-06 06:49 UTC

   We are currently experiencing performance degradation with Bitbucket Cloud. Users may encounter slower than expected response times when accessing Bitbucket Cloud website.

2. identified 2024-09-06 06:55 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-09-06 07:01 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2024-09-06 07:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Webhooks, Pipelines

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-09-05 02:19 UTC

   We are currently investigating an issue related to Connect Webhooks not being delivered. This had a downstream impact on Bitbucket Pipelines on push not being triggered. Manually triggered and scheduled pipelines are still working.

2. identified 2024-09-05 03:22 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2024-09-05 03:36 UTC

   A fix has been implemented and we are monitoring the results.

4. monitoring 2024-09-05 03:50 UTC

   We are continuing to monitor for any further issues.

5. resolved 2024-09-05 04:23 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Website

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-08-07 05:53 UTC

   We are currently experiencing an issue where Bitbucket website is slow to load. Our engineering team is actively investigating the root cause and working to resolve the issue as quickly as possible.

2. resolved 2024-08-07 06:29 UTC

   Between 2024-08-07 5.20am UTC to 2024-08-07 5.40am UTC, we experienced degraded performance with Bitbucket Website. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.

Affected: Pipelines

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-07-25 07:16 UTC

   We are currently experiencing an issue where Bitbucket Pipelines are failing to start. Our engineering team is actively investigating the root cause and working to resolve the issue as quickly as possible.

2. monitoring 2024-07-25 08:13 UTC

   We have identified the cause and have mitigated the problem. We are now monitoring this closely.

3. resolved 2024-07-25 08:44 UTC

   The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Bitbucket's status page.