Atlassian Outage History

Started Feb 20, 2026, 07:13 AM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

2. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

3. resolved Feb 20, 2026, 12:26 PM UTC

   This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 20, 2026, 04:14 AM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. identified Feb 20, 2026, 04:14 AM UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

2. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

3. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

4. resolved Feb 20, 2026, 12:26 PM UTC

   This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 20, 2026, 02:52 AM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. identified Feb 20, 2026, 02:52 AM UTC

   Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC

2. identified Feb 20, 2026, 04:14 AM UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

3. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

4. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

5. resolved Feb 20, 2026, 12:26 PM UTC

   This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 20, 2026, 02:52 AM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. identified Feb 20, 2026, 02:52 AM UTC

   Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue. Feb 20, 2026 - 02:52 UTC Please see prior notifications relating to this incident below: Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours. Feb 19, 2026 - 21:04 UTC Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 18:56 UTC Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. Feb 19, 2026 - 17:34 UTC Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available. Feb 19, 2026 - 17:14 UTC Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available. Feb 19, 2026 - 16:44 UTC

2. identified Feb 20, 2026, 04:14 AM UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

3. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

4. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

5. resolved Feb 20, 2026, 12:26 PM UTC

   This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 19, 2026, 04:44 PM UTC· resolved Feb 20, 2026, 12:26 PM UTC

1. investigating Feb 19, 2026, 04:44 PM UTC

   We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites. We will share updates here as more information is available.

2. investigating Feb 19, 2026, 05:14 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.

3. identified Feb 19, 2026, 05:34 PM UTC

   Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.

4. identified Feb 19, 2026, 06:56 PM UTC

   We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites. We will continue to share additional updates here as more information is available.

5. identified Feb 19, 2026, 09:04 PM UTC

   Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites. We anticipate next update to be posted in approximately 8 hours.

6. identified Feb 20, 2026, 02:52 AM UTC

   Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately. We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.

7. identified Feb 20, 2026, 04:14 AM UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours as we continue our investigation.

8. identified Feb 20, 2026, 07:13 AM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

9. identified Feb 20, 2026, 12:26 PM UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be posted within 6 hours or sooner based on significant progress.

10. resolved Feb 20, 2026, 12:26 PM UTC

    This issue has been resolved and all services are functional.

Read the full incident report →

Started Feb 19, 2026, 03:44 PM UTC· resolved Feb 19, 2026, 05:47 PM UTC

1. monitoring Feb 19, 2026, 03:44 PM UTC

   We have received and investigated reports of a partial service disruption affecting Confluence Cloud for some customers in AP South, APSE, APSE2, East, and Central. The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

2. resolved Feb 19, 2026, 05:47 PM UTC

   On February 19 2026, affected Confluence Cloud users may have experienced some service disruption in AP South, APSE, APSE2, East, and Central regions. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 19, 2026, 03:06 PM UTC· resolved Feb 19, 2026, 03:22 PM UTC

1. investigating Feb 19, 2026, 03:06 PM UTC

   We are actively investigating reports of performance degradation affecting Trello. We will share updates here as more information is available.

2. monitoring Feb 19, 2026, 03:10 PM UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

3. resolved Feb 19, 2026, 03:22 PM UTC

   On February 19, 2026, Trello users may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 18, 2026, 11:28 AM UTC· resolved Feb 18, 2026, 11:30 AM UTC

1. monitoring Feb 18, 2026, 11:28 AM UTC

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

2. resolved Feb 18, 2026, 11:30 AM UTC

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

Read the full incident report →

Started Feb 18, 2026, 11:28 AM UTC· resolved Feb 18, 2026, 11:30 AM UTC

1. monitoring Feb 18, 2026, 11:28 AM UTC

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

2. resolved Feb 18, 2026, 11:30 AM UTC

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

Read the full incident report →

Started Feb 18, 2026, 10:57 AM UTC· resolved Feb 18, 2026, 11:30 AM UTC

1. investigating Feb 18, 2026, 10:57 AM UTC

   Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next update will be shared in 60 mins or sooner.

2. monitoring Feb 18, 2026, 11:28 AM UTC

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

3. resolved Feb 18, 2026, 11:30 AM UTC

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

Read the full incident report →

Started Feb 18, 2026, 10:57 AM UTC· resolved Feb 18, 2026, 11:30 AM UTC

1. investigating Feb 18, 2026, 10:57 AM UTC

   Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next update will be shared in 60 mins or sooner.

2. monitoring Feb 18, 2026, 11:28 AM UTC

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

3. resolved Feb 18, 2026, 11:30 AM UTC

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

Read the full incident report →

Started Feb 16, 2026, 11:24 AM UTC· resolved Feb 19, 2026, 05:12 PM UTC

1. investigating Feb 16, 2026, 11:24 AM UTC

   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.

2. identified Feb 16, 2026, 11:27 AM UTC

   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.

3. resolved Feb 19, 2026, 05:12 PM UTC

   We have now reactivated all subscriptions that were previously cancelled. Impacted users may have received email notifications confirming this change. There has been no impact to the functioning of the app, it should continue to work as expected. To help prevent any future interruptions, we kindly request that billing admins ensure a valid billing payment method is added before the next billing cycle. We apologise for any confusion and appreciate your understanding.

Read the full incident report →

Started Feb 13, 2026, 07:41 AM UTC· resolved Feb 19, 2026, 08:04 AM UTC

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

   Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday. We will provide the next update on Monday, Feb 16, 2026.

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

   Impact Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services. Approximately 17,168 clients could be potentially affected, involving several cloud instances. The incident has resulted in 2LO permissions being incorrectly enabled, causing potential access issues. Some customers may notice unauthorized system users in their directories, which currently pose no identified security risk. Current Status The short term fix involving Workspace ARI's will be rolled out cautiously over today and should resolve some highly impacted installations. Full restoration via backfill scripts is being developed, though this will at least take the remainder of the week to cautiously roll out to production. Next Steps The backfill process for a permanent data correction is set to begin, with rigorous monitoring planned to observe system behavior. New communication updates are scheduled to occur within the next 12 hours, or sooner if significant developments arise. If you believe that you are impacted by this incident, and need assistance, then we recommend raising a support ticket.

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

   Our teams have identified customers that are actively experiencing issues relating to loss of access to their apps, and we are progressively rolling out a fix to these customers with urgency. We will provide further update within 24 hours or sooner if available.

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

   Our team is continuing to work on correcting the impact from this issue. A tested and validated process is now running to restore affected apps and our team is closely monitoring traffic to help to rule out any issues. Please raise a support request if you require further assistance. An update will be provided within 72 hours with our status on the backfill operation and estimated time to completion.

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

   Our team has resolved the permission errors relating to this incident across all Apps, and we will continue to monitor for any unexpected issues. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual. We'll provide another update within 24 hours on the results of our monitoring.

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

   This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

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

   This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

Read the full incident report →

Started Feb 13, 2026, 05:44 AM UTC· resolved Feb 13, 2026, 07:54 AM UTC

1. investigating Feb 13, 2026, 05:44 AM UTC

   We are investigating an issue with Rovo Dev components not properly starting that is impacting all Rovo Dev customers. We will provide more details within the next hour.

2. identified Feb 13, 2026, 06:30 AM UTC

   Our team has identified a potential root cause for this issue and is now working urgently to put a mitigation in place. We will provide an update within an hour.

3. monitoring Feb 13, 2026, 07:00 AM UTC

   We have identified the root cause of the errors and have mitigated the problem. We are now monitoring closely to ensure performance is fully restored

4. resolved Feb 13, 2026, 07:54 AM UTC

   This issue has been resolved and Rovo Dev is now working as expected.

Read the full incident report →

Started Feb 12, 2026, 10:44 AM UTC· resolved Feb 19, 2026, 08:04 AM UTC

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

   We are investigating an issue with Increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps. We will continue to share additional updates here as more information is available. Forge and Connect apps are not affected.

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

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

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

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased error rates on APIs in Jira and Jira Service Management Ecosystem Apps.

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

   Our teams identified two fix paths: a quick fix and a longer, time-consuming fix. We will test the quick fix over the weekend and, if no issues arise, implement it on Monday. We will provide the next update on Monday, Feb 16, 2026.

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

   Impact Ecosystem, Jira, and Jira Service Management customers might experience API call failures when using OAuth 2.0 apps, receiving 'The app is not installed on this instance' errors. The incident is attributed to OAuth scope mismatches between different internal services. Approximately 17,168 clients could be potentially affected, involving several cloud instances. The incident has resulted in 2LO permissions being incorrectly enabled, causing potential access issues. Some customers may notice unauthorized system users in their directories, which currently pose no identified security risk. Current Status The short term fix involving Workspace ARI's will be rolled out cautiously over today and should resolve some highly impacted installations. Full restoration via backfill scripts is being developed, though this will at least take the remainder of the week to cautiously roll out to production. Next Steps The backfill process for a permanent data correction is set to begin, with rigorous monitoring planned to observe system behavior. New communication updates are scheduled to occur within the next 12 hours, or sooner if significant developments arise. If you believe that you are impacted by this incident, and need assistance, then we recommend raising a support ticket.

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

   Our teams have identified customers that are actively experiencing issues relating to loss of access to their apps, and we are progressively rolling out a fix to these customers with urgency. We will provide further update within 24 hours or sooner if available.

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

   Our team is continuing to work on correcting the impact from this issue. A tested and validated process is now running to restore affected apps and our team is closely monitoring traffic to help to rule out any issues. Please raise a support request if you require further assistance. An update will be provided within 72 hours with our status on the backfill operation and estimated time to completion.

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

   Our team has resolved the permission errors relating to this incident across all Apps, and we will continue to monitor for any unexpected issues. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual. We'll provide another update within 24 hours on the results of our monitoring.

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

   This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

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

    This issue is resolved. In our monitoring no other unexpected issues were seen. For customers still experiencing errors, this may indicate a legitimate permission configuration issue on your side and should be investigated as usual.

Read the full incident report →

Started Feb 09, 2026, 08:20 AM UTC· resolved Feb 09, 2026, 08:36 AM UTC

1. monitoring Feb 09, 2026, 08:20 AM UTC

   Trello performance was degraded and the performance degradation of Trello has been resolved. All the services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

2. resolved Feb 09, 2026, 08:36 AM UTC

   Trello users experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

3. postmortem Feb 18, 2026, 08:33 AM UTC

   ### **Summary** On Feb 9, 2026, between 07:12 UTC and 08:05 UTC, Atlassian customers were unable to access Trello. The event was triggered by Trello servers reaching maximum memory limits and a subsequent failure to automatically scale for the traffic. The incident was detected within 5 minutes by automated monitoring systems, engaging Trello teams for resolution. Two parallel mitigation efforts were undertaken to restore access: 1\) manual scaling to address concerns with high utilization of hosts, and 2\) temporarily limiting traffic from free customers. This intervention put Trello systems in a known good state with a total time to resolution of ~53 minutes. ### **IMPACT** The overall impact occurred on Feb 9, 2026 between 07:12 AM UTC and 08:05 AM UTC for Trello customers and caused service disruption for all customers, making Trello inaccessible during that time. Access was restored for paid users approximately 43 minutes after the onset, with full service restoration for free users 10 minutes later. ### **ROOT CAUSE** The issue was cause by increased memory requirements during the transition from the weekend to EU business hours, combined with Auto Scaling group scaling rules based on CPU utilization. Memory allocation on our instances outpaced the CPU usage, which caused processes to hit Out-Of-Memory \(OOM\) errors and crash before reaching CPU usage thresholds that would trigger the auto scaling policies. As a result, Trello went down and users received HTTP 502 errors until the incident was resolved. ### **REMEDIAL ACTION PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a suite of automated infrastructure management in place, this specific issue required manual intervention to restore Trello access to users. To avoid repeating this type of incident, we are prioritizing the following remedial action items: * Pre-scale capacity before EU morning traffic - This change has already been introduced to prevent further incidents while we implement additional safeguards. * Adjust Trello’s Auto Scaling group settings - This change will ensure that unhealthy hosts will be replaced more rapidly and scaling policies will consider memory usage. * Refine Trello host memory commitments - This change will decrease the likelihood of memory overcommitment on hosts and associated OOM errors. * Increase isolation for OOM errors - This change will improve the ability for hosts to recover in the event of a single worker experiencing an OOM error. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Feb 06, 2026, 08:24 PM UTC· resolved Feb 07, 2026, 05:38 AM UTC

1. identified Feb 06, 2026, 08:24 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

2. identified Feb 06, 2026, 08:24 PM UTC

   Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

3. identified Feb 06, 2026, 08:26 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 06, 2026, 10:33 PM UTC

   Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

5. identified Feb 07, 2026, 02:22 AM UTC

   Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

6. identified Feb 07, 2026, 03:43 AM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

7. monitoring Feb 07, 2026, 05:28 AM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

8. resolved Feb 07, 2026, 05:38 AM UTC

   On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 06, 2026, 08:24 PM UTC· resolved Feb 07, 2026, 05:38 AM UTC

1. identified Feb 06, 2026, 08:24 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

2. identified Feb 06, 2026, 08:24 PM UTC

   Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

3. identified Feb 06, 2026, 08:26 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 06, 2026, 10:33 PM UTC

   Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

5. identified Feb 07, 2026, 02:22 AM UTC

   Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

6. identified Feb 07, 2026, 03:43 AM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

7. monitoring Feb 07, 2026, 05:28 AM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

8. resolved Feb 07, 2026, 05:38 AM UTC

   On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 06, 2026, 08:24 PM UTC· resolved Feb 07, 2026, 05:38 AM UTC

1. identified Feb 06, 2026, 08:24 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

2. identified Feb 06, 2026, 08:24 PM UTC

   Impact The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption. Current Status Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible. Next Steps The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.

3. identified Feb 06, 2026, 08:26 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 06, 2026, 10:33 PM UTC

   Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.

5. identified Feb 07, 2026, 02:22 AM UTC

   Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

6. identified Feb 07, 2026, 03:43 AM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.

7. monitoring Feb 07, 2026, 05:28 AM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

8. resolved Feb 07, 2026, 05:38 AM UTC

   On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 06, 2026, 09:37 AM UTC· resolved Feb 06, 2026, 11:32 AM UTC

1. investigating Feb 06, 2026, 09:37 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue and working toward restoring full service. The team is focused on identifying the root cause and implementing a solution to resolve the incident. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

2. identified Feb 06, 2026, 10:39 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue. The issue is suspected to be related to a recent change that was deployed. The team is currently rolling back the changes. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

3. resolved Feb 06, 2026, 11:32 AM UTC

   Impact We are currently experiencing an issue affecting the Forge platform, specifically related to scheduled triggers. Users may encounter instances where these triggers are not executing as anticipated, disrupting the normal operation of their Forge apps. This behavior began approximately at 2 AM UTC. Current Status Our engineering team identified the root cause and performed a rollback deployment to resolve the issue.

Read the full incident report →

Started Feb 06, 2026, 01:47 AM UTC· resolved Feb 06, 2026, 08:01 PM UTC

1. investigating Feb 06, 2026, 01:47 AM UTC

   We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts. Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status. Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status. There is currently no action required from those customers that have incorrectly received these emails. We will provide further update within an hour as our effort continues.

2. identified Feb 06, 2026, 03:02 AM UTC

   During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period. Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status. We will provide further update within two hours or earlier if there is important information to share.

3. identified Feb 06, 2026, 05:57 AM UTC

   Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident. We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed.

4. identified Feb 06, 2026, 07:52 AM UTC

   Our team continues active testing of the fix to restore customer accounts affected by this incident. We will provide further update within two hours or sooner.

5. identified Feb 06, 2026, 10:25 AM UTC

   Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements. We will provide our next update in four hours, or sooner if we have meaningful progress to share.

6. monitoring Feb 06, 2026, 02:41 PM UTC

   The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free. We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts.

7. resolved Feb 06, 2026, 08:01 PM UTC

   The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.

Read the full incident report →

Started Feb 06, 2026, 01:47 AM UTC· resolved Feb 06, 2026, 08:01 PM UTC

1. investigating Feb 06, 2026, 01:47 AM UTC

   We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts. Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status. Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status. There is currently no action required from those customers that have incorrectly received these emails. We will provide further update within an hour as our effort continues.

2. identified Feb 06, 2026, 03:02 AM UTC

   During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period. Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status. We will provide further update within two hours or earlier if there is important information to share.

3. identified Feb 06, 2026, 05:57 AM UTC

   Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident. We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed.

4. identified Feb 06, 2026, 07:52 AM UTC

   Our team continues active testing of the fix to restore customer accounts affected by this incident. We will provide further update within two hours or sooner.

5. identified Feb 06, 2026, 10:25 AM UTC

   Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements. We will provide our next update in four hours, or sooner if we have meaningful progress to share.

6. monitoring Feb 06, 2026, 02:41 PM UTC

   The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free. We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts.

7. resolved Feb 06, 2026, 08:01 PM UTC

   The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.

Read the full incident report →

Started Feb 05, 2026, 02:13 PM UTC· resolved Feb 05, 2026, 09:38 PM UTC

1. investigating Feb 05, 2026, 02:13 PM UTC

   Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

2. identified Feb 05, 2026, 02:40 PM UTC

   Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

3. identified Feb 05, 2026, 03:39 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 05, 2026, 05:35 PM UTC

   Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

5. identified Feb 05, 2026, 07:22 PM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

6. monitoring Feb 05, 2026, 09:09 PM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

7. resolved Feb 05, 2026, 09:38 PM UTC

   On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 05, 2026, 02:13 PM UTC· resolved Feb 05, 2026, 09:38 PM UTC

1. investigating Feb 05, 2026, 02:13 PM UTC

   Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

2. identified Feb 05, 2026, 02:40 PM UTC

   Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

3. identified Feb 05, 2026, 03:39 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 05, 2026, 05:35 PM UTC

   Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

5. identified Feb 05, 2026, 07:22 PM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

6. monitoring Feb 05, 2026, 09:09 PM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

7. resolved Feb 05, 2026, 09:38 PM UTC

   On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 05, 2026, 02:13 PM UTC· resolved Feb 05, 2026, 09:38 PM UTC

1. investigating Feb 05, 2026, 02:13 PM UTC

   Some users in us-east-1 region might not be able to access Jira and JSM. We are aware of this issue and are actively investigating the same. We will provide update on the progress in next 60 minutes or sooner.

2. identified Feb 05, 2026, 02:40 PM UTC

   Some users in the us-east-1 region cannot access Jira and JSM. We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution. We will provide update on the progress in next 60 minutes or sooner.

3. identified Feb 05, 2026, 03:39 PM UTC

   We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.

4. identified Feb 05, 2026, 05:35 PM UTC

   Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region. We will continue to share additional updates here as more information is available.

5. identified Feb 05, 2026, 07:22 PM UTC

   Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation. We will continue to share additional updates here as more information is available.

6. monitoring Feb 05, 2026, 09:09 PM UTC

   The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.

7. resolved Feb 05, 2026, 09:38 PM UTC

   On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →