Is there an Confluence outage?
Confluence status: Systems Active
Last checked: 6 minutes ago
Get notified about any outages, downtime or incidents for Confluence and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 6 minutes 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: Between February 9, 4 PM UTC to February 12, 5:49 PM UTC, we experienced degraded performance related to Invitations on Confluence and Jira Software Cloud. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: Minor | Started At: Feb. 12, 2024, 3:27 p.m.
Description: Between February 9, 4 PM UTC to February 12, 5:49 PM UTC, we experienced degraded performance related to Invitations on Confluence and Jira Software Cloud. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: Minor | Started At: Feb. 12, 2024, 3:27 p.m.
Description: ### Summary On February 12, 2024, between 1:45pm and 2:54pm UTC, some Atlassian customers were unable to access Confluence Cloud. The event was triggered by a Redis \(cache\) failure causing a spike in the retries to connect to Redis \(Cache\). The connection spike along with synching data from multiple nodes to Redis caused the threadpool depletion. This impacted some customers in US East and EU regions. The incident was detected within two minutes by monitoring and mitigated by scaling up the webserver nodes which put Atlassian systems into a known good state. The total time to resolution was about one hour and nine minutes. ### **IMPACT** The overall impact was on February 12, 2024, between 1:45pm and 2:54pm UTC. This caused service disruption to some customers in US East and EU regions where they were unable to access Confluence. ### **ROOT CAUSE** Confluence has a set of data controlling features that are stored locally in all nodes, and in a Redis cache as a persistent store. A Redis failover from primary to read replica triggered a process across all nodes to sync data from the local cache to Redis with a large payload. This resulted in spikes in connections with multiple retries resulting in spikes in CPU and threadpool depletion. As a result, Confluence was unavailable or with degraded experience \(very slow on load\). ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident. * Rely on streaming to sync local cache to Redis that prevents connections from being held for a long duration. * Increase the Redis instance type from t3.micros to t3.medium that provides a larger memory to accommodate a write-a-storm scenario We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: Minor | Started At: Feb. 12, 2024, 2:24 p.m.
Description: ### Summary On February 12, 2024, between 1:45pm and 2:54pm UTC, some Atlassian customers were unable to access Confluence Cloud. The event was triggered by a Redis \(cache\) failure causing a spike in the retries to connect to Redis \(Cache\). The connection spike along with synching data from multiple nodes to Redis caused the threadpool depletion. This impacted some customers in US East and EU regions. The incident was detected within two minutes by monitoring and mitigated by scaling up the webserver nodes which put Atlassian systems into a known good state. The total time to resolution was about one hour and nine minutes. ### **IMPACT** The overall impact was on February 12, 2024, between 1:45pm and 2:54pm UTC. This caused service disruption to some customers in US East and EU regions where they were unable to access Confluence. ### **ROOT CAUSE** Confluence has a set of data controlling features that are stored locally in all nodes, and in a Redis cache as a persistent store. A Redis failover from primary to read replica triggered a process across all nodes to sync data from the local cache to Redis with a large payload. This resulted in spikes in connections with multiple retries resulting in spikes in CPU and threadpool depletion. As a result, Confluence was unavailable or with degraded experience \(very slow on load\). ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. We are prioritizing the following improvement actions to avoid repeating this type of incident. * Rely on streaming to sync local cache to Redis that prevents connections from being held for a long duration. * Increase the Redis instance type from t3.micros to t3.medium that provides a larger memory to accommodate a write-a-storm scenario We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support
Status: Postmortem
Impact: Minor | Started At: Feb. 12, 2024, 2:24 p.m.
Description: Between 15:40 UTC to 15:57 UTC customers experienced intermittent failures when searching for users in Atlassian cloud services: Confluence, Jira Work Management, Jira Service Management, Jira Software, Atlassian Bitbucket, Jira Product Discovery, and Compass. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: None | Started At: Feb. 7, 2024, 4:40 p.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.
