Atlassian Outage History

Started Sep 12, 2025, 04:38 PM UTC· resolved Sep 16, 2025, 01:08 AM UTC

1. investigating Sep 12, 2025, 04:38 PM UTC

   Customer sites in our us-east-1 region are experiencing failures creating new data shares. We are investigating the issue.

2. identified Sep 12, 2025, 05:31 PM UTC

   The issue has been identified and we are working on a fix.

3. identified Sep 12, 2025, 06:09 PM UTC

   We are working with a vendor on the fix and expect resolution early next week. The next update will be Monday 9/15.

4. resolved Sep 16, 2025, 01:08 AM UTC

   A fix has been rolled out that resolves the error creating new Data Shares.

Read the full incident report →

Started Sep 11, 2025, 08:53 AM UTC· resolved Sep 11, 2025, 06:45 PM UTC

1. identified Sep 11, 2025, 08:53 AM UTC

   Atlassian teams remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams are also engaged on this incident to ensure we can get to a resolution as soon as possible. At this point, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

2. identified Sep 11, 2025, 09:51 AM UTC

   Atlassian teams continue to remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams also continue to remain engaged on this incident to ensure our focus is not diluted from a resolution as soon as possible. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

3. identified Sep 11, 2025, 10:59 AM UTC

   Our teams have are identified some potential resolution steps for this issue and continue to test the same on priority to be able to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

4. identified Sep 11, 2025, 11:53 AM UTC

   Atlassian teams continue to test the identified potential resolution steps for this issue. Our goal is to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

5. identified Sep 11, 2025, 01:02 PM UTC

   We are progressing well with the testing of identified potential mitigation steps for this issue; and we are seeing positive early results. We will update with an ETA and further information in the next update. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.

6. identified Sep 11, 2025, 02:00 PM UTC

   We have progressed further in preparing our system with a probable fix. Initial testing has been successful. We are in the process of completing further testing and finalising the fix. We expect the fix to be completed in next few hours. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.

7. monitoring Sep 11, 2025, 03:05 PM UTC

   We have deployed the fix and all operations are back to normal. We will continue to monitor the operations. We will continue providing specific updates when available.

8. resolved Sep 11, 2025, 06:45 PM UTC

   Between September 10, 2025, 3:19 PM UTC and September 11, 2025, 2:44 PM UTC, there was degraded performance in web experiences and the REST APIs for some Jira Service Management, Opsgenie, and Compass Cloud customers in the US region. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Sep 10, 2025, 03:23 PM UTC· resolved Sep 11, 2025, 06:45 PM UTC

1. investigating Sep 10, 2025, 03:23 PM UTC

   We identified degraded performance in web experiences and Alert Rest API for some Jira Service Management and Opsgenie Cloud customers in the US Region. The team has taken actions to mitigate the issue and minimize the impact on search functionality.

2. identified Sep 10, 2025, 03:26 PM UTC

   We continue to work on resolving the incident for Jira Service Management and Opsgenie. We have identified the root cause and taken actions to mitigate the issue and minimize the impact on search functionality.

3. identified Sep 10, 2025, 05:56 PM UTC

   We are continuing to work on a fix for this issue.

4. identified Sep 10, 2025, 08:10 PM UTC

   Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.

5. identified Sep 11, 2025, 12:11 AM UTC

   Our team has been able to identify the root cause of these performance issues and have put a mitigation into place. We are now continuing to see recovery of Jira Service Management operations and Opsgenie services. Existing alerts are continuing to be processed at this time. We will provide further update as soon as possible.

6. identified Sep 11, 2025, 01:10 AM UTC

   We are continuing to see recovery of Jira Service Management operations and Opsgenie services. There are a large number of missed alerts to be processed due to the prior service issue and our team is actively investigating methods to help expedite this processing. Alerts should trigger in the meantime but the content of these alerts may not be visible at this time. Our teams are continuing to investigate with urgency. We will provide further updates within the hour.

7. identified Sep 11, 2025, 02:10 AM UTC

   While new alerts should now correctly notify users, the content of those alerts for impacted customers will remain empty until missed alerts are fully processed. Our team is continuing to investigate with urgency potential infrastructure options to expedite this process. We will provide further updates within the hour.

8. identified Sep 11, 2025, 03:10 AM UTC

   New alerts should still continue to notify users as they are generated, however the alert content will still be missing. Our teams are still actively engaging with infrastructure teams to try and expedite historical processing of messages to fully restore services. We will provide further updates within the hour.

9. identified Sep 11, 2025, 03:49 AM UTC

   We have received reports that some customers are experiencing further issues relating to loading pages within Opsgenie and Jira Service Management which may be related to the infrastructure efforts underway to restore services to these products. Please be aware we also have teams actively investigating these issues to ensure as fast a resolution as possible. We want to reiterate that your alerts are still sending notifications correctly, and there is no data loss occurring. However, the underlying issue is affecting the propagation of alert details to notifications, and to the Web and Mobile UI. Viewing schedules may also be impacted at this time while we continue to process the tasks required for recovery. We will provide further updates as soon as possible.

10. identified Sep 11, 2025, 04:50 AM UTC

    Our team is continuing to investigate with the highest level of urgency in order to restore Jira Service Management and Opsgenie services. At this time we are prioritising infrastructure to try and restore new and active alerts to be populated with their alert content as soon as possible, while continuing to deliver existing messages as they are ready. We will continue to provide updates as we progress, and will ensure we have an update posted within the hour.

11. identified Sep 11, 2025, 05:51 AM UTC

    Our infrastructure teams are working diligently to try and ensure all services are restored to Jira Service Management and Opsgenie as soon as possible. New alerts are continuing to notify users, however we are still prioritising infrastructure to restore the content inside these alerts for Web and Mobile UIs. We will continue providing updates when available and will ensure we have further update within the hour.

12. identified Sep 11, 2025, 06:51 AM UTC

    Our teams priority remains to restore full functionality to new alerts to users from Jira Service Management and Opsgenie. Escalation teams are fully engaged on this incident to try and ensure we can get to a resolution as soon as possible. At this time these alerts are still successfully notifying users, but without the intended content within the alerts. We will continue providing specific updates when available and will ensure we have further update within the hour.

13. identified Sep 11, 2025, 07:50 AM UTC

    All concerned teams are engaged and are working to restore full functionality to new alerts to users from Jira Service Management and Opsgenie. Escalation teams are also engaged on this incident to try and ensure we can get to a resolution as soon as possible. Currently, the alerts continue to successfully notify users, but without the intended content within the alerts. We will continue providing specific updates when available and will ensure we have further update within the hour.

14. identified Sep 11, 2025, 08:53 AM UTC

    Atlassian teams remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams are also engaged on this incident to ensure we can get to a resolution as soon as possible. At this point, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

15. identified Sep 11, 2025, 09:51 AM UTC

    Atlassian teams continue to remain engaged with priority to restore full functionality to new alerts to users from Jira Service Management, Opsgenie and Compass. Escalation teams also continue to remain engaged on this incident to ensure our focus is not diluted from a resolution as soon as possible. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

16. identified Sep 11, 2025, 10:59 AM UTC

    Our teams have are identified some potential resolution steps for this issue and continue to test the same on priority to be able to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

17. identified Sep 11, 2025, 11:53 AM UTC

    Atlassian teams continue to test the identified potential resolution steps for this issue. Our goal is to restore full functionality to users from Jira Service Management, Opsgenie and Compass. Currently, the alerts continue to successfully notify users, except that the responder name may be missing. We will continue providing specific updates when available and will ensure we have further update within the hour.

18. identified Sep 11, 2025, 01:02 PM UTC

    We are progressing well with the testing of identified potential mitigation steps for this issue; and we are seeing positive early results. We will update with an ETA and further information in the next update. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.

19. identified Sep 11, 2025, 02:00 PM UTC

    We have progressed further in preparing our system with a probable fix. Initial testing has been successful. We are in the process of completing further testing and finalising the fix. We expect the fix to be completed in next few hours. Alerts continue to successfully notify users, in some cases the responder name may be missing. Our goal continues to restore full functionality to users from Jira Service Management, Opsgenie and Compass. We will continue providing specific updates when available and will ensure we have further update within the hour.

20. monitoring Sep 11, 2025, 03:05 PM UTC

    We have deployed the fix and all operations are back to normal. We will continue to monitor the operations. We will continue providing specific updates when available.

21. resolved Sep 11, 2025, 06:45 PM UTC

    Between September 10, 2025, 3:19 PM UTC and September 11, 2025, 2:44 PM UTC, there was degraded performance in web experiences and the REST APIs for some Jira Service Management, Opsgenie, and Compass Cloud customers in the US region. We have deployed a fix to mitigate the issue and have verified that the services have recovered. The issue has been resolved and the service is operating normally.

22. postmortem Sep 24, 2025, 06:24 AM UTC

    ### **SUMMARY** Between September 10, 2025, at 13:56 UTC and September 11, 2025, at 14:40 UTC, Jira Service Management, Compass Cloud Operations, and Opsgenie customers in the U.S. region experienced degraded performance across web and mobile applications, as well as Alert REST APIs. Certain customers experienced difficulties with alert searches and page loading, particularly on alert-related pages. This incident was initiated by an EBS volume upgrade conducted within the cloud-based managed ElasticSearch clusters. Our automated monitoring systems identified the incident within minutes, and it was resolved after 24 hours and 43 minutes by manually implementing vertical and horizontal scaling measures. ### **IMPACT** Between September 10, 2025, 13:56 UTC and September 11, 2025, 14:40 UTC, some customers in the U.S. region experienced degraded performance in Jira Service Management, Opsgenie, and Compass Cloud. During this time, web and mobile applications, as well as the Alert REST APIs, were impacted. Some customers may have seen issues with alert searches and slow loading of alert pages. During the incident, 22% of customers in the US region experienced failures in web API functionality, 8.6% encountered failures with the REST Alert API, and 1.3% experienced delays in notification delivery. Importantly, there was no loss of data during this event. ### **ROOT CAUSE** The degradation was caused by an EBS volume upgrade in the cloud-based managed ElasticSearch clusters, which necessitated a Blue/Green deployment strategy. One of the ElasticSearch nodes approached its shard size threshold, prompting the upgrade and subsequent deployment. This deployment resulted in elevated latency, increased 4xx HTTP response codes, and timeouts affecting both search and indexing operations. Recovery time exceeded expectations due to the prolonged blue/green deployment. After completion, the ElasticSearch cluster remained unhealthy and did not return to its normal state. Additionally, the switchover to the backup region failed because it was configured similarly in size and setup to the primary cluster. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages can affect your productivity. We are prioritizing the following improvement actions to help prevent similar incidents in the future: * Increase ElasticSearch cluster capacity and optimize settings to handle peak search loads efficiently. * Strengthen our high availability \(HA\) and failover architecture to ensure rapid and reliable recovery in the event of primary region failures. * Optimize cluster upgrade and shard rebalancing strategies to prevent similar issues. We apologize to customers whose services were impacted during this incident. We are taking steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   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.

3. identified Sep 10, 2025, 12:55 AM UTC

   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.

4. identified Sep 10, 2025, 06:35 PM UTC

   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.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   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.

6. resolved Sep 15, 2025, 06:40 AM UTC

   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.

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   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.

3. identified Sep 10, 2025, 12:55 AM UTC

   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.

4. identified Sep 10, 2025, 06:35 PM UTC

   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.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   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.

6. resolved Sep 15, 2025, 06:40 AM UTC

   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.

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   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.

3. identified Sep 10, 2025, 12:55 AM UTC

   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.

4. identified Sep 10, 2025, 06:35 PM UTC

   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.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   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.

6. resolved Sep 15, 2025, 06:40 AM UTC

   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.

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   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.

3. identified Sep 10, 2025, 12:55 AM UTC

   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.

4. identified Sep 10, 2025, 06:35 PM UTC

   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.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   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.

6. resolved Sep 15, 2025, 06:40 AM UTC

   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.

Read the full incident report →

Started Sep 09, 2025, 10:23 AM UTC· resolved Sep 15, 2025, 06:40 AM UTC

1. investigating Sep 09, 2025, 10:23 AM UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified Sep 09, 2025, 11:40 AM UTC

   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.

3. identified Sep 10, 2025, 12:55 AM UTC

   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.

4. identified Sep 10, 2025, 06:35 PM UTC

   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.

5. monitoring Sep 10, 2025, 08:34 PM UTC

   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.

6. resolved Sep 15, 2025, 06:40 AM UTC

   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.

Read the full incident report →

Started Sep 08, 2025, 05:20 AM UTC· resolved Sep 08, 2025, 03:45 PM UTC

1. resolved Sep 08, 2025, 09:46 PM UTC

   From 5:20AM to 3:45PM UTC today some customers using the Loom Chrome Extension experienced issues with recording. Looms recorded during this time may show up in the library but will not be playable. Unfortunately we are unable to recover these videos. If you are still experiencing this issue please make sure you are recording with extension version 5.5.121.

Read the full incident report →

Started Aug 27, 2025, 07:39 PM UTC· resolved Aug 27, 2025, 09:12 PM UTC

1. investigating Aug 27, 2025, 07:39 PM UTC

   We're receiving reports of connectivity problems while accessing Trello. You may see a "You are disconnected from Trello message" in the bottom left corner of your window notifying you that you've been disconnected. We're currently investigating the cause, and will post updates here as we determine it.

2. monitoring Aug 27, 2025, 09:01 PM UTC

   We are now seeing recovery and monitoring.

3. resolved Aug 27, 2025, 09:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 26, 2025, 03:06 PM UTC· resolved Aug 27, 2025, 03:25 PM UTC

1. investigating Aug 26, 2025, 03:06 PM UTC

   We are currently investigating this issue.

2. investigating Aug 26, 2025, 03:07 PM UTC

   Core daily job run id : scheduled__2025-08-24T04:00:00+00:00 has been running for over 30 hrs and all the downstream jobs have failed core daily Aug 25th run has not started yet.

3. resolved Aug 27, 2025, 03:25 PM UTC

   issue resloved pipeline is completed.

Read the full incident report →

Started Aug 20, 2025, 07:30 AM UTC· resolved Aug 20, 2025, 03:16 PM UTC

1. investigating Aug 20, 2025, 11:28 AM UTC

   - Bitbucket Cloud is investigating an incident affecting Git clone reliability. - The team is investigating the root cause and will update as soon as possible.

2. monitoring Aug 20, 2025, 01:24 PM UTC

   A root cause has been identified and a mitigation has been implemented; we're monitoring the situation.

3. resolved Aug 20, 2025, 03:16 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Aug 19, 2025, 02:27 PM UTC· resolved Aug 19, 2025, 03:22 PM UTC

1. investigating Aug 19, 2025, 02:27 PM UTC

   We are currently investigating the issue further.

2. monitoring Aug 19, 2025, 02:41 PM UTC

   Website functionality has recovered and we are monitoring to ensure no further regressions

3. resolved Aug 19, 2025, 03:22 PM UTC

   Bitbucket Cloud is fully recovered.

Read the full incident report →

Started Aug 15, 2025, 07:35 PM UTC· resolved Aug 15, 2025, 07:58 PM UTC

1. identified Aug 15, 2025, 07:35 PM UTC

   We are investigating reports of issues for Loom customers. Including names showing as IDs. We will provide more details once we identify the cause.

2. monitoring Aug 15, 2025, 07:50 PM UTC

   We have identified the cause of the issues and we are monitoring recovery.

3. resolved Aug 15, 2025, 07:58 PM UTC

   Between 18:45 and 19:35 UTC we experienced degraded functionality for Loom. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Aug 07, 2025, 10:25 PM UTC· resolved Aug 08, 2025, 12:18 PM UTC

1. investigating Aug 07, 2025, 10:25 PM UTC

   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.

2. identified Aug 07, 2025, 11:57 PM UTC

   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.

3. identified Aug 08, 2025, 05:08 AM UTC

   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.

4. identified Aug 08, 2025, 09:16 AM UTC

   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.

5. resolved Aug 08, 2025, 12:18 PM UTC

   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.

Read the full incident report →

Started Aug 07, 2025, 10:25 PM UTC· resolved Aug 08, 2025, 12:18 PM UTC

1. investigating Aug 07, 2025, 10:25 PM UTC

   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.

2. identified Aug 07, 2025, 11:57 PM UTC

   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.

3. identified Aug 08, 2025, 05:08 AM UTC

   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.

4. identified Aug 08, 2025, 09:16 AM UTC

   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.

5. resolved Aug 08, 2025, 12:18 PM UTC

   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.

Read the full incident report →

Started Aug 05, 2025, 01:55 PM UTC· resolved Aug 05, 2025, 02:35 PM UTC

1. resolved Aug 05, 2025, 03:03 PM UTC

   Today, between 13:55 and 14:35 UTC, we experienced a degradation on Bitbucket cloud, which impacted access to the website. This issue has been resolved, and services are now operating normally for all affected customers. We will monitor it closely to ensure stability

Read the full incident report →

Started Aug 04, 2025, 11:44 PM UTC· resolved Aug 05, 2025, 04:19 AM UTC

1. investigating Aug 04, 2025, 11:44 PM UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email notifications are currently impacted.

2. resolved Aug 05, 2025, 04:19 AM UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.

Read the full incident report →

Started Aug 04, 2025, 11:44 PM UTC· resolved Aug 05, 2025, 04:19 AM UTC

1. investigating Aug 04, 2025, 11:44 PM UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email notifications are currently impacted.

2. resolved Aug 05, 2025, 04:19 AM UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.

Read the full incident report →

Started Aug 04, 2025, 11:44 PM UTC· resolved Aug 05, 2025, 04:19 AM UTC

1. investigating Aug 04, 2025, 11:44 PM UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email notifications are currently impacted.

2. resolved Aug 05, 2025, 04:19 AM UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users that were impacted by this issue, re-submitting their invitation will also re-send the email to them if required.

Read the full incident report →

Started Aug 01, 2025, 08:16 AM UTC· resolved Aug 01, 2025, 09:22 AM UTC

1. investigating Aug 01, 2025, 08:16 AM UTC

   We are investigating reports of intermittent errors for some Atlassian Bitbucket Cloud customers. We will provide more details once we identify the root cause.

2. resolved Aug 01, 2025, 09:22 AM UTC

   Between 08:00UTC to 09:00UTC, we experienced degraded performance with push and clone operations for Atlassian Bitbucket. The issue has been resolved and the service is operating normally.

Read the full incident report →

Started Jul 30, 2025, 09:05 AM UTC· resolved Jul 30, 2025, 09:05 AM UTC

1. resolved Jul 30, 2025, 09:05 AM UTC

   This incident has been resolved and services are operating normally.

Read the full incident report →

Started Jul 30, 2025, 07:16 AM UTC· resolved Jul 30, 2025, 08:13 AM UTC

1. investigating Jul 30, 2025, 07:16 AM UTC

   We are currently investigating this issue.

2. resolved Jul 30, 2025, 08:13 AM UTC

   We have resolved this incident.

Read the full incident report →

Started Jul 30, 2025, 07:10 AM UTC· resolved Jul 30, 2025, 07:31 AM UTC

1. investigating Jul 30, 2025, 07:10 AM UTC

   We are investigating an issue causing a degraded experience when adding attachments or accessing existing media content.

2. resolved Jul 30, 2025, 07:31 AM UTC

   We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation.

Read the full incident report →

Started Jul 30, 2025, 07:10 AM UTC· resolved Jul 30, 2025, 07:31 AM UTC

1. investigating Jul 30, 2025, 07:10 AM UTC

   We are investigating an issue causing a degraded experience when adding attachments or accessing existing media content.

2. resolved Jul 30, 2025, 07:31 AM UTC

   We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation.

Read the full incident report →