Atlassian Developer 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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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: Some Forge app billing admins may have received subscription cancellation emails, but we want to assure you that there is no disruption or impact to the functioning of your Forge apps, your apps will continue to operate as normal.

Our team is actively working to reactivate any affected subscriptions. To help prevent any future interruptions, we kindly request that admins ensure a valid billing payment method is added before the next billing cycle.

We apologise for any confusion and appreciate your understanding.

Investigating: Some Forge app billing admins may have received subscription cancellation emails, but we want to assure you that there is no disruption or impact to the functioning of your Forge apps, your apps will continue to operate as normal.

Our team is actively working to reactivate any affected subscriptions. To help prevent any future interruptions, we kindly request that admins ensure a valid billing payment method is added before the next billing cycle.

We apologise for any confusion and appreciate your understanding.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.