https://approjects-vendor-status-watch.static.hf.space/v/bitbucket.htmlIncidents from Bitbucket's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/s3rqnpr60vydbitbucket:2026-09-16T09:32:05.447ZWed, 16 Sep 2026 09:32:05 +0000The 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.https://stspg.io/hd61ntzs517qbitbucket:2026-09-11T06:31:57.012ZFri, 11 Sep 2026 06:31:57 +0000On 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.https://stspg.io/21tkhnmzjbxxbitbucket:2026-07-31T13:09:55.121ZFri, 31 Jul 2026 13:09:55 +0000On 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.https://stspg.io/x11jczb81t0mbitbucket:2026-06-11T22:48:40.863ZThu, 11 Jun 2026 22:48:40 +0000On 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.https://stspg.io/2p9sklcysd8rbitbucket:2026-05-14T05:03:33.069ZThu, 14 May 2026 05:03:33 +0000### 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 incident was detected within a minute by automated monitoring systems and mitigated in 56 minutes. ### **IMPACT** During the incident, customers attempting to access Atlassian Cloud products in the us-east region experienced authentication and permission failures and were unable to access serviceshttps://stspg.io/tdfn9fgfmjm1bitbucket:2026-05-08T01:31:38.240ZFri, 08 May 2026 01:31:38 +0000All 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 performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core access by 06:08. Final cleanup of backlogged processes and minor issues progressed in stages from there was completed iteratively by 19:15. ### **IMPACT** The primary infrastructure affected in this incident was the event processing pipeline in the prod-east region, which distributes events between Ahttps://stspg.io/40tfywjd7wwzbitbucket:2026-04-16T20:23:10.857ZThu, 16 Apr 2026 20:23:10 +0000On 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.https://stspg.io/1ss54766623vbitbucket:2026-04-13T07:29:45.600ZMon, 13 Apr 2026 07:29:45 +0000### 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 during the peak impact window, affecting users in the US East and EU regions. The incident was mitigated within 40 minutes through manual intervention, and full service was restored by 06:29 UTC. ### **IMPACT** * **Duration**: ~40 minutes \(05:49–06:29 UTC, April 13, 2026\) * **Affected regions**: US East and EU \(authentication infrastructure serves EU traffic from US East, with traffic primarily from EU at this time of day\). * **Affected products**: All Atlassian cloud products requiring authentication, includinghttps://stspg.io/wzlbl1hbfjw5bitbucket:2026-03-12T08:48:06.230ZThu, 12 Mar 2026 08:48:06 +0000We 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.https://stspg.io/79pys6q16t59bitbucket:2026-03-06T02:44:40.605ZFri, 06 Mar 2026 02:44:40 +0000### 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 provider, preventing application workers from handling website traffic. The incident was detected within 1 minute by automated monitoring and mitigated by scaling systems down and then back up to full capacity which put Atlassian systems into a known good state. ### **IMPACT** The incident resulted in a Bitbucket Cloud services being unavailable for 1 hour and 6 minutes on March 6, 2026 between 02:19 UTC and 03:25 UTC, followed by degraded website performance until 04:00 UTC. During this time, customers were unable to achttps://stspg.io/tpqgk9pbtfbqbitbucket:2026-01-28T16:49:04.000ZWed, 28 Jan 2026 16:49:04 +0000On 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.https://stspg.io/lczntx7b0mq9bitbucket:2026-01-07T16:23:29.492ZWed, 07 Jan 2026 16:23:29 +0000### 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. The event was caused by an unexpected load on a public API, causing long-running queries on a database which resulted in failed web and api requests. The incident was detected within three minutes by automated monitoring systems and mitigated by introducing stricter limits on the API for certain traffic, while taking manual actions on the impacted database, restoring Bitbucket to a healthy state. ### **IMPACT** Occurring on Bitbucket Cloud on Jan 7, 2026, between 15:28 UTC and 17:04 UTC, the incident caused degrhttps://stspg.io/yw62pcl9w4nqbitbucket:2026-01-07T06:05:13.882ZWed, 07 Jan 2026 06:05:13 +0000We 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.https://stspg.io/5ptmqqb7jd52bitbucket:2025-12-27T04:42:31.916ZSat, 27 Dec 2025 04:42:31 +0000### 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 certificates used by Atlassian’s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependency on monitoring path leading to service disruptions. All impacted services were fully restored by **05:20 UTC**, around **2.5 hours** after customer impact began. ### IMPACT During the impact window, customers experienced: * **Outbound product email failures** \(notifications and other product https://stspg.io/1yhf38bwm7rfbitbucket:2025-11-11T16:59:13.466ZTue, 11 Nov 2025 16:59:13 +0000## 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 Cloud website, APIs, and Git hosting were unavailable. The event was triggered by a code change that unintentionally impacted how we evaluate feature flags, impacting all customers. The incident was detected within 5 minutes by automated monitoring systems and mitigated by scaling multiple services and deploying a fix which put Atlassian systems into a known good state. The total time to full resolution was about 2 hours and 48 minutes. ### **IMPACT** The overall impact was between November 11, 2025, 16:25 UTC and Nohttps://stspg.io/k1ddqd9k8d27bitbucket:2025-10-20T07:56:11.412ZMon, 20 Oct 2025 07:56:11 +0000### 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 disruptions were triggered due to an [AWS DynamoDB outage](https://aws.amazon.com/message/101925/#:~:text=1%3A50%20PM.-,DynamoDB,-Between%2011%3A48) and further affected by subsequent failures in [AWS EC2](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) and [AWS Network Load Balancer](https://aws.amazon.com/message/101925/#:~:text=service%20disruption%20event.-,Amazon%20EC2,-Between%2011%3A48) within the us-east-1 region. The incident started at Oct 2https://stspg.io/d00sxrvhxxckbitbucket:2025-09-16T04:00:45.092ZTue, 16 Sep 2025 04:00:45 +0000Between 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.https://stspg.io/q4mhks74j8gsbitbucket:2025-08-26T15:06:05.969ZTue, 26 Aug 2025 15:06:05 +0000issue resloved pipeline is completed.https://stspg.io/f1ndq4xqbh89bitbucket:2025-08-20T07:30:28.000ZWed, 20 Aug 2025 07:30:28 +0000This incident has been resolved.https://stspg.io/cz8qywsxqcfxbitbucket:2025-08-19T14:27:32.331ZTue, 19 Aug 2025 14:27:32 +0000Bitbucket Cloud is fully recovered.