Duplicate issues being created in Jira Service Management and Jira
Monitoring - Affected customers who have Tempo installed; the script will be delayed as we await confirmation from Tempo on next steps.

For other affected customers, Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 17, 2025 - 13:37 UTC
Identified - The issue has been identified and a fix is being implemented.
Sep 17, 2025 - 13:33 UTC
Update - For the affected customers who have Tempo installed; the script will be delayed as we await confirmation from Tempo on next steps.

For other affected customers, Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 17, 2025 - 13:31 UTC
Update - Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 15, 2025 - 09:18 UTC
Update - Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 15, 2025 - 09:14 UTC
Update - Atlassian team is in the process of moving the worklogs back to the original issues.

Root cause of the issue was identified to a code change. To fix the issue, we had reverted the code change and the behaviour is back to normal.

We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 15, 2025 - 09:11 UTC
Update - Root cause of the issue was identified to a code change. To fix the issue, we have reverted the code change and we expect the behaviour to be back to normal.

Atlassian team is work on creating steps or a script to remove the duplicate issues created. We request our customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 11, 2025 - 16:10 UTC
Update - We are continuing to monitor for any further issues.
Sep 11, 2025 - 16:08 UTC
Monitoring - Root cause of the issue was identified to a code change. To fix the issue, we have reverted the code change and we expect the behaviour to be back to normal.

Atlassian team is working on creating steps or a script to remove the duplicate issues created. We request customers not to delete these duplicate issues on your own to avoid any other issues.
Sep 11, 2025 - 16:05 UTC
Update - We continue to work on resolving the cause of the duplicate issue creation in Jira Service Management and Jira. We have identified the root cause and expect recovery shortly.
Sep 11, 2025 - 10:31 UTC
Identified - We continue to work on resolving the cause of the duplicate issue creation in Jira Service Management and Jira. We have identified the root cause and expect recovery shortly.
Sep 11, 2025 - 10:30 UTC
Investigating - We are investigating the issue of duplicate issues being created in Jira Service Management and Jira.

The team is working on identifying and taking actions to mitigate the issue and minimize the impact.
Sep 11, 2025 - 09:39 UTC

About This Site

Here we will post updates about Jira Service Management's availability. For status information about other Atlassian products or services, please visit the Atlassian status page.

Jira Service Management Web ? Operational
Service Portal ? Operational
Opsgenie Incident Flow Operational
Opsgenie Alert Flow Operational
Opsgenie Incident Flow Operational
Opsgenie Alert Flow Operational
Jira Service Management Email Requests ? Operational
Authentication and User Management Operational
Purchasing & Licensing Operational
Signup Operational
Automation for Jira Operational
Assist ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Sep 18, 2025

No incidents reported today.

Sep 17, 2025

Unresolved incident: Duplicate issues being created in Jira Service Management and Jira.

Sep 16, 2025

No incidents reported.

Sep 15, 2025
Degraded performance in Confluence and Jira for Microsoft Edge users
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 15, 06:40 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 10, 20:34 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 10, 18:35 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 10, 00:55 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 9, 11:40 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.
Sep 9, 10:23 UTC
Sep 14, 2025

No incidents reported.

Sep 13, 2025

No incidents reported.

Sep 12, 2025

No incidents reported.

Sep 11, 2025
Delays observed at JSM, Opsgenie and Compass alert search functionality in US Region
Resolved - 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.
Sep 11, 18:45 UTC
Monitoring - 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.
Sep 11, 15:05 UTC
Update - 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.
Sep 11, 14:00 UTC
Update - 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.
Sep 11, 13:02 UTC
Update - 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.
Sep 11, 11:53 UTC
Update - 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.
Sep 11, 10:59 UTC
Update - 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.
Sep 11, 09:51 UTC
Update - 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.
Sep 11, 08:53 UTC
Update - 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.
Sep 11, 07:50 UTC
Update - 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.
Sep 11, 06:51 UTC
Update - 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.
Sep 11, 05:51 UTC
Update - 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.
Sep 11, 04:50 UTC
Update - 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.
Sep 11, 03:49 UTC
Update - 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.
Sep 11, 03:10 UTC
Update - 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.
Sep 11, 02:10 UTC
Update - 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.
Sep 11, 01:10 UTC
Update - 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.
Sep 11, 00:11 UTC
Update - Our team is still actively working to resolve the issue and making progress toward a resolution. Thank you for your patience.
Sep 10, 20:11 UTC
Update - We are continuing to work on a fix for the issue.
Sep 10, 18:01 UTC
Identified - 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.
Sep 10, 15:26 UTC
Investigating - 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.
Sep 10, 15:23 UTC
Duplicate issues being created in Jira Service Management and Jira
Resolved - Duplicated message. Please refer to the updates from this incident: https://jira-software.status.atlassian.com/incidents/knx11cj542ks
Sep 11, 09:45 UTC
Investigating - We are investigating the issue of duplicate issues being created in Jira Service Management and Jira.
The team is working on identifying and taking actions to mitigate the issue and minimize the impact.
Sep 11, 09:41 UTC
Sep 10, 2025
Sep 9, 2025
Disappearing 'account' filed for Tempo users
Resolved - Our team is now satisfied that the issues relating to these missing fields are now resolved.
Sep 9, 00:40 UTC
Monitoring - Our team has identified the root cause of this issue and has now put a fix in place to resolve this issue. We are continuing to monitor the situation and will provide further updates as available.
Sep 8, 23:59 UTC
Update - We are continuing to investigate this issue
Sep 8, 17:22 UTC
Update - All affected fields originate from Tempo(Vendor), we are consulting it now with them.
Sep 8, 12:46 UTC
Investigating - We are investigating cases of disappearing 'account' while trying to edit it. Account field is Tempo(Vendor) field. We are investigating the case and provide further informations
Sep 8, 10:55 UTC
Sep 8, 2025
Sep 7, 2025

No incidents reported.

Sep 6, 2025

No incidents reported.

Sep 5, 2025

No incidents reported.

Sep 4, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage