Organization administrators can now receive personalized incident information in Atlassian Administration. Subscribe to System Health (currently in Beta) to receive notifications if a reliability incident affects your organization.
Subscribe to UpdatesSubscribe
Get email notifications whenever Jira creates, updates or resolves an incident.
Get text message notifications whenever Jira creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Jira creates an incident, updates an incident, resolves an incident or changes a component status.
All Systems Operational
About This Site
Here we will post updates about Jira's service availability. For status information about other Atlassian products or services, please visit the Atlassian status page.
Viewing content
Operational
Create and edit
Operational
Authentication and User Management
Operational
Search
Operational
Notifications
Operational
Administration
Operational
Marketplace
Operational
Mobile
Operational
Purchasing & Licensing
Operational
Signup
Operational
Automation for Jira
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Feb 20, 2026
Resolved -
This issue has been resolved and all services are functional.
Feb 20, 12:26 UTC
Feb 20, 12:26 UTC
Update -
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 12:26 UTC
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 12:26 UTC
Update -
We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 07:13 UTC
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 07:13 UTC
Update -
Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours as we continue our investigation.
Feb 20, 04:14 UTC
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours as we continue our investigation.
Feb 20, 04:14 UTC
Update -
Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately.
We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
Feb 20, 02:52 UTC
We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
Feb 20, 02:52 UTC
Update -
Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We anticipate next update to be posted in approximately 8 hours.
Feb 19, 21:04 UTC
We anticipate next update to be posted in approximately 8 hours.
Feb 19, 21:04 UTC
Update -
We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 18:56 UTC
We will continue to share additional updates here as more information is available.
Feb 19, 18:56 UTC
Identified -
Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
Feb 19, 17:34 UTC
Feb 19, 17:34 UTC
Update -
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 17:14 UTC
We will continue to share additional updates here as more information is available.
Feb 19, 17:14 UTC
Investigating -
We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites.
We will share updates here as more information is available.
Feb 19, 16:44 UTC
We will share updates here as more information is available.
Feb 19, 16:44 UTC
Feb 19, 2026
Resolved -
This issue is resolved. In our monitoring no other unexpected issues were seen.
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
Feb 19, 08:04 UTC
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
Feb 19, 08:04 UTC
Update -
This issue is resolved. In our monitoring no other unexpected issues were seen.
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
Feb 19, 08:04 UTC
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
Feb 19, 08:04 UTC
Monitoring -
Our team has resolved the permission errors relating to this incident across all Apps, and we will continue to monitor for any unexpected issues.
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
We'll provide another update within 24 hours on the results of our monitoring.
Feb 19, 00:51 UTC
For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.
We'll provide another update within 24 hours on the results of our monitoring.
Feb 19, 00:51 UTC
Update -
Our team is continuing to work on correcting the impact from this issue. A tested and validated process is now running to restore affected apps and our team is closely monitoring traffic to help to rule out any issues.
Please raise a support request if you require further assistance.
An update will be provided within 72 hours with our status on the backfill operation and estimated time to completion.
Feb 17, 05:40 UTC
Please raise a support request if you require further assistance.
An update will be provided within 72 hours with our status on the backfill operation and estimated time to completion.
Feb 17, 05:40 UTC
Update -
Our teams have identified customers that are actively experiencing issues relating to loss of access to their apps, and we are progressively rolling out a fix to these customers with urgency.
We will provide further update within 24 hours or sooner if available.
Feb 16, 05:30 UTC
We will provide further update within 24 hours or sooner if available.
Feb 16, 05:30 UTC
Update -
Impact
Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services. Approximately 17,168 clients could be potentially affected, involving several cloud instances. The incident has resulted in 2LO permissions being incorrectly enabled, causing potential access issues. Some customers may notice unauthorized system users in their directories, which currently pose no identified security risk.
Current Status
The short term fix involving Workspace ARI's will be rolled out cautiously over today and should resolve some highly impacted installations.
Full restoration via backfill scripts is being developed, though this will at least take the remainder of the week to cautiously roll out to production.
Next Steps
The backfill process for a permanent data correction is set to begin, with rigorous monitoring planned to observe system behavior.
New communication updates are scheduled to occur within the next 12 hours, or sooner if significant developments arise.
If you believe that you are impacted by this incident, and need assistance, then we recommend raising a support ticket.
Feb 16, 00:24 UTC
Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services. Approximately 17,168 clients could be potentially affected, involving several cloud instances. The incident has resulted in 2LO permissions being incorrectly enabled, causing potential access issues. Some customers may notice unauthorized system users in their directories, which currently pose no identified security risk.
Current Status
The short term fix involving Workspace ARI's will be rolled out cautiously over today and should resolve some highly impacted installations.
Full restoration via backfill scripts is being developed, though this will at least take the remainder of the week to cautiously roll out to production.
Next Steps
The backfill process for a permanent data correction is set to begin, with rigorous monitoring planned to observe system behavior.
New communication updates are scheduled to occur within the next 12 hours, or sooner if significant developments arise.
If you believe that you are impacted by this incident, and need assistance, then we recommend raising a support ticket.
Feb 16, 00:24 UTC
Update -
Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday.
We will provide the next update on Monday, Feb 16, 2026.
Feb 13, 07:41 UTC
We will provide the next update on Monday, Feb 16, 2026.
Feb 13, 07:41 UTC
Identified -
We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.
Feb 12, 22:29 UTC
Feb 12, 22:29 UTC
Update -
Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.
Feb 12, 14:33 UTC
Feb 12, 14:33 UTC
Investigating -
We are investigating an issue with Increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.
We will continue to share additional updates here as more information is available.
Forge and Connect apps are not affected.
Feb 12, 10:44 UTC
We will continue to share additional updates here as more information is available.
Forge and Connect apps are not affected.
Feb 12, 10:44 UTC
Feb 18, 2026
Resolved -
We have implemented the fix and the group page in the Admin Hub is now functioning as expected.
Feb 18, 11:30 UTC
Feb 18, 11:30 UTC
Monitoring -
We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.
Feb 18, 11:28 UTC
Feb 18, 11:28 UTC
Investigating -
Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com.
We are currently investigating the problem. Next update will be shared in 60 mins or sooner.
Feb 18, 10:57 UTC
We are currently investigating the problem. Next update will be shared in 60 mins or sooner.
Feb 18, 10:57 UTC
Feb 17, 2026
Feb 16, 2026
Feb 15, 2026
No incidents reported.
Feb 14, 2026
No incidents reported.
Feb 13, 2026
Feb 12, 2026
Feb 11, 2026
No incidents reported.
Feb 10, 2026
No incidents reported.
Feb 9, 2026
No incidents reported.
Feb 8, 2026
No incidents reported.
Feb 7, 2026
Resolved -
On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Feb 7, 05:38 UTC
Feb 7, 05:38 UTC
Monitoring -
The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Feb 7, 05:28 UTC
Feb 7, 05:28 UTC
Update -
Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
Feb 7, 03:43 UTC
Feb 7, 03:43 UTC
Update -
Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.
Feb 7, 02:22 UTC
Feb 7, 02:22 UTC
Update -
Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.
Feb 6, 22:33 UTC
Feb 6, 22:33 UTC
Update -
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 6, 20:26 UTC
We will continue to share additional updates here as more information is available.
Feb 6, 20:26 UTC
Update -
Impact
The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.
Current Status
Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.
Next Steps
The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
Feb 6, 20:24 UTC
The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.
Current Status
Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.
Next Steps
The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
Feb 6, 20:24 UTC
Identified -
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 6, 20:24 UTC
We will continue to share additional updates here as more information is available.
Feb 6, 20:24 UTC
Feb 6, 2026