Confluence reported this minor-impact incident on its official status page on Jun 16, 2026, 13:46 UTC. It was resolved after 2h 10m.
Right now Confluence is operational. Live Confluence status →
### 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 inci
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.
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.
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.
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.
Our 5-minute checks didn't record a change in Confluence's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Confluence reported 7 incidents in the last 90 days, 4 of them major or critical. A typical incident lasted 3h 40m. See Confluence's uptime and incident history