Increased error rates on Jira and Jira Service Management Ecosystem Apps

Update timeline

1. investigating Feb 12, 2026, 10:44 AM UTC

   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.

2. investigating Feb 12, 2026, 02:33 PM UTC

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

3. identified Feb 12, 2026, 10:29 PM UTC

   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.

4. identified Feb 13, 2026, 07:41 AM UTC

   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.

5. identified Feb 16, 2026, 12:24 AM UTC

   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.

6. identified Feb 16, 2026, 05:30 AM UTC

   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.

7. identified Feb 17, 2026, 05:40 AM UTC

   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.

8. monitoring Feb 19, 2026, 12:51 AM UTC

   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.

9. monitoring Feb 19, 2026, 08:04 AM UTC

   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.

10. resolved Feb 19, 2026, 08:04 AM UTC

    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.