Jira Status

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.

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.

Monitoring: 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.

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.

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

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

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

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

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.

Investigating: Our teams are in the final stages of mitigation. We will continue to share additional updates here as more information is available.

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.

Resolved: We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Monitoring: We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

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.

Resolved: This issue has been resolved and all services are functional.

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

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

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

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

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

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

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.

Investigating: 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.

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.