Is Confluence down?

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.

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.

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.

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.

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.

## 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

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.

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.

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.

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.

### 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

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.

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.

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.

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.

### 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

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.

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.

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.

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.

We are investigating an issue where customers attempting to view Calendars receive an error message on Confluence Cloud pages. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 1 hours, or sooner if we have any meaningful developments to report.

Between 00:50 UTC and 07:30 UTC on 27 May 2026, some users were facing errors when attempting to view Calendars in Confluence. Our engineering team identified and resolved the underlying issue, and this incident has been fully restored.