Atlassian Outage History

Started Jul 20, 2026, 08:18 PM UTC· resolved Jul 22, 2026, 12:56 AM UTC

1. investigating Jul 20, 2026, 08:18 PM UTC

   We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.

2. investigating Jul 20, 2026, 09:27 PM UTC

   Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.

3. identified Jul 21, 2026, 04:53 AM UTC

   The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.

4. resolved Jul 22, 2026, 12:56 AM UTC

   Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.

Read the full incident report →

Started Jul 13, 2026, 03:48 PM UTC· resolved Jul 13, 2026, 05:46 PM UTC

1. investigating Jul 13, 2026, 03:48 PM UTC

   Marketplace partner pages are unavailable. Partners are unable to access dashboards and management interfaces, experiencing timeouts when attempting to load these pages. All partner-related functionality is affected. Investigation into the underlying cause is underway. Next comms will be sent in 60 minutes or upon significant progress.

2. monitoring Jul 13, 2026, 05:17 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 Jul 13, 2026, 05:46 PM UTC

   On Jul 13, 2026, partner operations may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jul 06, 2026, 04:11 PM UTC· resolved Jul 06, 2026, 06:52 PM UTC

1. investigating Jul 06, 2026, 04:11 PM UTC

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

2. investigating Jul 06, 2026, 05:12 PM UTC

   We continue to investigate performance degradation affecting Automation for JIRA in Europe regions. We will share updates here as more information becomes available.

3. identified Jul 06, 2026, 05:57 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience performance degradation affecting Automation for JIRA in Europe regions. We will continue to share additional updates here as more information is available.

4. monitoring Jul 06, 2026, 06:41 PM UTC

   The performance degradation of Automation for JIRA in Europe regions has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.

5. resolved Jul 06, 2026, 06:52 PM UTC

   On July 6, 2026, some users in Europe regions may have experienced performance degradation with Automation for JIRA. The issue has now been resolved, and the service is operating normally for all affected customers. If you believe the issue continues to persist, please contact our Support team for further assistance and troubleshooting.

6. postmortem Jul 27, 2026, 06:57 AM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jul 06, 2026, 10:04 AM UTC· resolved Jul 06, 2026, 01:04 PM UTC

1. monitoring Jul 06, 2026, 10:04 AM UTC

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

2. investigating Jul 06, 2026, 11:46 AM UTC

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

3. monitoring Jul 06, 2026, 12:25 PM UTC

   We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

4. resolved Jul 06, 2026, 01:04 PM UTC

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

5. postmortem Jul 17, 2026, 04:59 PM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jul 06, 2026, 09:23 AM UTC· resolved Jul 06, 2026, 01:04 PM UTC

1. investigating Jul 06, 2026, 09:23 AM UTC

   We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. monitoring Jul 06, 2026, 10:04 AM UTC

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

3. investigating Jul 06, 2026, 11:46 AM UTC

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

4. monitoring Jul 06, 2026, 12:25 PM UTC

   We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

5. resolved Jul 06, 2026, 01:04 PM UTC

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

6. postmortem Jul 17, 2026, 04:59 PM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jul 06, 2026, 09:23 AM UTC· resolved Jul 06, 2026, 01:04 PM UTC

1. investigating Jul 06, 2026, 09:23 AM UTC

   We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. monitoring Jul 06, 2026, 10:04 AM UTC

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

3. investigating Jul 06, 2026, 11:46 AM UTC

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

4. monitoring Jul 06, 2026, 12:25 PM UTC

   We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

5. resolved Jul 06, 2026, 01:04 PM UTC

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

6. postmortem Jul 17, 2026, 04:59 PM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jul 06, 2026, 09:23 AM UTC· resolved Jul 06, 2026, 01:04 PM UTC

1. investigating Jul 06, 2026, 09:23 AM UTC

   We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. monitoring Jul 06, 2026, 10:04 AM UTC

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

3. investigating Jul 06, 2026, 11:46 AM UTC

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

4. monitoring Jul 06, 2026, 12:25 PM UTC

   We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

5. resolved Jul 06, 2026, 01:04 PM UTC

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

6. postmortem Jul 17, 2026, 04:59 PM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jul 06, 2026, 09:23 AM UTC· resolved Jul 06, 2026, 01:04 PM UTC

1. investigating Jul 06, 2026, 09:23 AM UTC

   We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. monitoring Jul 06, 2026, 10:04 AM UTC

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

3. investigating Jul 06, 2026, 11:46 AM UTC

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

4. monitoring Jul 06, 2026, 12:25 PM UTC

   We have applied the fix to mitigate the issue and are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

5. resolved Jul 06, 2026, 01:04 PM UTC

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

6. postmortem Jul 17, 2026, 04:59 PM UTC

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing the identity endpoint. In parallel, the elevated identity latency contributed to a cascading failure in a downstream user search service, degrading user search and user picker experiences across multiple products. Service was progressively restored after additional database read capacity was added, the emergency block was removed, and the user search service was manually scaled up. ## Impact The incident affected customers across multiple Atlassian products in EU regions on Jul 6, 2026 between 06:51 and 20:17 UTC. - **Core Identity service degradation:** elevated intermittent access denied rates were observed across products in EU regions. - **Automation rule execution failures:** automation rules using the default user (Automation for Jira) in Jira, Jira Service Management, and Jira Product Discovery in EU regions failed with a permissions error. - **User search and user picker failures:** user search success rates dropped significantly in EU regions, with user picker capability largely unavailable across products. ## Root Cause The incident originated from a recent configuration change that reduced the cache lifetime for a core identity service. As EU workday traffic ramped up on July 6, 2026, a larger share of requests began reaching the backing database directly rather than being served from cache. The EU databases did not have sufficient regional capacity to absorb the increased load, and database CPU reached saturation, causing elevated intermittent access denied rates. As part of the mitigation, an emergency block was applied to reduce load on the saturated identity service database and prioritize restoring the core identity service. This inadvertently prevented automation rules from passing their pre-execution permission checks, causing them to fail. The extended duration was primarily due to a secondary wave of automation rule failures caused by the processing limit throttling. In parallel, the sustained degradation caused increased latency and intermittent failures across products that depend on these checks, and contributed to a cascading failure in a downstream user search service. As a result, user search and user picker experiences became largely unavailable in EU regions until the permissions service recovered and the user search service was scaled up to restore capacity. ## Remedial Actions Plan & Next Steps We know outages impact customers' productivity. Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Improve safeguards for high-impact emergency mitigations:** Harden operational tooling so mitigation steps that could disable customer-facing workflows require additional review. - **Strengthen identity infrastructure capacity and change safety:** Review regional database sizing and capacity headroom to reduce the risk of saturation during peak traffic periods, and refine the assessment process for configuration changes so downstream load impact is evaluated before production rollout. - **Strengthen resilience against cascading failures from upstream degradation:** Audit backpressure handling, circuit breaker configuration, and autoscaling behavior in services, so that upstream degradation does not cause broader product impact across user search, user picker, and related experiences. - **Harden replay mechanisms for Automation rule failures:** Increase resilience of automation rules to reduce impact associated with incidents occurring in dependencies.. We recognize how critical reliable product workflows are for our customers, and we apologize to customers who were impacted by this incident. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 30, 2026, 02:45 AM UTC· resolved Jul 02, 2026, 04:43 AM UTC

1. investigating Jun 30, 2026, 02:45 AM UTC

   We are aware that some customers that are using the Time Tracker for Jira Cloud and DC app were incorrectly notified about the app converting to a free or a trial subscription. Our team is investigating this issue with urgency, and we will plan to notify any customers that received the incorrect email with a correction. There is no action required from those customers that have incorrectly received these emails. We apologize for any inconvenience this may have caused.

2. resolved Jul 02, 2026, 04:43 AM UTC

   All customers that had previously received the incorrect notifications about the Time Tracker for Jira Cloud and DC app should have received corrective communications at this time. We are now resolving this issue.

Read the full incident report →

Started Jun 26, 2026, 02:32 PM UTC· resolved Jun 26, 2026, 09:39 PM UTC

1. identified Jun 26, 2026, 02:32 PM UTC

   We have identified the source of service performance issues, affecting your forge remote-apps services. Our team has initiated a remediation and is actively monitoring recovery. We will provide the next update within the next one hour.

2. identified Jun 26, 2026, 03:28 PM UTC

   Our team has applied the mitigation, and we are seeing recovery. We will continue to share additional updates here as more information becomes available.

3. identified Jun 26, 2026, 07:43 PM UTC

   Our team continues to monitor the recovery in progress, and we will share additional updates here as more information becomes available.

4. monitoring Jun 26, 2026, 09:24 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.

5. resolved Jun 26, 2026, 09:39 PM UTC

   On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jun 19, 2026, 10:46 PM UTC· resolved Jun 26, 2026, 05:13 AM UTC

1. monitoring Jun 19, 2026, 10:46 PM UTC

   Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

2. resolved Jun 26, 2026, 05:13 AM UTC

   Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Started Jun 19, 2026, 10:46 PM UTC· resolved Jun 26, 2026, 05:13 AM UTC

1. monitoring Jun 19, 2026, 10:46 PM UTC

   Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

2. resolved Jun 26, 2026, 05:13 AM UTC

   Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Started Jun 19, 2026, 10:46 PM UTC· resolved Jun 26, 2026, 05:13 AM UTC

1. monitoring Jun 19, 2026, 10:46 PM UTC

   Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.

2. resolved Jun 26, 2026, 05:13 AM UTC

   Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.

Read the full incident report →

Started Jun 16, 2026, 01:46 PM UTC· resolved Jun 16, 2026, 03:56 PM UTC

1. investigating Jun 16, 2026, 01:46 PM UTC

   Our team is investigating degraded performance affecting your service. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

2. identified Jun 16, 2026, 02:28 PM UTC

   We have identified the source of degraded performance affecting some Confluence Cloud users. A subset of users may experience errors or slowness when viewing or editing pages. Our team has initiated a remediation and is actively monitoring recovery. We will provide another update within one hour or once the issue is fully resolved.

3. monitoring Jun 16, 2026, 02:53 PM UTC

   We have been able to apply the fix to mitigate the issue and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.

4. resolved Jun 16, 2026, 03:56 PM UTC

   On June 16, 2026, Confluence Cloud users for some customers may have experienced performance degradation of view and edit page experiences. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem Jun 23, 2026, 06:25 PM UTC

   ### Summary ### On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT ### The overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces. ### ROOT CAUSE ### 1. A database cluster within our infrastructure stopped responding to connection close requests. 2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer. 3. Hitting max connections on the cluster degraded query performance. 4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result. ### REMEDIAL ACTIONS PLAN & NEXT STEPS ### We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production. We have already deployed the following fix: - Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others. To minimize the impact of similar incidents in the future, we will implement additional preventative measures such as: - Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early. - Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._ Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 15, 2026, 06:48 AM UTC· resolved Jun 17, 2026, 05:00 PM UTC

1. investigating Jun 15, 2026, 06:48 AM UTC

   We are currently investigating reports of some users being unable to access Rovo Studio or remove apps from the Rovo access blocklist. Our teams are actively working to identify the cause and resolve the issue. We will provide a further update within one hour.

2. investigating Jun 15, 2026, 07:55 AM UTC

   Our teams continue to investigate the root cause of this issue. We have identified a workaround that can mitigate the impact while a permanent fix is implemented, expected within approximately 10 hours or sooner. We are proactively reaching out to affected customers with this interim solution. If you are experiencing a similar issue, please raise a support case for assistance.

3. identified Jun 15, 2026, 05:44 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a permanent fix. Affected customers may experience an inability to access Rovo Studio or to remove apps from the access blocklist. A workaround is available; affected customers can raise a support case and our team can restore access quickly. We'll share additional updates here at 18:00 UTC on June 16th, 2006, or as more information becomes available.

4. identified Jun 16, 2026, 05:45 PM UTC

   Our teams are continuing work on a permanent fix. Affected customers may experience an inability to access Rovo Studio or to remove apps from the access blocklist. A workaround is available; affected customers can raise a support case and our team can restore access quickly. We'll share additional updates here at 18:00 UTC on June 17th, 2026, or as more information becomes available.

5. monitoring Jun 17, 2026, 05:14 AM UTC

   Our teams have identified the root cause of this issue and implemented a fix. We are beginning to observe signs of recovery, with some users regaining the ability to access Rovo Studio and remove apps from the Rovo access blocklist. We are closely monitoring the situation to ensure stability and will provide a further update once full recovery is confirmed. If you require assistance in the meantime, please reach out to our support team.

6. resolved Jun 17, 2026, 05:00 PM UTC

   On June 15, 2026, affected Rovo users, for some customers, may have experienced a service disruption with the Rovo access blocklist, where they were unable to remove apps from the blocklist. The issue with the Rovo access blocklist has now been resolved, and the service is operating normally for affected customers. Customers can use the Rovo access page to unblock any app instances, including Studio: https://support.atlassian.com/organization-administration/docs/manage-rovo-access/ If you continue to experience any issues, please contact our support team by raising a ticket at https://support.atlassian.com/

Read the full incident report →

Started Jun 12, 2026, 01:50 PM UTC· resolved Jun 12, 2026, 02:29 PM UTC

1. monitoring Jun 12, 2026, 01:50 PM UTC

   We are investigating reports of incomplete or missing field data in Jira Product Discovery views, including list, timeline, and single idea views. A limited number of customers are affected. Your data is safe, this is a display issue only. We have identified the root cause and a fix is being deployed. We will provide an update once recovery is confirmed.

2. resolved Jun 12, 2026, 02:29 PM UTC

   On June 12th 2026, between 07:30 UTC to 13:48 UTC, some users experienced viewing disruptions with our product discovery service. The issue has now been resolved and the service is operating normally for all the customers.

Read the full incident report →

Started Jun 12, 2026, 07:39 AM UTC· resolved Jun 12, 2026, 11:15 AM UTC

1. investigating Jun 12, 2026, 07:39 AM UTC

   Users are experiencing experiencing degraded performance in Confluence Cloud affecting view page and edit page functionality. Our teams are actively investigating and will be sharing more updates in next 1 hour or sooner.

2. investigating Jun 12, 2026, 08:45 AM UTC

   Users are experiencing degraded performance with view content, create and edit functionality on Confluence Cloud primarily in the EU region. Our teams are actively working to identify the root cause of the issue. We will share additional updates in next 2 hours or sooner as more information is available.

3. identified Jun 12, 2026, 10:29 AM UTC

   Our teams have identified the root cause of this issue and implemented a fix. We are beginning to observe signs of recovery, with some affected users regaining access to view, create, and edit content on Confluence Cloud. We will provide a further update within one hour, or sooner if we confirm full recovery for all affected customers.

4. resolved Jun 12, 2026, 11:15 AM UTC

   On June 12th 2026, between 07:04 to 11:06 UTC, some Confluence users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all affected customers.

5. postmortem Jun 23, 2026, 06:28 PM UTC

   ### Summary On Jun 12, 2026, between 07:04 and 12:10 UTC and on Jun 16, 2026, between 12:56 and 14:35 UTC, a subset of Atlassian customers using Confluence Cloud experienced errors and degraded performance when attempting to view or edit pages. The event was triggered when a database cluster within our infrastructure stopped responding to connection close requests. This caused idle connections to accumulate rather than be released — resulting in increased memory pressure and cascading errors for users. The incident was detected by our automated monitoring within 18 minutes and mitigated by scaling database resources and redeploying, which recycled the idle connections. A permanent fix has since been developed and deployed. ### IMPACT The overall impact was between Jun 12, 2026 07:04 and 12:10 UTC and Jun 16, 2026 12:56 and 14:35 UTC on Confluence Cloud. The June 12 incident caused service disruption to a subset of customers in the EU region while the June 16 incident caused service disruption to a subset of customers in the US region. Impacted users experienced errors or degraded performance when attempting to view, edit, or access Confluence content and spaces. ‌ ### ROOT CAUSE ‌ 1. A database cluster within our infrastructure stopped responding to connection close requests. 2. Idle connections accumulated across clusters rather than being closed, creating a connection leak and increasing memory pressure on the database layer. 3. Hitting max connections on the cluster degraded query performance. 4. Users attempting to view or edit Confluence content experienced errors and slow load times as a result. ‌ ### REMEDIAL ACTIONS PLAN & NEXT STEPS ‌ We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific design limitation in our connection cleanup process was not identified until it was triggered by an adverse infrastructure condition in production. ‌ We have already deployed the following fix: * Redesigned the database connection cleanup process to prevent unresponsive connections from impacting the closure of others. To minimize the impact of similar incidents in the future, we will implement additional preventative measures such as: * Monitoring and alerting for connection cleanup latency and failure rates, so that slowdowns in connection closure are detected early. * Enhanced safeguards on database connection creation to limit the blast radius of any future connection accumulation events. We apologize to customers whose services were impacted during this incident. We are taking immediate steps to improve the resilience of our platform_._ ‌ Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 11, 2026, 10:48 PM UTC· resolved Jun 12, 2026, 12:14 AM UTC

1. investigating Jun 11, 2026, 10:48 PM UTC

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

2. identified Jun 11, 2026, 11:21 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.

3. monitoring Jun 11, 2026, 11:58 PM UTC

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

4. resolved Jun 12, 2026, 12:14 AM UTC

   On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Jun 10, 2026, 09:42 AM UTC· resolved Jun 10, 2026, 10:00 AM UTC

1. investigating Jun 10, 2026, 09:42 AM UTC

   Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

2. resolved Jun 10, 2026, 10:00 AM UTC

   On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.

Read the full incident report →

Started Jun 10, 2026, 09:42 AM UTC· resolved Jun 10, 2026, 10:00 AM UTC

1. investigating Jun 10, 2026, 09:42 AM UTC

   Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.

2. resolved Jun 10, 2026, 10:00 AM UTC

   On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.

Read the full incident report →

Started Jun 10, 2026, 06:14 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 06:14 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 06:14 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Jun 10, 2026, 06:14 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 06:14 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 06:14 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Jun 10, 2026, 06:14 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 06:14 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 06:14 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 04:55 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 05:39 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 04:55 AM UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 05:39 AM UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →