tag:jira-product-discovery.status.atlassian.com,2005:/historyJira Product Discovery Status - Incident History2024-03-29T06:53:27ZJira Product Discoverytag:jira-product-discovery.status.atlassian.com,2005:Incident/201048332024-03-06T04:51:51Z2024-03-06T04:51:51ZConfiguration data discrepancies in automation rules<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>04:51</var> UTC</small><br><strong>Resolved</strong> - All the impacted customers have been contacted and all the impacted rules have been fixed. We are now marking this issue as resolved.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>14:51</var> UTC</small><br><strong>Update</strong> - We have successfully restored the majority of automation rules that were affected, but we are currently in the process of manually fixing the remaining ones. Our support team will be contacting the customers impacted by this issue to proceed with resolving their cases.</p><p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>03:17</var> UTC</small><br><strong>Update</strong> - This issue has been mitigated, and we have restored the majority of automation rules that were affected. Those rules are working as normal, including the rules that had not been modified in the last 48 hours and the rules created after the incident. The remaining rules that haven't yet been restored are cases where customers have manually updated the rules after the incident happened.<br />We are proceeding with caution to avoid overwriting these changes.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>17:30</var> UTC</small><br><strong>Update</strong> - We are continuously working on restoring the affected automation rules configuration data. At the moment the majority of the impact has already been mitigated and the team is currently focusing on a few specific outstanding scenarios. We will continue to update you as we progress.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>15:20</var> UTC</small><br><strong>Update</strong> - We are currently working on restoring the lost automation rules configuration data. The email notifications related to the automation will be addressed upon restoring the lost data. Customers can update the configurations with the Automation rules themselves, and our fix will not override those changes. We will share further updates as we progress.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>10:54</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause and we are currently working on deploying fix to restore any lost configuration/rules. Next update will be provided in an hour.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>09:23</var> UTC</small><br><strong>Update</strong> - We continue to investigate the issue with the Automation rules losing configuration data that is impacting certain cloud products. We are actively working to resolve this issue as quickly as possible.</p><p><small>Feb <var data-var='date'>29</var>, <var data-var='time'>08:23</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with the Automation rules losing configuration data that is impacting some of the Cloud products. We are actively working to resolve this issue as quickly as possible.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/201024102024-02-29T02:53:17Z2024-02-29T03:58:09ZInvestigating 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 00:05 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:jira-product-discovery.status.atlassian.com,2005:Incident/200974642024-02-28T17:17:17Z2024-02-29T07:25:15ZIssue with Automation and Connect Apps<p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>17:17</var> UTC</small><br><strong>Resolved</strong> - On 28th Feb between 12:15 UTC and 15:20 UTC Connect apps were unable to perform user-impersonation operations and failed to execute. This had a widespread impact on all product extensions based on the Connect platform resulting in failure when performing actions on behalf of a user.<br /><br />Jira Cloud Automation rules that triggered during the outage may have failed to run. Those rules will not be able to be replayed by customers or Atlassian. Our support engineers have details regarding which customers and automation rules that were impacted. However, support engineers will not be able to replay the failed automation rules.<br /><br />We have identified the root cause of the fault and have resolved it by scaling up the infrastructure. The incident is now resolved.<br /><br />If you have questions or require support - please reach out at https://support.atlassian.com/contact/.<br /><br />We apologise to all of our developers, customers and users who were impacted during this time.<br /><br />We will release a public incident review (PIR) here in the upcoming weeks. We will detail all that we can about what caused the issue, and what we are doing to prevent it from happening again.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>16:25</var> UTC</small><br><strong>Identified</strong> - Starting from 13:15 UTC, Automation and Connect Apps affecting certain cloud products<br /><br />We have scaled up the underlying services and we're seeing an improvement in response times and success rates. We continue to investigate the root cause and will provide the next update by 18:00 UTC.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>15:12</var> UTC</small><br><strong>Update</strong> - We continue to investigate the issue with the Automation and Connect Apps affecting certain cloud products. We are actively working to resolve this issue as quickly as possible.</p><p><small>Feb <var data-var='date'>28</var>, <var data-var='time'>13:44</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Automation and Connect Apps that is impacting some Cloud products. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/199871662024-02-14T23:32:18Z2024-02-27T05:44:32ZService 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:jira-product-discovery.status.atlassian.com,2005:Incident/199320442024-02-07T17:44:38Z2024-02-07T17:44:38ZUser 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:jira-product-discovery.status.atlassian.com,2005:Incident/198915092024-02-02T08:53:24Z2024-02-02T08:53:24ZAutomation for Jira email address handling failures<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>08:53</var> UTC</small><br><strong>Resolved</strong> - Between 02:00 AM UTC to 04:13 AM UTC, we experienced email address handling failures, for email fields and smart values, which resulted in rule executions failing for some customers using Automation for Jira - JSW, JSM, JWM, JPD. The issue has been resolved and the service is operating normally.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/197969582024-01-23T00:07:36Z2024-01-23T00:07:36ZPerfomance degradation for Jira instances affecting small cohort of customers<p><small>Jan <var data-var='date'>23</var>, <var data-var='time'>00:07</var> UTC</small><br><strong>Resolved</strong> - Between 14:45 UTC to 18:25 UTC, we experienced degraded performance for Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery for a small subset of instances. The situation has stabilized, and the service is operating normally.</p><p><small>Jan <var data-var='date'>22</var>, <var data-var='time'>18:13</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent degraded performance for Jira Service Management, Jira Software, Jira Work Management, and Jira Product Discovery Cloud, affecting a small cohort of customers in a US shard. We will provide more details shortly.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/197494082024-01-18T15:55:59Z2024-01-18T15:55:59ZJira Family is unavailable across shards<p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>15:55</var> UTC</small><br><strong>Resolved</strong> - Between 06:52 UTC to 10:29 UTC, we experienced an outage for Jira Work Management, Jira Software, and Jira Product Discovery. The issue has been resolved and the service is operating normally.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>10:52</var> UTC</small><br><strong>Monitoring</strong> - Our engineering team has implemented fixes for Jira and should be recovered again. We will continue to monitor all systems.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>09:48</var> UTC</small><br><strong>Identified</strong> - We have identified the root cause of the issue and working on the fix.</p><p><small>Jan <var data-var='date'>18</var>, <var data-var='time'>08:34</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with outage that is impacting Jira Work management, Jira Software, Jira Service Management and Jira Product Discovery. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/197070362024-01-15T01:00:14Z2024-01-15T01:00:14ZHOT-106981: Outage 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:jira-product-discovery.status.atlassian.com,2005:Incident/194712262023-12-19T03:28:16Z2023-12-28T03:26:57ZAtlassian'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:jira-product-discovery.status.atlassian.com,2005:Incident/192543492023-12-05T18:33:46Z2023-12-05T18:33:46ZSome customers aren't receiving email notification when exporting users from User Management<p><small>Dec <var data-var='date'> 5</var>, <var data-var='time'>18:33</var> UTC</small><br><strong>Resolved</strong> - We have not observed any further complaints of this issue and believe the matter is resolved.</p><p><small>Dec <var data-var='date'> 4</var>, <var data-var='time'>06:07</var> UTC</small><br><strong>Monitoring</strong> - We have identified some delays in the delivery of emails which should be resolved now. Customers who retried are expected to receive the exports. We are currently monitoring the situation.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>21:11</var> UTC</small><br><strong>Update</strong> - Some end users have confirmed that they are now able to receive the email to download the export file. The issue might still persist for a small number of customers and we will keep monitoring and investigating further. However, there are indications that the frequency for the issue has been reduced. We will provide further updates early next week.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>02:47</var> UTC</small><br><strong>Update</strong> - Some end users confirmed that they are now able to receive the email to download the export file. The issue still persists for some customers and we are working with them to identify and investigate this issue further.</p><p><small>Dec <var data-var='date'> 1</var>, <var data-var='time'>01:24</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases where some customers aren't receiving email notification to download the file when exporting users from User Management. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/193161762023-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:jira-product-discovery.status.atlassian.com,2005:Incident/192395412023-11-29T03:00:00Z2023-11-29T05:59:45ZForge 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:jira-product-discovery.status.atlassian.com,2005:Incident/190070402023-11-02T23:25:00Z2023-11-03T06:27:35ZJira Automation rules failed when sending out emails<p><small>Nov <var data-var='date'> 2</var>, <var data-var='time'>23:25</var> UTC</small><br><strong>Resolved</strong> - Between 23:25 UTC and 23:46 UTC on 2nd November, we encountered a problem where automation rules in Jira that send out emails failed for certain customers. This was caused by spam-protection limits being incorrectly applied to the legitimate sending of emails. The issue has been resolved and the service is operating normally.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/189179892023-10-26T04:37:27Z2023-11-02T07:39:33ZEmail domain unverified<p><small>Oct <var data-var='date'>26</var>, <var data-var='time'>04:37</var> UTC</small><br><strong>Resolved</strong> - Between 10-23-2023 21:00 UTC and 10-26-2023 03:00 UTC, some customers received emails stating that the domain verification was failing for Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery.<br /><br />The issue has been resolved and the service is operating normally. Additional details about the issue will be shared in our Post Incident Review</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>06:02</var> UTC</small><br><strong>Update</strong> - The fix for the issue has been rolled out and is expected to be complete by 3 am UTC, 26 October. In the meantime, we have refreshed all affected domains and the service is expected to be working normally. <br /><br />We will continue to monitor this issue for 24 hours to ensure it has been resolved and will share an update once confirmed.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>01:46</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the issues with emails that have been sent out to admins stating domain verification is failing for Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery.<br /><br />A fix is currently being implemented, and we expect this issue to be resolved shortly.</p><p><small>Oct <var data-var='date'>25</var>, <var data-var='time'>00:37</var> UTC</small><br><strong>Identified</strong> - We continue to work on resolving the issues with emails that have been sent out to admins stating domain verification is failing for Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery. <br /><br />We have identified the root cause and expect recovery shortly.</p><p><small>Oct <var data-var='date'>24</var>, <var data-var='time'>23:27</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with emails that have been sent out to admins stating domain verification is failing. Affected users may see emails sent from Atlassian's default domain instead of the custom domain they have configured<br /><br />We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/185413352023-09-19T07:23:36Z2023-10-06T04:52:04ZDegraded performance in Cloud<p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>07:23</var> UTC</small><br><strong>Resolved</strong> - Between 09/18 10:47 UTC to 09/19 04:15 UTC, we experienced degraded performance for some Confluence, Jira Work Management, Jira Service Management, Jira Software, Trello, Atlassian Access, and Jira Product Discovery customers. The issue has been resolved and the service is operating normally.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>05:45</var> UTC</small><br><strong>Update</strong> - Services are confirmed to be stable. We are performing final validation checks before confirming the incident's resolution.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>04:56</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the downgraded performance and have mitigated the problem. We are monitoring this closely.</p><p><small>Sep <var data-var='date'>19</var>, <var data-var='time'>02:53</var> UTC</small><br><strong>Investigating</strong> - We are investigating cases of degraded performance for some Confluence, Jira Work Management, Jira Service Management, Jira Software, Trello, and Jira Product Discovery Cloud customers. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/185070352023-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>tag:jira-product-discovery.status.atlassian.com,2005:Incident/184906972023-09-13T19:32:01Z2023-09-22T20:03:14ZAtlassian Account login issues<p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>19:32</var> UTC</small><br><strong>Resolved</strong> - Between 12:45 UTC to 15:30 UTC, we experienced login and signup issues for Atlassian Accounts. The issue has been resolved and the service is operating normally.<br /><br />We will publish a post-incident review with the details of the incident and the actions we are taking to prevent similar problem in the future.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>17:36</var> UTC</small><br><strong>Update</strong> - We are no longer seeing occurrences of the Atlassian Accounts login errors, all clients should be able to successfully login now. We will continue to monitor.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>16:30</var> UTC</small><br><strong>Update</strong> - We can see a reduction in the Atlassian Accounts login issues after the mitigation actions were taken. We are still monitoring closely and will continue to provide updates.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>15:21</var> UTC</small><br><strong>Monitoring</strong> - We have identified the root cause of the Atlassian Accounts login issues impacting Cloud Customers and have mitigated the problem. We are now monitoring this closely.</p><p><small>Sep <var data-var='date'>13</var>, <var data-var='time'>14:08</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with Atlassian Accounts login that is impacting some Cloud customers. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/183162822023-08-30T06:17:15Z2023-09-22T06:02:25ZMultiple product logins<p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>06:17</var> UTC</small><br><strong>Resolved</strong> - Between 4:30AM UTC to 6:00AM UTC, we experienced issues for users attempting to login for Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Jira Product Discovery, Compass, and Atlassian Analytics. The issue has been resolved and the service is operating normally.</p><p><small>Aug <var data-var='date'>30</var>, <var data-var='time'>05:19</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of intermittent errors for login to Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Jira Product Discovery, Compass, and Atlassian Analytics Cloud customers. We will provide more details once we identify the root cause.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/182426332023-08-24T07:38:07Z2023-08-24T07:40:13ZMedia outage affecting multiple Atlassian services<p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>07:38</var> UTC</small><br><strong>Resolved</strong> - Between 06:22 UTC to 7:20 UTC, we experienced a problem with the service responsible for file and media services across our cloud services including Confluence, Jira Work Management, Jira Service Management, Jira Software, Bitbucket and Jira Product Discovery. The issue has been resolved by reverting a network change and service has now been restored.</p><p><small>Aug <var data-var='date'>24</var>, <var data-var='time'>07:10</var> UTC</small><br><strong>Investigating</strong> - We are investigating an issue with the attachments or media service that is impacting some Atlassian Cloud customers. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/182247752023-08-22T20:03:48Z2023-08-22T20:03:48ZElevated API Errors<p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>20:03</var> UTC</small><br><strong>Resolved</strong> - This incident has been resolved.</p><p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>19:36</var> UTC</small><br><strong>Investigating</strong> - We're experiencing an elevated level of API errors and are currently looking into the issue.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/182177422023-08-22T16:26:05Z2023-08-22T16:26:05ZSmall cohort of customers are unable to access JSW/JWM/JSM/JPD<p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>16:26</var> UTC</small><br><strong>Resolved</strong> - The small cohort of Jira Software, Jira Work Management, Jira Service Management, and Jira Product Discovery customers no longer face any issues in accessing their Atlassian Sites. We are implementing measures to prevent similar issues from occurring in the future.</p><p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>06:53</var> UTC</small><br><strong>Monitoring</strong> - The small cohort of Jira Software, Jira Work Management, Jira Service Management and Jira Product Discovery customers no longer face any issues in accessing their Atlassian Sites.</p><p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>05:39</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of Jira Software, Jira Work Management, Jira Service Management and Jira Product Discovery being unavailable for a small cohort of customers.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/182161952023-08-22T01:08:35Z2023-08-22T01:08:35ZAtlassian services unable to scale<p><small>Aug <var data-var='date'>22</var>, <var data-var='time'>01:08</var> UTC</small><br><strong>Resolved</strong> - We have resolved a case of degraded performance for Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, and Compass Cloud customers. We will provide more details within the next hour.</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/181545202023-08-15T18:13:47Z2023-08-15T18:13:47ZSlowness and intermittent failure while creating new Cloud instances<p><small>Aug <var data-var='date'>15</var>, <var data-var='time'>18:13</var> UTC</small><br><strong>Resolved</strong> - We are pleased to report that the issues concerning slowness and intermittent errors while creating new Cloud instances for Jira Service Management, Jira Software, Jira Work Management, and Jira Product Discovery in the Europe region have now been resolved. We have identified and rectified the root cause, ensuring smooth operations hereafter.</p><p><small>Aug <var data-var='date'>15</var>, <var data-var='time'>17:33</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of slowness and intermittent errors while creating new Cloud instances for Jira Service Management, Jira Software, Jira Work Management, and Jira Product Discovery in Europe region. No impact to existing Cloud instances was observed. We will provide more details as we identify the root cause and fix the issue</p>tag:jira-product-discovery.status.atlassian.com,2005:Incident/180720812023-08-07T09:54:26Z2023-08-07T09:54:26ZBilling preview in admin hub not showing all products for some customers<p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>09:54</var> UTC</small><br><strong>Resolved</strong> - Between 04/08 to 07/08, we experienced Issues for Billing preview for Confluence, Jira Work Management, Jira Service Management, Jira Software, and Jira Product Discovery. The issue has been resolved and the service is operating normally.<br /><br />Users can now correctly browse their billing preview and take action</p><p><small>Aug <var data-var='date'> 7</var>, <var data-var='time'>06:14</var> UTC</small><br><strong>Investigating</strong> - We are investigating reports of Billing preview not being displayed for some products for some customers. We will provide more details once we identify the root cause.</p>