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:07</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'>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.

Users experiencing issues accessing multiple Atlassian products

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'>06:39</var> UTC Resolved - The issue causing Jira users inability to log time on business board has been resolved. A fix was deployed to address the problem and the service is operating normally for all affected customers. May <var data-var='date'> 6</var>, <var data-var='time'>04:16</var> UTC Identified - Our engineering teams have identified the cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. May <var data-var='date'> 6</var>, <var data-var='time'>03:18</var> UTC Investigating - We are investigating reports of users unable to log time while on business board. Our engineering teams are actively investigating and working to resolve the issue. We will provide more updates in next 1 hour.

Jira users unable to log time while on business board

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

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

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.

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:47</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 Identified - 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.

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

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:24</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.

Degraded Performance for Some Jira Users

Nov <var data-var='date'>17</var>, <var data-var='time'>11:50</var> UTC Resolved - The issue has been resolved. All systems are healthy and fully operational, with no further problems observed in sending emails from Jira. Nov <var data-var='date'>15</var>, <var data-var='time'>21:36</var> UTC Monitoring - We were experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This affected authentication for some users. After scaling our internal services, we have observed a reduction in timeout errors with reliability metrics returning to normal. We apologize for any inconvenience this may have caused. Nov <var data-var='date'>15</var>, <var data-var='time'>21:36</var> UTC Update - We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress. Nov <var data-var='date'>15</var>, <var data-var='time'>16:29</var> UTC Identified - We are currently experiencing issues due to timeouts when refreshing OAuth tokens from Microsoft. This has impacted authentication for some users. In the last 30 minutes, we have observed a reduction in timeout errors and signs of recovery. We apologize for any inconvenience this may have caused and appreciate your patience as we work towards a full resolution. We will continue to keep you updated on our progress.

Some users are unable to send emails from Jira

Oct <var data-var='date'>27</var>, <var data-var='time'>17:50</var> UTC Resolved - Between 15:09 UTC to 17:16 UTC, some customers experienced partial outage for Jira Work Management, Jira Service Management, and Jira viewIssue, createIssue and editIssue caused by a faulty code rollout. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The root cause is still being investigated and will be provided in the post incident review. The conditions that cause the errors are being addressed and we're actively working on a permanent fix. The issue has been resolved and the services are operating normally. Oct <var data-var='date'>27</var>, <var data-var='time'>16:33</var> UTC Investigating - Impact Jira Software users are experiencing service degradation in viewIssue and createIssue. This issue affects multiple regions, with noticeable impacts on user functionalities across these experiences. This is potentially affecting Jira Service Management and Jira Work Management. Next Steps - The team is investigating and further communications will be provided in 60 minutes.

Jira Platform Incident - viewIssue and createIssue Service Disruption

Oct <var data-var='date'>21</var>, <var data-var='time'>05:24</var> UTC Resolved - Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the inconvenience that this incident has caused and we will provide further information when the Post Incident Investigation has been completed. Oct <var data-var='date'>21</var>, <var data-var='time'>03:24</var> UTC Update - The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue to see recovery continuing across all impacted products and our teams are continuing to monitor as the recovery continues. We will provide further update on our recovery status within two hours. Oct <var data-var='date'>21</var>, <var data-var='time'>01:07</var> UTC Update - We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in two hours. Oct <var data-var='date'>21</var>, <var data-var='time'>00:03</var> UTC Update - Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message directing customers to our temporary support channel. Please note that our support portal is currently fully functional for those attempting to raise requests. We are continuing to look into this alert to remove this message. We will provide further update on our recovery status in one hour. Oct <var data-var='date'>20</var>, <var data-var='time'>22:58</var> UTC Update - Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support. Oct <var data-var='date'>20</var>, <var data-var='time'>21:26</var> UTC Update - Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and will continue to monitor the health of AWS services and the effects on Atlassian customers. We appreciate your continued patience and remain committed to full resolution as we work through this situation. We will post our next update in two hours. Oct <var data-var='date'>20</var>, <var data-var='time'>18:38</var> UTC Monitoring - There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. Oct <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available. Oct <var data-var='date'>20</var>, <var data-var='time'>17:43</var> UTC Update - We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and we are closely monitoring the health of AWS services. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available. Oct <var data-var='date'>20</var>, <var data-var='time'>17:27</var> UTC Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available. Oct <var data-var='date'>20</var>, <var data-var='time'>16:35</var> UTC Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue. Oct <var data-var='date'>20</var>, <var data-var='time'>16:34</var> UTC Update - Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and while we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will be providing hourly updates on this issue. Oct <var data-var='date'>20</var>, <var data-var='time'>15:21</var> UTC Update - Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this time, we remain committed to full resolution and deeply appreciate your patience as we work through this situation. We will continue to provide updates every hour or sooner as new information becomes available. Oct <var data-var='date'>20</var>, <var data-var='time'>14:03</var> UTC Update - We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide updates every hour or sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>13:58</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>13:56</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>13:07</var> UTC Update - Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>12:06</var> UTC Update - Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>11:06</var> UTC Update - We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>09:58</var> UTC Identified - We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>09:24</var> UTC Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>09:23</var> UTC Update - We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not sooner. Oct <var data-var='date'>20</var>, <var data-var='time'>08:24</var> UTC Update - Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour. Oct <var data-var='date'>20</var>, <var data-var='time'>07:56</var> UTC Investigating - We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.

Atlassian Cloud Services impacted

Oct <var data-var='date'>15</var>, <var data-var='time'>16:16</var> UTC Resolved - Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Approximately 50 percent of Automation API calls were affected in the us-east-1 region with customers receiving 429 status codes. Current Status The incident has been mitigated by increasing the API Gateway rate limit service quota and disabling the internal service that was causing high traffic volume. Next Steps We are conducting a root cause analysis of the internal service. A post incident review will be conducted. Oct <var data-var='date'>15</var>, <var data-var='time'>15:26</var> UTC Monitoring - We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and require re-running. Current Status The incident has been mitigated and we continue to investigate the cause of this incident Next Steps We are continuing to monitor the service, and will provide further updates in the next two hours Oct <var data-var='date'>15</var>, <var data-var='time'>14:34</var> UTC Update - Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of the progress in next 2 hours, if not sooner. Oct <var data-var='date'>15</var>, <var data-var='time'>13:43</var> UTC Investigating - UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

Unable to perform UI Operations

Sep <var data-var='date'>22</var>, <var data-var='time'>07:17</var> UTC Resolved - A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up. Sep <var data-var='date'>22</var>, <var data-var='time'>06:55</var> UTC Monitoring - Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available. Sep <var data-var='date'>22</var>, <var data-var='time'>05:59</var> UTC Update - Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing. Sep <var data-var='date'>22</var>, <var data-var='time'>05:38</var> UTC Identified - Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.

Degraded performance to multiple Atlassian experiences

Sep <var data-var='date'>15</var>, <var data-var='time'>06:40</var> UTC Resolved - An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections List', ensuring that you are on version 1.0.0.31 or higher to ensure you are running the version that contains the fixed release. All Edge browsers should otherwise receive this update within 10 hours without user intervention. Sep <var data-var='date'>10</var>, <var data-var='time'>20:34</var> UTC Monitoring - We have identified the root cause of the Microsoft Edge 140 tracking prevention issue and have mitigated the problem and we continue monitoring closely. The issue has been mitigated however it will not be considered resolved until Microsoft issues an updated version of the Edge browser scheduled for September 18th. This will be the last update until the issue is resolved. Sep <var data-var='date'>10</var>, <var data-var='time'>18:35</var> UTC Update - We continue to work on resolving the Microsoft Edge 140 tracking prevention issue for Confluence, Jira Work Management, Jira Service Management, Jira, Jira Align, and Jira Product Discovery. We have identified the root cause and are working on solutions for each product. We will provide the next update within three hours. Sep <var data-var='date'>10</var>, <var data-var='time'>00:55</var> UTC Update - Our team is aware that the incorrect classification of Atlassian sites as advertising has been resolved, however these changes will take some time to propagate out to users since we are waiting for Edge from Microsoft to incorporate the changes. We are continuing to monitor the situation and will provide further update when we are able to confirm that the issue is resolved. Sep <var data-var='date'> 9</var>, <var data-var='time'>11:40</var> UTC Identified - Important Update on Attachment Issues with Edge 140 and Atlassian Products We've identified an issue affecting images, media, and Whiteboards in Confluence and Jira for users who have upgraded to Microsoft Edge version 140.0.3485.54 with Strict tracking prevention enabled. These settings can block media (images and videos) content from loading, uploading, or opening. The issue is triggered by Edge's Strict tracking prevention incorrectly classifying Atlassian as advertising, impacting functionality. Recommended Workarounds: - Switch your tracking prevention settings from 'Strict' to the 'Balanced (Recommended)' mode in Edge. - Alternatively, add an 'Exception' for the URL you use to access Atlassian products. - Use a different browser, such as Chrome, Firefox, or Safari. This issue only affects Microsoft Edge. Other browsers are not affected by this issue. Thank you for your patience as we work through this issue. We'll provide updates as they become available. Sep <var data-var='date'> 9</var>, <var data-var='time'>10:23</var> UTC Investigating - We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

Degraded performance in Confluence and Jira for Microsoft Edge users

Aug <var data-var='date'> 8</var>, <var data-var='time'>12:18</var> UTC Resolved - Between 02:00 am UTC and 11:57 am UTC, we experienced issues with custom fields created by the Forge app for Jira Work Management and Jira. The issue has been resolved, and the service is now operating normally. Aug <var data-var='date'> 8</var>, <var data-var='time'>09:16</var> UTC Update - Our team continues to work on restoring full functionality. The fix is currently being deployed across all regions. Some users can already start noticing improvements. The next update will be provided as soon as the issue is fully resolved. Aug <var data-var='date'> 8</var>, <var data-var='time'>05:08</var> UTC Update - Our intended resolution for the issue impacting Forge custom fields on Jira Work Management and Jira is taking longer than expected. Our team is continuing to work on this issue with urgency and we will provide an update as soon as possible. Aug <var data-var='date'> 7</var>, <var data-var='time'>23:57</var> UTC Identified - We continue to work on resolving the functionality impacted for Forge custom fields on Jira Work Management and Jira. We have identified the root cause and expect recovery shortly. Aug <var data-var='date'> 7</var>, <var data-var='time'>22:25</var> UTC Investigating - We are aware of the fact that customers are facing issues with using Forge app created custom fields. The issue is that the the data selected or typed in the field is cleared when the focus is lost. However, even though the data looks like it is no longer present, the system has still stored it. Therefore, as a workaround, users can ignore the fact that the data is no longer visible and Click Issue create anyway. We are actively looking into the root cause to remediate this issue promptly.

Custom Fields loses values after submission on Global Issue Create Screen

Jul <var data-var='date'>30</var>, <var data-var='time'>07:31</var> UTC Resolved - We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation. Jul <var data-var='date'>30</var>, <var data-var='time'>07:10</var> UTC Investigating - We are investigating an issue causing a degraded experience when adding attachments or accessing existing media content.

Degraded experience adding and accessing media attachments

Jul <var data-var='date'>10</var>, <var data-var='time'>08:55</var> UTC Resolved - Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating normally. All scheduled triggers has been replayed. Jul <var data-var='date'>10</var>, <var data-var='time'>08:32</var> UTC Monitoring - We are investigating reports of intermittent errors for some Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud customers failing invocation, mostly scheduled triggers and smart links from 5:44 am UTC to 7:44 am UTC. We have put mitigations in place, and the errors have receded. We are monitoring the incident resolution. Customers will sometimes see errors in app functionality during this time and scheduled triggers might not work. We have replayed the scheduled triggers.

Intermittent failure in Forge app invocation

Jun <var data-var='date'>25</var>, <var data-var='time'>10:57</var> UTC Resolved - Between 07:40 UTC and 10:31 UTC, we experienced issues affecting user syncing in Atassian Administration. This affected Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. The issue has been resolved and the service is operating normally. Jun <var data-var='date'>25</var>, <var data-var='time'>10:41</var> UTC Monitoring - We have identified the root cause of the issue and have mitigated the problem. We are now monitoring closely. Jun <var data-var='date'>25</var>, <var data-var='time'>10:21</var> UTC Identified - We continue to work on resolving the user syncing functionality for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. We have identified the root cause and expect recovery shortly. Jun <var data-var='date'>25</var>, <var data-var='time'>09:38</var> UTC Investigating - We are investigating reports of errors loading Users and Groups pages in Atlassian Administration, and errors affecting user IDP syncing. We will provide more details once we identify the root cause.

Issues affecting user syncing, Atlassian Administration

Jun <var data-var='date'>24</var>, <var data-var='time'>13:36</var> UTC Resolved - The issue affecting Jira access, which occurred between June 24th 9:55 AM UTC and 11:08 AM UTC due to a service scaling problem, has been resolved, and the incident is now closed. Jun <var data-var='date'>24</var>, <var data-var='time'>12:03</var> UTC Investigating - We are investigating an issue where multiple customers are unable to open their Jira cloud products. We will provide additional updates within the next hour.

Users unable to open their Jira cloud products

Jun <var data-var='date'>17</var>, <var data-var='time'>09:31</var> UTC Resolved - Between 2:12 UTC to 08:45 UTC, we experienced child work item panel not loading intermittently for Jira Work Management, Jira Service Management, and Jira. The issue has been resolved and the service is operating normally. Jun <var data-var='date'>17</var>, <var data-var='time'>08:54</var> UTC Monitoring - We have identified the root cause of the intermittent errors for child work item panel and have mitigated the problem. We are now monitoring closely. Jun <var data-var='date'>17</var>, <var data-var='time'>08:21</var> UTC Update - We continue to work on resolving the child work item panel for Jira Work Management, Jira Service Management, and Jira. We have identified the root cause and expect recovery shortly. Jun <var data-var='date'>17</var>, <var data-var='time'>08:07</var> UTC Identified - We are investigating reports of intermittent errors for Jira Work Management, Jira Service Management, and Jira Cloud customers for child work item panel. We will provide more details once we identify the root cause.

Child work item panel is not loading intermitently

Jun <var data-var='date'>13</var>, <var data-var='time'>07:11</var> UTC Resolved - The issues causing delayed emails from Jira have been resolved, and services are functioning normally for all affected users. Jun <var data-var='date'>13</var>, <var data-var='time'>05:40</var> UTC Investigating - We are aware of some customers having delays receiving emails from their Jira, JWM and JSM automations. Our team is looking into this issue with urgency and will provide further update when available.

Jira, JWM and JSM Email Automations delays for some users

Jun <var data-var='date'> 4</var>, <var data-var='time'>20:59</var> UTC Resolved - Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the service is operating normally. Jun <var data-var='date'> 4</var>, <var data-var='time'>17:17</var> UTC Investigating - We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and mail is being processed normally as of 16:45 UTC. We will continue to monitor system performance and will provide more details within the next hour.

Is Jira Core down?

Jira Core status is UP

Lastest published events

For Jira-software viewIssues and viewBoard are degraded

Users experiencing issues accessing multiple Atlassian products

Multiple Atlassian services are experiencing issues

Jira Core Services, Components and Regions

Recent Jira Core events

For Jira-software viewIssues and viewBoard are degraded

Users experiencing issues accessing multiple Atlassian products

Multiple Atlassian services are experiencing issues

Jira users unable to log time while on business board

The Work Item view experience of Jira is restored

Disrupted Rovo availability for Automation rules

Get your FREE account now,
5 monitors included!

Is Jira Core down?

Jira Core status is UP

Lastest published events

For Jira-software viewIssues and viewBoard are degraded

Users experiencing issues accessing multiple Atlassian products

Multiple Atlassian services are experiencing issues

Jira Core Services, Components and Regions

Recent Jira Core events

For Jira-software viewIssues and viewBoard are degraded

Users experiencing issues accessing multiple Atlassian products

Multiple Atlassian services are experiencing issues

Jira users unable to log time while on business board

The Work Item view experience of Jira is restored

Disrupted Rovo availability for Automation rules

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!