Is there an Confluence outage?
Confluence status: Systems Active
Last checked: 46 seconds ago
Get notified about any outages, downtime or incidents for Confluence and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 46 seconds ago
Get notified about any outages, downtime or incidents for Confluence and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Confluence.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Administration | Active |
| Authentication and User Management | Active |
| Cloud to Cloud Migrations - Copy Product Data | Active |
| Comments | Active |
| Confluence Automations | Active |
| Create and Edit | Active |
| Marketplace Apps | Active |
| Notifications | Active |
| Purchasing & Licensing | Active |
| Search | Active |
| Server to Cloud Migrations - Copy Product Data | Active |
| Signup | Active |
| View Content | Active |
| Mobile | Active |
| Android App | Active |
| iOS App | Active |
View the latest incidents for Confluence and check for official updates:
Description: This incident has been resolved. Version 3.71.3 and above have been monitored and validated.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 11:36 p.m.
Description: This incident has been resolved. Version 3.71.3 and above have been monitored and validated.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 11:36 p.m.
Description: We have identified that this behavior existed for long time and is due to a bug triggered in edge scenario when following sequence of events happens: 1. First a paid app gets suspended due to lack of payment 2. Then administrator decides to uninstall app 3. Then administrator decides to (re)install app 4. Payment is issued for the app 5. App fails to reactivate (as a result of this bug) We are advising customers to raise a support ticket with Atlassian to restore app functionality when faced with such scenario. The app reactivates correctly when no re-installation was attempted after suspension. We haven't found any recent changes that could cause this scenario to be happening more frequently. We're going to work in the future on improving the reinstallation flow for the suspended apps which will reduce the possibility to leave apps in state whey they can't be reactivated.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 6:45 a.m.
Description: We have identified that this behavior existed for long time and is due to a bug triggered in edge scenario when following sequence of events happens: 1. First a paid app gets suspended due to lack of payment 2. Then administrator decides to uninstall app 3. Then administrator decides to (re)install app 4. Payment is issued for the app 5. App fails to reactivate (as a result of this bug) We are advising customers to raise a support ticket with Atlassian to restore app functionality when faced with such scenario. The app reactivates correctly when no re-installation was attempted after suspension. We haven't found any recent changes that could cause this scenario to be happening more frequently. We're going to work in the future on improving the reinstallation flow for the suspended apps which will reduce the possibility to leave apps in state whey they can't be reactivated.
Status: Resolved
Impact: Minor | Started At: June 12, 2024, 6:45 a.m.
Description: ### Summary On June 04, 2024, between 07:28 and 08:32 UTC, some Atlassian customers using Confluence Cloud products could not access the functionality in parts of the EU Central region. The event was triggered by temporarily reduced capacity following a rollback deployment, with insufficient nodes to handle the load. Our alerts detected the incident within two minutes and mitigated it by rolling forward the release and manually adding more nodes, which put Atlassian systems into a known-good state. The total time to resolution was about 64 minutes. ### **IMPACT** The overall impact was on June 04, 2024, between 07:28 and 08:32 UTC, to customers using Confluence Cloud. The Incident caused service disruption to some EU Central region customers, resulting in reduced functionality, slower response times, and limited access when loading Confluence pages, space overview pages, and the home page. ### **ROOT CAUSE** When we deploy and release our changes to all the different regions, we execute a progressive rollout strategy. This helps us catch any issues proactively. If an issue is found during deployment, the deployment is paused and an automated rollback to the previous release is triggered. In this case, there was a timeout from our configuration to our cloud provider for one region, which forced an automated rollback to the previous release in all the regions. As that rollback happened in the EU Central region, there needed to be more compute nodes to handle the high traffic. Other regions rolled back successfully with no customer impact. Thus the root cause of the incident was the failure to scale our nodes to the optimal capacity caused by an automated rollback of a release. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have several testing and preventative processes in place, this specific issue wasn’t identified because it was an issue in our deployment pipeline that was not picked up by our regular automated continuous deployment suites and manual test scripts. We are prioritizing the following improvement actions to avoid repeating this type of incident: * Introduce more aggressive scaling of our nodes to handle incoming traffic if we rollback to an older release * Address gaps in deployment and testing processes, add more post-deployment validations to handle these cases * Have a fallback to an alternative source when we cannot render the experiences due to these failures We apologize to customers whose services were impacted by this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: Major | Started At: June 4, 2024, 8:15 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
