tag:bitbucket.statuspage.io,2005:/historyAtlassian Bitbucket Status - Incident History2024-03-19T08:48:46ZAtlassian Bitbuckettag:bitbucket.statuspage.io,2005:Incident/202189962024-03-11T21:56:34Z2024-03-11T21:56:34ZBitbucket Cloud service degradation<p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>21:56</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>21:43</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>21:28</var> UTC</small><br><strong>Update</strong> - Identified degraded performance and increased error rate, the team is currently working to mitigate.</p><p><small>Mar <var data-var='date'>11</var>, <var data-var='time'>21:12</var> UTC</small><br><strong>Investigating</strong> - We're investigating an issue with high resource utilisation on one of our databases, customers may experience a degradation in performance while we work on a resolution.</p>tag:bitbucket.statuspage.io,2005:Incident/201024192024-02-29T02:53:17Z2024-02-29T02:53:17ZInvestigating new product purchasing<p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>02:53</var> UTC</small><br><strong>Resolved</strong> - Between 28th Feb 2024 23:15 UTC to 29th Feb 2024 02:41 UTC, we experienced issue with new product purchasing for all products. All new sign up products have been successfully provision and confirmed issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>01:27</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with new product purchasing that is impacting for all products. Customers adding new cloud products may have experienced a long waiting page or an error page after attempting to add a product. We have mitigated the root cause and are working to resolve impact for customers who attempted to add a product during the impact period. We will provide more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/200486792024-02-22T17:45:44Z2024-03-11T18:02:56ZPipelines stuck in pending state<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>17:45</var> UTC</small><br><strong>Resolved</strong> - Services have recovered and are operational</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>17:24</var> UTC</small><br><strong>Monitoring</strong> - Services are in the process of recovering while we continue to monitor</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>16:39</var> UTC</small><br><strong>Identified</strong> - The issue has been identified. We are working towards resolution.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>15:55</var> UTC</small><br><strong>Investigating</strong> - We are still receiving some reports of Pipelines queueing or delays, requiring further investigation</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>15:20</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>15:16</var> UTC</small><br><strong>Identified</strong> - The issue has been identified and a fix is being implemented.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>14:45</var> UTC</small><br><strong>Investigating</strong> - We are currently investigating an issue preventing Bitbucket Pipelines from starting for some customers.</p>tag:bitbucket.statuspage.io,2005:Incident/200457682024-02-22T13:57:05Z2024-03-12T17:58:41ZBitbucket Cloud website performance degraded<p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>13:57</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>13:39</var> UTC</small><br><strong>Monitoring</strong> - A fix has been implemented and we are monitoring the results.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>11:56</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate the cause of the degraded performance.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>10:13</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>10:08</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate the cause of the degraded performance.</p><p><small>Feb <var data-var='date'>22</var>, <var data-var='time'>08:37</var> UTC</small><br><strong>Investigating</strong> - We are aware of an incident impacting the performance of the Bitbucket Cloud website. An update will be provided soon.</p>tag:bitbucket.statuspage.io,2005:Incident/200347952024-02-21T04:57:17Z2024-02-21T04:57:17ZIncreased authentication errors across multiple products<p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>04:57</var> UTC</small><br><strong>Resolved</strong> - Between 2:30 UTC to 4:26 UTC, we experienced increased authentication errors for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>04:22</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the authentication errors and have mitigated the problem. We are now monitoring this closely and will provide further updates within the hour.</p><p><small>Feb <var data-var='date'>21</var>, <var data-var='time'>03:41</var> UTC</small><br><strong>Investigating</strong> - We are investigating authentication issues impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, and Atlassian Bitbucket Cloud customers. We will provide more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/200230722024-02-19T20:25:00Z2024-02-19T20:25:00ZBitbucket Pipelines - Unable to pull image errors<p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>20:25</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved and the service is operating normally.<br /><br />Bitbucket Cloud customers experienced failures when running Pipelines builds on self-hosted runners. Customers received error messages noting "Unable to pull image".</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>19:52</var> UTC</small><br><strong>Monitoring</strong> - The cause of the issue has been identified and remediated. We are continuing to monitor the issue to ensure that impact has been resolved.</p><p><small>Feb <var data-var='date'>19</var>, <var data-var='time'>19:14</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Bitbucket Pipelines builds, some customers may see errors and failed builds when using self-hosted runners.<br /><br />We will update with more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/198189452024-02-17T20:42:52Z2024-02-17T20:42:52ZScheduled Ongoing Maintenance<p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>20:42</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Feb <var data-var='date'>17</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>23:12</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'>16</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>22:11</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'>15</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>22:54</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'>13</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>23:27</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'>10</var>, <var data-var='time'>00:07</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 9</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>23:40</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 8</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>23:55</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>00:18</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>22:52</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>17:06</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>22:00</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>23:05</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Feb <var data-var='date'> 1</var>, <var data-var='time'>17:01</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>21:06</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>17:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>30</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>29</var>, <var data-var='time'>17:02</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>21:01</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>17:11</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>21:31</var> UTC</small><br><strong>Update</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>21:00</var> UTC</small><br><strong>Scheduled</strong> - We will be undergoing scheduled maintenance during this time.</p><p><small>Jan <var data-var='date'>25</var>, <var data-var='time'>17:04</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Jan <var data-var='date'>24</var>, <var data-var='time'>15:29</var> UTC</small><br><strong>Scheduled</strong> - Bitbucket Cloud is currently conducting scheduled maintenance that may impact write access to your repositories between 1700UTC and 2100UTC. This scheduled maintenance will be ongoing from the week of January 22, 2024 through the end of March 2024. If you receive an error and are unable to write to your repositories, try again after 5-10 min. This could impact your repository for up to 30 minutes but on average, should not last more than a few minutes.<br /><br />For more details please refer to <a href="https://community.atlassian.com/t5/Bitbucket-articles/Announcing-upcoming-required-maintenance-for-Bitbucket-Cloud/ba-p/2578363#M2162">Community post</a></p>tag:bitbucket.statuspage.io,2005:Incident/199871742024-02-14T23:32:18Z2024-02-27T05:24:03ZService Disruptions Affecting Atlassian Products<p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>23:32</var> UTC</small><br><strong>Resolved</strong> - We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the services are operating normally.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:55</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>22:31</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.</p><p><small>Feb <var data-var='date'>14</var>, <var data-var='time'>21:57</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.</p>tag:bitbucket.statuspage.io,2005:Incident/199320472024-02-07T17:44:39Z2024-02-07T17:44:39ZUser searches failing<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:44</var> UTC</small><br><strong>Resolved</strong> - Between 15:40 UTC to 15:57 UTC customers experienced intermittent failures when searching for users in Atlassian cloud services: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>17:05</var> UTC</small><br><strong>Monitoring</strong> - We have mitigated the problem. We are now monitoring closely.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>16:40</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with our user search service that is impacting Atlassian cloud service: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. We will provide more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/199179602024-02-06T02:40:54Z2024-02-06T02:40:54ZDrop in the success rate of Forge hosted storage API calls<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>02:40</var> UTC</small><br><strong>Resolved</strong> - We identified a problem with the Forge hosted storage API calls, which resulted in a drop in invocation success rates in the developer console. The impact of this incident has been mitigated and our monitoring tools confirm that the success-rate is back to the pre-incident behaviour. It impacted 16 apps according to our logs, where these apps saw a reduced success rate of storage.get API calls, as listed in https://developer.atlassian.com/platform/forge/runtime-reference/storage-api-basic.<br /><br />As part of Forge's preparation to support Data Residency, Forge hosted storage has been undergoing a platform and data migration for storing app data. As part of this migration we do comparison checks for data consistency between the old and new platform. The previous incident earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl, had put the data on the new platform out of sync and so comparisons of the data from the old and new platform started showing failures and the migration logic retries on failures to test for consistency issues. This retry behaviour increased latency of these requests which led to 16 apps receiving an increased number of 504 timeout errors. <br /><br />Checking synchronously was identified by the team as a bug and should have been async. Once the root cause was identified we moved our backing platform rollout to a previous stage. The rollout is split into several stages. The issues we were having were on our blocking stage where we make calls to both the old and new platform and wait for both to complete so we can test any performance issues in the new platform before using it as our source of truth. It was in this blocking stage where we had a bug that included waiting on comparisons when it should've been async.<br /><br />To recover, we reverted back to our shadow mode stage. In this stage, all operations to the new platform are asynchronous, including comparisons that were blocking in the other stage and resulted in timeout issues and 504 errors being sent to apps. This is the state that Forge hosted storage has been in for several months without any problems.<br /><br />Here is the timeline of the impact:<br />- On 2024-02-05 at 06:42 PM UTC, impact started with comparisons start happening on out of sync data in blocking mode<br />- On 2024-02-05 at 08:57 PM UTC, impact was detected to API by our monitoring systems<br />- On 2024-02-05 at 11:34 PM UTC, rollout to new platform was reverted to known stable state and impact ended<br /><br />We will release a public incident review, PIR, here in the upcoming weeks for this and the incident that happened earlier, https://developer.status.atlassian.com/incidents/9q71ytpjhbtl. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.<br /><br />We apologise for any inconveniences this may have caused our customers and the developer community and committed to preventing further issues with our hosted storage capability.</p>tag:bitbucket.statuspage.io,2005:Incident/199102892024-02-05T08:15:34Z2024-02-05T08:15:34ZNot able to access Bitbucket Pipelines UI<p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>08:15</var> UTC</small><br><strong>Resolved</strong> - We experienced problems not being able to access Bitbucket Pipelines UI. The issue has been resolved and the service is operating normally.</p><p><small>Feb <var data-var='date'> 5</var>, <var data-var='time'>08:01</var> UTC</small><br><strong>Identified</strong> - We are investigating cases of not being able to access Bitbucket Pipelines page. We will provide more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/198729872024-01-31T06:03:12Z2024-01-31T06:03:12ZPerformance degradation for Forge app invocations<p><small>Jan <var data-var='date'>31</var>, <var data-var='time'>06:03</var> UTC</small><br><strong>Resolved</strong> - At around 4am UTC, about 40 percent of Forge app invocations experienced high latency, with a portion of the requests failing, during a 15 minute time window.<br /><br />The scaling of the instances was misconfigured following a new deployment of the service, which needed manual intervention which took a few minutes to resolve the issue.<br /><br />Timeline:<br />- 2024-01-31 04:00 UTC: impact started<br />- 2024-01-31 04:03 UTC: incident detected<br />- 2024-01-31 04:15 UTC: the incident was resolved and the impact ended<br /><br />This issue is now resolved and Forge is fully operational. We apologize for any inconveniences this may have caused to our customers, partners, and our developer community.</p>tag:bitbucket.statuspage.io,2005:Incident/197070342024-01-15T01:00:14Z2024-01-29T00:14:37ZOutage in Atlassian Intelligence functionality in multiple products<p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>01:00</var> UTC</small><br><strong>Resolved</strong> - Between 23:45 UTC to 00:30 UTC, we experienced an outage in some Atlassian Intelligence features for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, Atlas, and Compass. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>00:47</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the increased errors and have mitigated the problem. We are now monitoring closely.</p><p><small>Jan <var data-var='date'>15</var>, <var data-var='time'>00:31</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Atlassian Intelligence that is impacting some Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.</p>tag:bitbucket.statuspage.io,2005:Incident/194712302023-12-19T03:28:15Z2023-12-28T03:17:19ZAtlassian's cross product user search service is currently degraded.<p><small>Dec <var data-var='date'>19</var>, <var data-var='time'>03:28</var> UTC</small><br><strong>Resolved</strong> - It has been resolved. Atlassian's cross product user search is working.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:23</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is currently healthy. Searches for users within Atlassian products are working as expected.<br />We are in the process of investigating the root cause of this incident.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:06</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:02</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>16:01</var> UTC</small><br><strong>Update</strong> - Atlassian's cross product user search service is recovering. Searches for users within Atlassian products are returning to normal.</p><p><small>Dec <var data-var='date'>18</var>, <var data-var='time'>15:04</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors for <SOME/ALL> Atlassian, Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details once we identify the root cause.</p>tag:bitbucket.statuspage.io,2005:Incident/190616532023-12-09T23:27:01Z2023-12-09T23:27:11ZBitbucket Database Maintenance<p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>23:27</var> UTC</small><br><strong>Completed</strong> - The scheduled maintenance has been completed.</p><p><small>Dec <var data-var='date'> 9</var>, <var data-var='time'>18:00</var> UTC</small><br><strong>In progress</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>19:21</var> UTC</small><br><strong>Scheduled</strong> - The Bitbucket team will be performing maintenance on our database infrastructure on Saturday December 9th at 18:00 UTC. This maintenance will require up to 5 hours of downtime on all Bitbucket Cloud Services, including the Bitbucket website, Git operations via SSH and HTTPS, API requests, and Bitbucket Pipelines. All services are expected to be back to normal after this maintenance is complete.</p>tag:bitbucket.statuspage.io,2005:Incident/193161732023-12-04T17:15:04Z2023-12-04T17:15:04ZEgress connectivity timing out<p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>17:15</var> UTC</small><br><strong>Resolved</strong> - The systems are stable after the fix and monitoring for a specified duration</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:59</var> UTC</small><br><strong>Monitoring</strong> - The issue was identified and a fix implemented. We are monitoring currently.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:54</var> UTC</small><br><strong>Update</strong> - We are currently investigating an incident that result in outbound connections from Atlassian cloud in us-east-1 intermittently timing out. This affects Jira, Trello, Confluence, Ecosystem products. The features affected for these products are those that require opening a connection from Atlassian Cloud to public endpoints on the Internet</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:43</var> UTC</small><br><strong>Update</strong> - Including Atlassian Developer</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>16:33</var> UTC</small><br><strong>Identified</strong> - We are currently investigating an incident that result in connection time outs on service egress proxy. This affects Jira, JSM, Confluence, BitBucket, Trello, Ecosystem products. The features affected for these products are those that require a connection to service egress.</p>tag:bitbucket.statuspage.io,2005:Incident/192396322023-11-29T03:00:00Z2023-11-29T06:21:40ZForge Function Invocations outage impacting Smartlinks<p><small>Nov <var data-var='date'>29</var>, <var data-var='time'>03:00</var> UTC</small><br><strong>Resolved</strong> - Forge Invocations had an 8 minute outage between 2023-11-29 03:05:13 UTC to 2023-11-29 03:13:27 UTC resulting in Smart Links failing. This service has recovered post this time period.</p>tag:bitbucket.statuspage.io,2005:Incident/190583682023-11-08T15:46:13Z2023-11-09T09:22:37ZAtlassian Intelligence functionally completely down<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>15:46</var> UTC</small><br><strong>Resolved</strong> - Between 13:40 UTC to 15:30 UTC, we experienced an outage in all Atlassian Intelligence features for Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas. The issue has been resolved and the service is operating normally.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>14:57</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the outage affecting Atlassian Intelligence related features for Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas. We have identified the root cause and expect recovery shortly.</p>tag:bitbucket.statuspage.io,2005:Incident/190533252023-11-08T06:19:39Z2023-11-08T06:19:40ZBitbucket Cloud operations are experiencing an outage<p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>06:19</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>05:42</var> UTC</small><br><strong>Monitoring</strong> - The increased error rate has resolved and operations have returned to normal, we're investigating the root cause and monitoring the situation.</p><p><small>Nov <var data-var='date'> 8</var>, <var data-var='time'>05:26</var> UTC</small><br><strong>Investigating</strong> - We've been alerted to an increased error rate across API, GIT, Pipelines and other operations, we're investigating the issue and will provide an update soon.</p>tag:bitbucket.statuspage.io,2005:Incident/190063602023-11-03T05:18:47Z2023-11-03T05:18:47ZPipeline and runner orchestration degraded<p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>05:18</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>03:35</var> UTC</small><br><strong>Update</strong> - Incident resolved.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>03:34</var> UTC</small><br><strong>Update</strong> - The rollback has been completed and error rate has decreased, we will investigate root cause.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>03:19</var> UTC</small><br><strong>Monitoring</strong> - The Pipelines team have rolled back a recent set of changes, we are observing a recovery in pipelines and agent actions, we're now monitoring the situation during recovery.</p><p><small>Nov <var data-var='date'> 3</var>, <var data-var='time'>03:05</var> UTC</small><br><strong>Investigating</strong> - Steps on runners are not able to execute due to an issue with one of our services, this prevents the executions of builds on runners and lifecycle management of runners. We're attempting to isolate the issue and revert recent changes to recover.</p>tag:bitbucket.statuspage.io,2005:Incident/189317332023-10-26T08:56:59Z2023-10-26T08:56:59ZIntermittent failures running Bitbucket Pipelines builds<p><small>Oct <var data-var='date'>26</var>, <var data-var='time'>08:56</var> UTC</small><br><strong>Resolved</strong> - Between 19:28 UTC to 20:30 UTC, some customers experienced intermittent errors running Pipelines on Atlassian Bitbucket due to a failure with our container registry service. The issue has been resolved and the service is operating normally.</p><p><small>Oct <var data-var='date'>26</var>, <var data-var='time'>07:45</var> UTC</small><br><strong>Monitoring</strong> - We are investigating reports of intermittent Pipelines errors for some Atlassian Bitbucket Cloud customers. We will provide more details once we identify the root cause.</p>tag:bitbucket.statuspage.io,2005:Incident/189279682023-10-25T22:52:53Z2023-10-25T22:52:54ZBitbucket Pipelines - Unable to pull image errors<p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>22:52</var> UTC</small><br><strong>Resolved</strong> - Between 20:45 UTC to 21:30 UTC, we experienced issues with our artifactory service supporting Atlassian Bitbucket Pipelines, causing some pipelines to fail. The issue has been resolved and the service is operating normally. <br /><br />We advise any customers that had experience pipeline failures at this time to re-run the entire pipeline.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>21:49</var> UTC</small><br><strong>Monitoring</strong> - We recently identified an issue with one of the services supporting bitbucket pipelines, we have failed over and no long seeing any impact to customers. Advising any customers that had failures occur to rerun their entire pipeline.<br /><br />We are continuing to monitor.</p>tag:bitbucket.statuspage.io,2005:Incident/188609762023-10-20T04:34:30Z2023-10-25T14:03:53ZDegraded experience for Atlassian Intelligence features<p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>04:34</var> UTC</small><br><strong>Resolved</strong> - Between 23:51 19th Oct, 2023 UTC to 03:30 20th Oct, 2023 UTC, we experienced a service degradation of Atlassian Intelligence capabilities in Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas. <br />The issue has been resolved and the service is operating normally.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>03:42</var> UTC</small><br><strong>Monitoring</strong> - OpenAI has mitigated the problem and we are currently not seeing any errors w.r.t. Atlassian Intelligence capabilities. <br />We are now monitoring closely.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>02:38</var> UTC</small><br><strong>Update</strong> - OpenAI team has applied a fix and we are seeing a reduction in the failure rate for Atlassian Intelligence capabilities in Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas. <br /><br />We continue to closely monitor our systems and coordinating with OpenAI for a faster recovery of Atlassian Intelligence capabilities.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>02:13</var> UTC</small><br><strong>Update</strong> - We continue to work on resolving the failures in Atlassian Intelligence capabilities for Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas. <br /><br />The cause of incident is increased API failure rate from OpenAI, we are in touch with them to understand the time to recover.</p><p><small>Oct <var data-var='date'>20</var>, <var data-var='time'>01:49</var> UTC</small><br><strong>Identified</strong> - We are investigating reports of intermittent errors in Atlassian Intelligence capabilities for some Confluence, Jira Service Management, Jira Software, Trello, Atlassian Bitbucket, and Atlas Cloud customers. We will provide more details once we identify the root cause.</p>tag:bitbucket.statuspage.io,2005:Incident/185995232023-09-25T11:36:03Z2023-10-04T00:50:44ZBitbucket has an increased error rate<p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>11:36</var> UTC</small><br><strong>Resolved</strong> - The issue has been resolved and all services are operating normally.</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>10:42</var> UTC</small><br><strong>Update</strong> - We've identified the cause of the issue and remediated the impact, the Bitbucket Cloud team will continue to monitor the issue now the impact has been resolved.</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>10:39</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Sep <var data-var='date'>25</var>, <var data-var='time'>10:27</var> UTC</small><br><strong>Investigating</strong> - The bitbucket team has detected an issue with multiple bitbucket cloud services, we're currently investigating the issue and will provide an update shortly.</p>tag:bitbucket.statuspage.io,2005:Incident/185070402023-09-15T05:19:25Z2023-09-15T05:19:25ZInfrastructure outage affecting attachments and Bitbucket Pipelines in all regions<p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>05:19</var> UTC</small><br><strong>Resolved</strong> - Between 04:00 UTC to 05:00 UTC, we experienced a partial outage for Bitbucket Pipelines, issues viewing in-product attachments; and degraded performance across all products. The issue has been resolved and all services are operating normally.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:47</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause, initiated mitigation actions, and are seeing a reduction in errors when scaling up in response to customer traffic. We are still monitoring closely and will continue to provide updates.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:12</var> UTC</small><br><strong>Update</strong> - A major infrastructure outage is affecting our ability to scale up in response to customer traffic. We are pre-emptively disabling any downscaling to minimize future impact. This is primarily affecting Bitbucket Pipelines, and attachment storage for all products. All regions are affected. We will provide more details in the next hour.</p><p><small>Sep <var data-var='date'>15</var>, <var data-var='time'>04:02</var> UTC</small><br><strong>Identified</strong> - A major infrastructure outage is affecting our ability to scale up in response to customer traffic. We are pre-emptively disabling any downscaling to minimize future impact. This is primarily affecting Bitbucket Pipelines, and attachment storage for all products. All regions are affected. We will provide more details in the next hour.</p>