- Level
- confirmed
- Worst impact
- Partial outage
- Components
- View Content, iOS App, Create and Edit, Android App, Comments, Authentication and User Management, Search, Administration, Notifications, Marketplace Apps, Purchasing & Licensing, Signup, Confluence Automations, Cloud to Cloud Migrations - Copy Product Data, Server to Cloud Migrations - Copy Product Data
- Down Index
- 49of 100
What to do
Check whether you use Confluence View Content, iOS App, Create and Edit, Android App and 11 more. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 8m it lasted.
Anything that failed between 2025-09-22 05:09 UTC and 2025-09-22 07:17 UTC may need a replay.Subscribe to Confluence's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=confluence works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Confluence 6
- investigating
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.
provider
- identified
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.
provider
- identified
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.
provider
- monitoring
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.
provider
- resolved
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.
provider
- postmortem
### **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 to customers when they attempted to load those products in their browser or interact with APIs. Between 04:48 UTC and 06:17 UTC some customers continued to observe intermittent errors as services gradually recovered. ### **ROOT CAUSE** The issue was caused by a change to the hostname configuration of our Content Delivery Network \(CDN\). As a result, the products mentioned could not receive connections, and the users received TLS handshake errors, followed by HTTP 503 and 403 errors. More specifically a new CDN configuration contained a resource name which conflicted with the existing customer-serving CDN resource, and was able to be deployed, overwriting it. The root cause of the incident was the failure in the detection of the bug by our pre-deployment validations and tests. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that you rely on our products for your daily operations and productivity, and we sincerely apologize for any impact this disruption has had on you, your team or your organisation. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Improved pre-deployment change controls and testing. * Improved validation of target configurations before deployment to ensure customer-serving CDN resources cannot their hostnames changed. * Sharding of our CDN configuration to enable progressive changes. We sincerely appreciate your understanding and patience as we improve our processes to provide a better customer experience. Thank you, Atlassian Customer Support
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-c0192d72d1
Is Confluence still down?
No, this incident was resolved 2025-09-22 07:17 UTC. For Confluence's live state, see https://down.guide/confluence.
How long did it last?
2h 8m, from 2025-09-22 05:09 UTC to 2025-09-22 07:17 UTC, by the times Confluence posted.
What was affected?
Confluence named View Content, iOS App, Create and Edit, Android App and 11 more.
What caused it?
Confluence hasn't published a root cause. If it does, it shows here.
Where does this come from?
Confluence's official status page, https://confluence.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.