Oct <var data-var='date'> 1</var>, <var data-var='time'>07:51</var> UTC Resolved - On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during the incident window, you may wait for the next scheduled execution or trigger them manually. Oct <var data-var='date'> 1</var>, <var data-var='time'>07:01</var> UTC Update - Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets. Oct <var data-var='date'> 1</var>, <var data-var='time'>05:00</var> UTC Update - Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected. Oct <var data-var='date'> 1</var>, <var data-var='time'>04:03</var> UTC Update - Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. Oct <var data-var='date'> 1</var>, <var data-var='time'>03:47</var> UTC Identified - Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share. Oct <var data-var='date'> 1</var>, <var data-var='time'>02:55</var> UTC Investigating - Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

Job processing and scheduling is degraded affecting multiple Atlassian products

Sep <var data-var='date'>24</var>, <var data-var='time'>15:53</var> UTC Resolved - On September 24th 2026, some Jira and JSM users in the US region may have experienced a performance degradation impacting Jira issue creation, issue viewing, and board loading. The issue has now been resolved, and the service is operating normally for all affected customers. Sep <var data-var='date'>24</var>, <var data-var='time'>14:58</var> UTC Monitoring - Mitigations have been deployed and we are seeing positive signs of recovery across Jira. Issues viewing work items, loading boards, and creating tickets are subsiding. We are continuing to monitor system health to ensure full stability and will share our next update within 60 minutes. Sep <var data-var='date'>24</var>, <var data-var='time'>13:54</var> UTC Investigating - We continue to investigate the issue impacting Jira issue creation, issue viewing, and board loading. Our teams remain engaged on identifying a resolution. We will provide the next update in 1 hour, or sooner if there is material progress.

Degraded Performance Viewing Issues and Boards

Sep <var data-var='date'>14</var>, <var data-var='time'>17:43</var> UTC Resolved - On September 14, 2026, Opsgenie and Jira Service Management experienced a disruption, and impacted users saw delayed alerts notification and inability to view the alerts in the user interface. The issue has now been resolved, and the service is operating normally for all affected customers. Sep <var data-var='date'>14</var>, <var data-var='time'>17:27</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. Sep <var data-var='date'>14</var>, <var data-var='time'>17:16</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We will continue to share additional updates here as more information is available. Sep <var data-var='date'>14</var>, <var data-var='time'>16:46</var> UTC Investigating - We are actively investigating reports of a service disruption affecting Opsgenie and Jira Service Management. We will share updates here as more information is available.

Disrupted Opsgenie/JSM availability

Sep <var data-var='date'>11</var>, <var data-var='time'>08:37</var> UTC Resolved - On 11 September 2026, Between 07:02 UTC and 07:56 UTC, some Jira Software and Jira Service Management users may have experienced degraded performance and errors when accessing Work Items and Boards. The issue has now been resolved, and all services are operating normally. Sep <var data-var='date'>11</var>, <var data-var='time'>08:06</var> UTC Monitoring - A mitigation has been deployed, and we are observing recovery across Jira Software and Jira Service Management issue views and boards. Our engineering teams are closely monitoring the environment to ensure sustained stability. We will provide another update once full resolution is confirmed or within 60 minutes. Sep <var data-var='date'>11</var>, <var data-var='time'>07:46</var> UTC Investigating - We are investigating reports of an issue affecting Jira Software and Jira Service Management. Affected users may experience errors or delays when loading issue views and viewing boards. We are working to identify the root cause and will provide an update as more information becomes available.

Degraded performance affecting Jira Software and Jira Service Management

Sep <var data-var='date'> 3</var>, <var data-var='time'>17:03</var> UTC Resolved - On September 3, 2026, some Jira Service Management users may have experienced errors viewing the Affected Services field or performance degradation on the web. The issue has now been resolved, and the service is operating normally for all affected customers. Sep <var data-var='date'> 3</var>, <var data-var='time'>16:15</var> UTC Monitoring - The performance degradation of Jira Service Management has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability. Sep <var data-var='date'> 3</var>, <var data-var='time'>15:20</var> UTC Update - We have identified the cause of the issue affecting Jira Service Management and are currently deploying a fix. We expect to see recovery shortly and will continue to monitor the situation closely. We will provide the next update in 60 minutes, or sooner if there is a material update. Sep <var data-var='date'> 3</var>, <var data-var='time'>14:20</var> UTC Investigating - We are investigating an issue impacting Jira Service Management. Affected users may experience errors or slowness when viewing or interacting with the Affected Services field. Our teams are actively investigating the root cause. We will provide the next update in the next 1 hour, or sooner.

Jira Service Management - Degradation with Affected Services Field

Sep <var data-var='date'> 1</var>, <var data-var='time'>11:44</var> UTC Resolved - On 1st Sept 2026, between 04:22 UTC to 10:59 UTC, some Jira users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all the customers. Sep <var data-var='date'> 1</var>, <var data-var='time'>10:11</var> UTC Monitoring - We have identified the root cause of the issue impacting Jira Work Item transitions and have applied a fix. We are currently seeing signs of recovery and will continue to monitor. We will provide the next update in the next 1 hour, or sooner if there is a material update.

Jira - Work Item transition failures

Aug <var data-var='date'>27</var>, <var data-var='time'>05:16</var> UTC Resolved - On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence 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. A public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed. Aug <var data-var='date'>27</var>, <var data-var='time'>04:51</var> UTC Monitoring - The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available. Aug <var data-var='date'>27</var>, <var data-var='time'>04:33</var> UTC Identified - Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available. Aug <var data-var='date'>27</var>, <var data-var='time'>04:25</var> UTC Update - We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers. Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available. Aug <var data-var='date'>27</var>, <var data-var='time'>04:22</var> UTC Investigating - Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.

Issues accessing multiple Atlassian products in some regions

Aug <var data-var='date'>25</var>, <var data-var='time'>14:33</var> UTC Resolved - On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers. Aug <var data-var='date'>25</var>, <var data-var='time'>13:01</var> UTC Monitoring - Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share. Aug <var data-var='date'>25</var>, <var data-var='time'>10:49</var> UTC Update - Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share. Aug <var data-var='date'>25</var>, <var data-var='time'>09:44</var> UTC Update - Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share. Aug <var data-var='date'>25</var>, <var data-var='time'>08:42</var> UTC Investigating - We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.

Notifications are delayed

Aug <var data-var='date'>24</var>, <var data-var='time'>23:15</var> UTC Resolved - On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours. Aug <var data-var='date'>24</var>, <var data-var='time'>21:30</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 increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available. Aug <var data-var='date'>24</var>, <var data-var='time'>20:25</var> UTC Update - Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence. Aug <var data-var='date'>24</var>, <var data-var='time'>19:22</var> UTC Investigating - We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.

Degraded performance of Notifications

Aug <var data-var='date'> 7</var>, <var data-var='time'>12:52</var> UTC Resolved - On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers. Aug <var data-var='date'> 7</var>, <var data-var='time'>12:22</var> UTC Monitoring - Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier. Aug <var data-var='date'> 7</var>, <var data-var='time'>11:30</var> UTC Investigating - We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

Performance and access related issues with Jira

Aug <var data-var='date'> 7</var>, <var data-var='time'>01:46</var> UTC Resolved - On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers. Aug <var data-var='date'> 7</var>, <var data-var='time'>01:39</var> UTC Monitoring - The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability. Aug <var data-var='date'> 7</var>, <var data-var='time'>01:33</var> UTC Investigating - We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.

Degraded performance of JIRA

Jul <var data-var='date'>24</var>, <var data-var='time'>13:07</var> UTC Resolved - Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance. Jul <var data-var='date'>22</var>, <var data-var='time'>06:59</var> UTC Update - A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team. Jul <var data-var='date'>21</var>, <var data-var='time'>09:48</var> UTC Identified - We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.

Voice call failures for some India based numbers

Jul <var data-var='date'>22</var>, <var data-var='time'>00:56</var> UTC Resolved - Our team has been able to validate that all rule executions are performing normally and this issue is now resolved. Jul <var data-var='date'>21</var>, <var data-var='time'>04:53</var> UTC Identified - The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place. Jul <var data-var='date'>20</var>, <var data-var='time'>21:27</var> UTC Update - Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available. Jul <var data-var='date'>20</var>, <var data-var='time'>20:18</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.

Degraded performance of Jira Automation rules

Jul <var data-var='date'>20</var>, <var data-var='time'>17:23</var> UTC Resolved - On July 20, 2026, some Jira and Jira Service Management users may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Jul <var data-var='date'>20</var>, <var data-var='time'>16:58</var> UTC Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. We are currently seeing signs of improvements, however, affected users may experience delays in Jira and Jira Service management Automation rule executions. We'll continue to share additional updates here as more information is available. Jul <var data-var='date'>20</var>, <var data-var='time'>16:03</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.

Jul <var data-var='date'> 6</var>, <var data-var='time'>13:04</var> UTC Resolved - On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and  between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers. Jul <var data-var='date'> 6</var>, <var data-var='time'>12:25</var> UTC Monitoring - We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier. Jul <var data-var='date'> 6</var>, <var data-var='time'>11:46</var> UTC Investigating - We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner. Jul <var data-var='date'> 6</var>, <var data-var='time'>10:04</var> UTC Monitoring - We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner. Jul <var data-var='date'> 6</var>, <var data-var='time'>09:23</var> UTC Investigating - We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

Reliability issues with Jira and Confluence

Jun <var data-var='date'>26</var>, <var data-var='time'>05:13</var> UTC Resolved - Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance. Jun <var data-var='date'>19</var>, <var data-var='time'>22:46</var> UTC Monitoring - Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select  > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

Jira : Incoming emails partial outage

Jun <var data-var='date'>10</var>, <var data-var='time'>10:00</var> UTC Resolved - On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers. Jun <var data-var='date'>10</var>, <var data-var='time'>09:42</var> UTC Investigating - Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

Unable to load Assets page

Jun <var data-var='date'>10</var>, <var data-var='time'>06:31</var> UTC Resolved - We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused. Jun <var data-var='date'>10</var>, <var data-var='time'>06:14</var> UTC Monitoring - Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner. Jun <var data-var='date'>10</var>, <var data-var='time'>05:39</var> UTC Identified - Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products. Jun <var data-var='date'>10</var>, <var data-var='time'>04:55</var> UTC Investigating - We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

Delays in processing incoming Emails, Work Item notifications, and Scheduled Triggers in Marketplace Apps

Jun <var data-var='date'> 9</var>, <var data-var='time'>18:27</var> UTC Resolved - The issue has now been resolved, and the service is operating normally for all affected customers. Jun <var data-var='date'> 9</var>, <var data-var='time'>10:36</var> UTC Monitoring - Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability. Jun <var data-var='date'> 9</var>, <var data-var='time'>10:21</var> UTC Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>10:20</var> UTC Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>09:27</var> UTC Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>09:26</var> UTC Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>06:22</var> UTC Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>06:21</var> UTC Identified - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier. Jun <var data-var='date'> 9</var>, <var data-var='time'>05:29</var> UTC Investigating - We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

Some users experiencing issues viewing boards and work items

Jun <var data-var='date'> 8</var>, <var data-var='time'>02:56</var> UTC Resolved - On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely. Jun <var data-var='date'> 8</var>, <var data-var='time'>02:36</var> UTC Identified - We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour. Jun <var data-var='date'> 8</var>, <var data-var='time'>01:53</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

Users experiencing issues loading work items in Jira and JSM

Jun <var data-var='date'> 2</var>, <var data-var='time'>16:51</var> UTC Resolved - On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours. Jun <var data-var='date'> 2</var>, <var data-var='time'>15:32</var> UTC Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

Degraded performance of Jira and JSM automations in US East

Jun <var data-var='date'> 1</var>, <var data-var='time'>13:23</var> UTC Resolved - This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience. Jun <var data-var='date'> 1</var>, <var data-var='time'>09:08</var> UTC Monitoring - We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability. Jun <var data-var='date'> 1</var>, <var data-var='time'>08:06</var> UTC Identified - We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour. Jun <var data-var='date'> 1</var>, <var data-var='time'>08:06</var> UTC Investigating - We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

For Jira-software viewIssues and viewBoard are degraded

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.

Is Jira Service Desk down?

Jira Service Desk status is UP

Lastest published events

Job processing and scheduling is degraded affecting multiple Atlassian products

Degraded Performance Viewing Issues and Boards

Disrupted Opsgenie/JSM availability

Jira Service Desk Services, Components and Regions

Recent Jira Service Desk events

Job processing and scheduling is degraded affecting multiple Atlassian products

Degraded Performance Viewing Issues and Boards

Disrupted Opsgenie/JSM availability

Degraded performance affecting Jira Software and Jira Service Management

Jira Service Management - Degradation with Affected Services Field

Jira - Work Item transition failures