May <var data-var='date'>14</var>, <var data-var='time'>09:41</var> UTC Resolved - This incident has been resolved. During the incident window, some customers using Atlassian Assist experienced excessive notifications as our team replayed delayed events caused by this prior incident: https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7 Our engineering team identified and addressed the issue. All services have fully recovered, and notification delivery is operating normally. No data loss occurred as a result of this incident. We apologize for the disruption and any confusion caused by the excessive notifications. May <var data-var='date'>14</var>, <var data-var='time'>03:52</var> UTC Update - Some of the users continue to experience an excessive number of notifications arriving from JSM (Assist) as our team replays delayed events experienced in this prior incident: https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7 At this time we expect that these notifications will be arriving for the next few hours, until the recovery of the delayed events are processed which is taking longer than expected (ETA approx. 4 hours). We will provide further updates within 6 hours or sooner if the recovery occurs. May <var data-var='date'>14</var>, <var data-var='time'>01:15</var> UTC Investigating - We are aware that some users are experiencing an excessive number of notifications arriving from Jira Service Management (Assist) as our team replays delayed events experienced in this prior incident: https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7 At this time we expect that the vast majority of these notifications will be arriving within the next two hours. We will provide further update at that time or sooner if further information becomes available.

Excessive notifications being received by some Jira Service Management users

May <var data-var='date'>14</var>, <var data-var='time'>06:48</var> UTC Resolved - All products and services impacted by this incident should now be fully recovered, and this incident is resolved. May <var data-var='date'>14</var>, <var data-var='time'>06:41</var> UTC Update - We are approaching full system recovery at this time, and are performing final confirmations that services are restored. May <var data-var='date'>14</var>, <var data-var='time'>06:40</var> UTC Update - We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed. May <var data-var='date'>14</var>, <var data-var='time'>05:43</var> UTC Monitoring - Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken place. May <var data-var='date'>14</var>, <var data-var='time'>05:34</var> UTC Update - Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update within an hour as we are able to progress mitigating this issue. May <var data-var='date'>14</var>, <var data-var='time'>05:24</var> UTC Update - It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available. May <var data-var='date'>14</var>, <var data-var='time'>05:11</var> UTC Identified - Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available. May <var data-var='date'>14</var>, <var data-var='time'>05:03</var> UTC Investigating - We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is available.

Users experiencing issues accessing multiple Atlassian products

May <var data-var='date'>13</var>, <var data-var='time'>09:59</var> UTC Resolved - We appreciate your patience during this incident. Our services are now fully operational and all delayed automation events have been processed. May <var data-var='date'>13</var>, <var data-var='time'>08:42</var> UTC Update - Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed. May <var data-var='date'>13</var>, <var data-var='time'>07:42</var> UTC Update - While new automation events are being processed correctly, our teams continue working through the processing of historical events that were delayed by this incident. We will provide an update on the progress within one hour. May <var data-var='date'>13</var>, <var data-var='time'>06:38</var> UTC Update - Our team has been able to confirm that new automation events should now be processed correctly. We are working through the processing of historical events that have been delayed by this incident and will provide an update on progress within one hour. May <var data-var='date'>13</var>, <var data-var='time'>05:38</var> UTC Update - The root cause of this issue has now been confirmed by our incident response team. We are working urgently to bring back normal automation processing to impacted users, and process historical events that were delayed by the impact of the incident. We will provide further update within one hour or sooner if available. May <var data-var='date'>13</var>, <var data-var='time'>02:41</var> UTC Identified - Our team has identified a likely root cause of this issue and is actively working on a fix. At this point in time the required steps to mitigate this issue are expected to take approximately three hours. We will provide further update within three hours or sooner if further information is available prior to that time. May <var data-var='date'>13</var>, <var data-var='time'>01:37</var> UTC Investigating - At this time it is expected that impacted users may be experiencing delays for multiple hours on their automation events. Our team is continuing to investigate this issue with urgency. We will provide further update within an hour.

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

May <var data-var='date'> 8</var>, <var data-var='time'>19:45</var> UTC Resolved - 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. May <var data-var='date'> 8</var>, <var data-var='time'>11:12</var> UTC Update - 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 apologise for the disruption and thank you for your patience. May <var data-var='date'> 8</var>, <var data-var='time'>08:03</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>05:53</var> UTC Monitoring - 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 triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Update - 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 product page. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available. May <var data-var='date'> 8</var>, <var data-var='time'>04:10</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>03:00</var> UTC Update - Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available. May <var data-var='date'> 8</var>, <var data-var='time'>03:00</var> UTC Update - 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. May <var data-var='date'> 8</var>, <var data-var='time'>02:15</var> UTC Identified - 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. May <var data-var='date'> 8</var>, <var data-var='time'>01:31</var> UTC Investigating - We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

Multiple Atlassian services are experiencing issues

May <var data-var='date'> 6</var>, <var data-var='time'>11:17</var> UTC Resolved - The issue causing failures in the lookup objects within JSM Automation has been resolved. A fix was implemented to address the problem and the service is now operating normally for all affected customers. May <var data-var='date'> 6</var>, <var data-var='time'>10:18</var> UTC Monitoring - A fix has been implemented to address the failures observed in the lookup objects within JSM Automation. We are actively monitoring the situation to ensure stability. We will share the final update within next 1 hour. May <var data-var='date'> 6</var>, <var data-var='time'>09:35</var> UTC Investigating - We are investigating reports of lookup objects in Automation for Jira Service Management are not functioning as expected. Our engineering teams are actively investigating and working to resolve the issue. We will provide further updates in next 1 hour.

Lookup Objects in Automation for Jira Service Management are not functioning

May <var data-var='date'> 2</var>, <var data-var='time'>02:48</var> UTC Resolved - The Jira Work Item View experience has been restored to normal service. Our teams are continuing to investigate the root cause affecting this issue. We will provide more details once we identify the root cause May <var data-var='date'> 2</var>, <var data-var='time'>02:00</var> UTC Update - We are actively investigating reports of a service disruption affecting the Work Item viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available. May <var data-var='date'> 2</var>, <var data-var='time'>01:38</var> UTC Update - We are actively investigating reports of a service disruption affecting the issue viewing experience in Jira. This is also impacting the accessibility of support tickets. We will share updates here as more information becomes available. May <var data-var='date'> 2</var>, <var data-var='time'>00:55</var> UTC Investigating - We are investigating an incident affecting Jira Software (viewBoard, viewIssue, createIssue). Our team is working to identify the cause and restore service to normal levels. We will provide the next update within 60 minutes.

The Work Item view experience of Jira is restored

Apr <var data-var='date'>14</var>, <var data-var='time'>16:11</var> UTC Resolved - On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers. Apr <var data-var='date'>14</var>, <var data-var='time'>15:46</var> UTC Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability. Apr <var data-var='date'>14</var>, <var data-var='time'>14:11</var> UTC Identified - We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available. Apr <var data-var='date'>14</var>, <var data-var='time'>12:25</var> UTC Update - We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more. Apr <var data-var='date'>14</var>, <var data-var='time'>12:12</var> UTC Investigating - We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more information becomes available.

Disrupted Rovo availability for Automation rules

Apr <var data-var='date'>13</var>, <var data-var='time'>10:17</var> UTC Resolved - 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. Apr <var data-var='date'>13</var>, <var data-var='time'>08:33</var> UTC Update - 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. Apr <var data-var='date'>13</var>, <var data-var='time'>07:29</var> UTC Monitoring - 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 will provide an update within 1 hour.

Users experiencing issues with login across Atlassian products

Apr <var data-var='date'> 8</var>, <var data-var='time'>11:43</var> UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Apr <var data-var='date'> 8</var>, <var data-var='time'>09:03</var> UTC Monitoring - The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability. Apr <var data-var='date'> 8</var>, <var data-var='time'>09:03</var> UTC Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>08:33</var> UTC Update - We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update this page as performance fully recovers. Apr <var data-var='date'> 8</var>, <var data-var='time'>08:33</var> UTC Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>07:40</var> UTC Update - Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable. Apr <var data-var='date'> 8</var>, <var data-var='time'>07:40</var> UTC Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>06:25</var> UTC Identified - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution. We will provide further update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>06:25</var> UTC Update - The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>06:25</var> UTC Update - Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour. Apr <var data-var='date'> 8</var>, <var data-var='time'>06:24</var> UTC Investigating - Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

Multiple products impacted by search failures

Mar <var data-var='date'>19</var>, <var data-var='time'>04:08</var> UTC Resolved - The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner. Mar <var data-var='date'>18</var>, <var data-var='time'>23:44</var> UTC Update - Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier. Mar <var data-var='date'>18</var>, <var data-var='time'>21:44</var> UTC Update - We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours. Mar <var data-var='date'>18</var>, <var data-var='time'>14:53</var> UTC Update - We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete. Mar <var data-var='date'>18</var>, <var data-var='time'>14:03</var> UTC Monitoring - We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability. Mar <var data-var='date'>18</var>, <var data-var='time'>14:01</var> UTC Update - We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved. Mar <var data-var='date'>18</var>, <var data-var='time'>13:07</var> UTC Update - We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved. Mar <var data-var='date'>18</var>, <var data-var='time'>12:24</var> UTC Update - Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available. Mar <var data-var='date'>18</var>, <var data-var='time'>11:32</var> UTC Update - Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected. Mar <var data-var='date'>18</var>, <var data-var='time'>11:32</var> UTC Investigating - We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Automations aren't triggering on work item creation, field updates, or comment additions

Mar <var data-var='date'>10</var>, <var data-var='time'>00:59</var> UTC Resolved - On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers. Mar <var data-var='date'>10</var>, <var data-var='time'>00:51</var> UTC Monitoring - The performance degradation of automations has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability. Mar <var data-var='date'>10</var>, <var data-var='time'>00:15</var> UTC Identified - Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed. Mar <var data-var='date'>10</var>, <var data-var='time'>00:06</var> UTC Investigating - We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.

Automation events delayed for some customers in the APAC region

Feb <var data-var='date'>26</var>, <var data-var='time'>18:55</var> UTC Resolved - On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers. Feb <var data-var='date'>26</var>, <var data-var='time'>18:33</var> UTC Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability. Feb <var data-var='date'>26</var>, <var data-var='time'>18:05</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available. Feb <var data-var='date'>26</var>, <var data-var='time'>16:21</var> UTC Update - We continue to investigate the issue, and will share an update within next 2 hours or sooner. Feb <var data-var='date'>26</var>, <var data-var='time'>14:25</var> UTC Update - We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner. Feb <var data-var='date'>26</var>, <var data-var='time'>13:22</var> UTC Investigating - Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.

Atlassian Assist in Jira Service Management is currently unavailable.

Feb <var data-var='date'>20</var>, <var data-var='time'>12:26</var> UTC Resolved - This issue has been resolved and all services are functional. Feb <var data-var='date'>20</var>, <var data-var='time'>12:26</var> UTC Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress. Feb <var data-var='date'>20</var>, <var data-var='time'>07:13</var> UTC Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress. Feb <var data-var='date'>20</var>, <var data-var='time'>04:14</var> UTC Update - Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation. Feb <var data-var='date'>20</var>, <var data-var='time'>02:52</var> UTC Identified - Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC

Degraded performance of Cloud Products when selecting users or teams

Feb <var data-var='date'> 7</var>, <var data-var='time'>05:38</var> UTC Resolved - On February 6, 2026, JIRA and JSM 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. Feb <var data-var='date'> 7</var>, <var data-var='time'>05:28</var> UTC Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability. Feb <var data-var='date'> 7</var>, <var data-var='time'>03:43</var> UTC Update - Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. Feb <var data-var='date'> 7</var>, <var data-var='time'>02:22</var> UTC Update - Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available. Feb <var data-var='date'> 6</var>, <var data-var='time'>22:33</var> UTC Update - Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available. Feb <var data-var='date'> 6</var>, <var data-var='time'>20:26</var> UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available. Feb <var data-var='date'> 6</var>, <var data-var='time'>20:24</var> UTC Update - Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes. Feb <var data-var='date'> 6</var>, <var data-var='time'>20:24</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

Disrupted JIRA and JSM availability

Feb <var data-var='date'> 6</var>, <var data-var='time'>20:01</var> UTC Resolved - The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information. Feb <var data-var='date'> 6</var>, <var data-var='time'>14:41</var> UTC Monitoring - The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free. We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts. Feb <var data-var='date'> 6</var>, <var data-var='time'>10:25</var> UTC Update - Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements. We will provide our next update in four hours, or sooner if we have meaningful progress to share. Feb <var data-var='date'> 6</var>, <var data-var='time'>07:52</var> UTC Update - Our team continues active testing of the fix to restore customer accounts affected by this incident. We will provide further update within two hours or sooner. Feb <var data-var='date'> 6</var>, <var data-var='time'>05:57</var> UTC Update - Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident. We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed. Feb <var data-var='date'> 6</var>, <var data-var='time'>03:02</var> UTC Identified - During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period. Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status. We will provide further update within two hours or earlier if there is important information to share. Feb <var data-var='date'> 6</var>, <var data-var='time'>01:47</var> UTC Investigating - We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts. Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status. Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status. There is currently no action required from those customers that have incorrectly received these emails. We will provide further update within an hour as our effort continues.

Users incorrectly moved from Free to Standard Service Collection Trial account

Feb <var data-var='date'> 5</var>, <var data-var='time'>21:38</var> UTC Resolved - On February 5, 2026, JIRA and JIRA Service Management 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. Feb <var data-var='date'> 5</var>, <var data-var='time'>21:09</var> UTC Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability. Feb <var data-var='date'> 5</var>, <var data-var='time'>19:22</var> UTC Update - Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available. Feb <var data-var='date'> 5</var>, <var data-var='time'>17:35</var> UTC Update - Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available. Feb <var data-var='date'> 5</var>, <var data-var='time'>15:39</var> UTC Update - We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available. Feb <var data-var='date'> 5</var>, <var data-var='time'>14:40</var> UTC Identified - Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner. Feb <var data-var='date'> 5</var>, <var data-var='time'>14:13</var> UTC Investigating - Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

Some users in us-east-1 region unable to access Jira and JSM.

Jan <var data-var='date'>28</var>, <var data-var='time'>19:42</var> UTC Resolved - On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident.  There are no actions needed from customers.  The issue has now been resolved, and the service is operating normally for all affected customers. Jan <var data-var='date'>28</var>, <var data-var='time'>18:50</var> UTC Update - We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view.  We will share updates here in one hour or as more information becomes available. Jan <var data-var='date'>28</var>, <var data-var='time'>18:12</var> UTC Identified - We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view.  We will share updates here in one hour or as more information becomes available.

Degraded performance of Jira, JPD, and JSM in eu-west-1

Jan <var data-var='date'>27</var>, <var data-var='time'>11:49</var> UTC Resolved - Deployment of the fix is completed and services are back to normal. This issue is resolved. Jan <var data-var='date'>27</var>, <var data-var='time'>11:33</var> UTC Identified - The incident has affected the Assets product, leading users encountering intermittent unavailability. Our team has identified the cause of the issue and deployed fix for the same. We see that the error rate has decreased, and the team is actively monitoring to ensure further stability. Further updates will follow in 60 minutes or upon significant progress. Jan <var data-var='date'>27</var>, <var data-var='time'>11:07</var> UTC Investigating - We understand that some of our customers are facing intermittent issues with Assets. Our team is investigating the issue. We will update you on the progress within 60 minutes or sooner.

Assets intermittently unavailable

Jan <var data-var='date'>22</var>, <var data-var='time'>16:47</var> UTC Resolved - On January 22, 2026, affected Jira Service Management users may have experienced some service disruption where assets were not loading, affecting their interactions with service management functionality. The issue has now been resolved, and the service is operating normally for all affected customers. Jan <var data-var='date'>22</var>, <var data-var='time'>16:32</var> UTC Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability. Jan <var data-var='date'>22</var>, <var data-var='time'>15:41</var> UTC Identified - We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience issue where assets are not loading, affecting their interactions with service management functionality. We will continue to share additional updates here as more information becomes available. Jan <var data-var='date'>22</var>, <var data-var='time'>14:44</var> UTC Investigating - Jira Service Management users are currently experiencing an issue where assets are not loading, affecting their interactions with service management functionality. We are currently investigating the issue, and the next update will be shared in 60 minutes or sooner

JSM Asset not loading

Jan <var data-var='date'>20</var>, <var data-var='time'>23:09</var> UTC Resolved - On January 20, 2026, some customers may have experienced performance degradation of Assets. The issue has now been resolved, and the service is operating normally for all affected customers. Jan <var data-var='date'>20</var>, <var data-var='time'>21:14</var> UTC Monitoring - The performance degradation of Assets has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability. Jan <var data-var='date'>20</var>, <var data-var='time'>20:08</var> UTC Update - We continue to investigate the issue, and next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved. Jan <var data-var='date'>20</var>, <var data-var='time'>19:10</var> UTC Investigating - Impact Users of the Assets product are experiencing intermittent accessibility issues, resulting in gateway timeouts and internal server errors. These technical disruptions are causing difficulties in performing queries, which may manifest as slow performance or failure to load certain pages, particularly those involving schemas. This issue affects related features that depend on the Assets product, such as specific custom fields and automation processes. Current Status The support teams are actively working to diagnose the issue and are focused on identifying the underlying problems causing the disruption. Efforts are ongoing to restore normal service levels and minimize any further inconvenience to users. Next Steps The incident team is continuing its investigation to determine the full extent of the impact and to identify effective resolutions. Further communications will be issued in 60 minutes or when significant progress is made.

Issue affecting Assets

Jan <var data-var='date'> 7</var>, <var data-var='time'>11:32</var> UTC Resolved - Rerunning the remaining Automation for Jira rules that failed for affected customers is complete. This update resolves the issue. Jan <var data-var='date'> 7</var>, <var data-var='time'>08:37</var> UTC Update - We have replayed about 7 hours of historical events for affected customers to rerun Automation for Jira rules that previously failed. This covers most of the APAC business hours. Based on customer feedback, our team continues monitoring the situation and plans to complete rerunning the remaining Automation for Jira rules that failed earlier. We will provide the next update once replaying the historical events is complete. Jan <var data-var='date'> 7</var>, <var data-var='time'>04:43</var> UTC Update - We are currently replaying historical events for affected customers to rerun Automation for Jira rules that failed to execute earlier. Our teams are closely monitoring the results of this replay to confirm that all affected automations are running as expected. We will provide the next update in about two hours or sooner. Jan <var data-var='date'> 6</var>, <var data-var='time'>14:04</var> UTC Monitoring - Issue has been fixed for all new events - we are waiting for confirmation from some customers when they come online. Customers using Jira and Jira Service Management in Asia Pacific and South East regions had faced issues with Automation for Jira. Other regions not impacted. During Asia Pacific hours tomorrow, the team plans to replay historical events. Team will continue monitoring. Next update will tomorrow. Jan <var data-var='date'> 6</var>, <var data-var='time'>12:19</var> UTC Update - Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. The cause has been identified, and the team is actively working on restoring the operations back to normal as soon as possible. Workaround to manage critical rules, disable and re-enable each automation rule. This triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner. Jan <var data-var='date'> 6</var>, <var data-var='time'>10:11</var> UTC Update - Customers using Jira and Jira Service Management in Asia Pacific and South East regions have faced issues with Automation for Jira. Other regions are not impacted. Some automation rules using specific triggers failed to execute, causing rules to appear unresponsive. We have identified the cause and we continue working on restoring the operations back to normal as soon as possible. In the meantime, workaround to manage business critical rules is to disable and then re-enable each automation rule. This action triggers the rule and must be done for every critical rule. We will provide the next update in about two hours or sooner. Jan <var data-var='date'> 6</var>, <var data-var='time'>07:58</var> UTC Update - Our engineers are continuing work toward the resolution of the incident impacting Automation for Jira. There are no new updates to share at this time. We will provide the next update within 2 hours. Jan <var data-var='date'> 6</var>, <var data-var='time'>06:17</var> UTC Identified - We have identified the cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information becomes available. Jan <var data-var='date'> 6</var>, <var data-var='time'>05:18</var> UTC Investigating - We are investigating an incident impacting Automation for Jira across Jira and Jira Service Management. Some automation rules that use specific triggers may fail to execute. Our team is working to identify the cause and restore normal service. We will provide the next update within 60 minutes.

Disrupted Automation for Jira triggers not running for some customers

Dec <var data-var='date'>27</var>, <var data-var='time'>05:20</var> UTC Resolved - 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. Dec <var data-var='date'>27</var>, <var data-var='time'>04:42</var> UTC Monitoring - 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 progress. Dec <var data-var='date'>27</var>, <var data-var='time'>03:28</var> UTC Update - We are actively investigating this issue and will share additional updates as soon as more information becomes available. We sincerely apologize for the inconvenience this has caused. Dec <var data-var='date'>27</var>, <var data-var='time'>02:48</var> UTC Investigating - We have identified an issue with outbound email delivery and mobile push notifications that is impacting Atlassian Cloud customers across all products. Importantly, customer support tickets are unable to be generated during this time. We apologise for any inconvenience this may cause. We are currently investigating and will provide more information as it becomes available.

Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products

Dec <var data-var='date'>15</var>, <var data-var='time'>19:02</var> UTC Resolved - On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers. Dec <var data-var='date'>15</var>, <var data-var='time'>17:47</var> UTC Update - Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available. Dec <var data-var='date'>15</var>, <var data-var='time'>16:48</var> UTC Update - We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available. Dec <var data-var='date'>15</var>, <var data-var='time'>16:26</var> UTC Update - We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available. Dec <var data-var='date'>15</var>, <var data-var='time'>16:16</var> UTC Identified - We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.

Degraded performance of Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo

Dec <var data-var='date'> 5</var>, <var data-var='time'>15:32</var> UTC Resolved - On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for all affected customers. Dec <var data-var='date'> 5</var>, <var data-var='time'>13:16</var> UTC Monitoring - We are currently investigating an issue where users encounter a Something Went Wrong error when creating a Linked Work Item that includes an attachment. Our engineering team is in the process of deploying the fix to production, and the ETA is 9hours from now. We apologize for the inconvenience and will provide updates as soon as more information becomes available. Thank you for your patience. Next Steps: The team will continue to monitor the situation until the hotfix is fully rolled out. Follow-up communications will be sent once the hot fix is fully rolled out.

Linked worked item functionality is broken, if the work item contains an attachment.

Dec <var data-var='date'> 1</var>, <var data-var='time'>18:26</var> UTC Resolved - Impact Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time. Current Status The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services. Next Steps The team is actively monitoring the systems. Dec <var data-var='date'> 1</var>, <var data-var='time'>18:26</var> UTC Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours. Dec <var data-var='date'> 1</var>, <var data-var='time'>17:30</var> UTC Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours. Dec <var data-var='date'> 1</var>, <var data-var='time'>17:26</var> UTC Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours. Dec <var data-var='date'> 1</var>, <var data-var='time'>17:25</var> UTC Investigating - We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly. The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.

Is Jira Service Desk down?

Jira Service Desk status is UP

Lastest published events

Excessive notifications being received by some Jira Service Management users

Users experiencing issues accessing multiple Atlassian products

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

Jira Service Desk Services, Components and Regions

Recent Jira Service Desk events

Excessive notifications being received by some Jira Service Management users

Users experiencing issues accessing multiple Atlassian products

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

Multiple Atlassian services are experiencing issues

Lookup Objects in Automation for Jira Service Management are not functioning

The Work Item view experience of Jira is restored

Get your FREE account now,
5 monitors included!

Is Jira Service Desk down?

Jira Service Desk status is UP

Lastest published events

Excessive notifications being received by some Jira Service Management users

Users experiencing issues accessing multiple Atlassian products

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

Jira Service Desk Services, Components and Regions

Recent Jira Service Desk events

Excessive notifications being received by some Jira Service Management users

Users experiencing issues accessing multiple Atlassian products

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some users

Multiple Atlassian services are experiencing issues

Lookup Objects in Automation for Jira Service Management are not functioning

The Work Item view experience of Jira is restored

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!