Confluence reported this major-impact incident on its official status page on Sep 22, 2025, 05:09 UTC. It was resolved after 2h 8m.
Right now Confluence is operational. Live Confluence status →
### **SUMMARY** On September 22, 2025, between 04:38 and 04:48 UTC, Atlassian customers experienced connection errors preventing access to their [atlassian.net](http://atlassian.net/) sites. Some customers observed intermittent errors as services gradually recovered until 06:17 UTC. The event was triggered by a faulty configuration change to our Content Delivery Network \(CDN\). The change included an invalid hostname which prevented customers from successfully connecting to [atlassian.net](http://atlassian.net/) domains. The incident was detected within 1 minute by our monitoring systems and mitigated by rolling back the change, which put Atlassian systems into a known good state. The acute impact was resolved in 10 minutes and all lingering errors resolved in 1 hour 38 minutes. ### **IMPACT** The acute impact occurred on September 22, 2025, between 04:38 UTC and 04:48 UTC to Confluence, Compass and Jira, including Jira Service Management. The incident caused service disruption t
A configuration change to our CDN configuration for the atlassian.net domain resulted in customer traffic temporarily being dropped. This was immediately identified by our monitoring systems and rolled back. A public PIR with full details will be issued as a follow up.
Our team has investigated and enabled configuration changes which should be restoring services across all impacted products starting at 06:17AM UTC. We are monitoring for recovery across all products and services at this time, and will provide further update when available.
Our team is performing an investigation into all Atlassian products and services to understand the full impact of the prior certificate changes that caused this incident. While many services are restored we are continuing to monitor for additional impacted service issues that customers may be experiencing.
Our team is continuing to monitor Jira and Confluence products following the earlier issues relating to an erroneous certificate change. We are assessing all impacted products to ensure that services are fully restored and we will provide further update within the hour.
Our team is aware that access to Jira and Confluence cloud products was degraded between 04:39 and 04:52 UTC due to an erroneous certificate. The certificate has now been corrected and functionality has been restored. We are continuing to monitor the situation and will provide further update when available.
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.
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