Is Confluence Cloud down?

Product match: components.

Read the provider’s incident report

1. 2026-10-09T18:24:30.659Z · postmortem

   ### Summary On October 1, 2026, between 01:00 and 07:25 UTC, degraded job processing and scheduling impacted Atlassian products including Bitbucket Cloud, Confluence, Forge apps, Jira, and Jira Service Management in all commercial cloud regions. This caused delayed or missed background tasks, such as email-to-ticket processing and scheduled pipelines; interactive product use was not affected. The event was triggered when an unexpected volume of scheduled tasks became due simultaneously, overwhe

2. 2026-10-01T07:51:30.367Z · resolved

   On 01st Oct 2026, between 01:00 UTC and 07:25 UTC, users may have seen missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected. We have now implemented a fix and and services have been restored to normal operation for affected customers. The impact to support tickets with missing SLA component and delayed notifications have also confirmed recovery. Note: For Bitbucket customers, if there was any scheduled pipelines that did not run during th

3. 2026-10-01T07:01:47.575Z · identified

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. There is also an impact to the new support tickets created in terms of missing SLA component, notifications which may be affecting the response times and backlog management of some tickets.

4. 2026-10-01T05:00:54.989Z · identified

   Our teams continue to work on recovery until the incident is fully resolved. We will provide further updates if we have significant progress to share. Along with impact to scheduled and asynchronous work across several products, we also identified SLA component in Jira Service Management is not appearing as expected.

5. 2026-10-01T04:03:57.604Z · identified

   Our teams have taken corrective steps to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered.

6. 2026-10-01T03:47:45.775Z · identified

   Our teams have identified the root cause of this incident and is now actively working on mitigating the issue. We will provide further updates within an hour or sooner if we have any significant progress to share.

7. 2026-10-01T02:55:56.047Z · investigating

   Job processing and job scheduling is degraded, which is affecting scheduled and asynchronous work across several products, including Jira, Confluence and Bitbucket Cloud. Affected users may see delayed or missing job execution, including delayed email-to-ticket processing and schedules that do not run as expected.

Product match: components.

Read the provider’s incident report

1. 2026-09-07T02:53:18.559Z · postmortem

   **SUMMARY** On August 27, 2026, between 03:51 and 04:35 UTC, Atlassian customers in the Western Europe and Southeast APAC regions were unable to reach Atlassian Cloud products, including Atlassian Analytics, Compass, Confluence, Focus, Guard, Jira, JPD, JSM, Opsgenie, Rovo Search, and Talent. The event was triggered by a defective code change to the routing layer of one of our proxy fleets. This led to HTTP 404 errors being served to all customer traffic through these proxy fleets in Wester

2. 2026-08-27T05:16:07.474Z · resolved

   On 27 August 2026 UTC, Atlassian products including Jira Cloud, Jira Service Management and Confluence experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers. A public postmortem for this incident will be made available on this page when our full investigation of the incident has been completed.

3. 2026-08-27T04:51:26.551Z · monitoring

   The issues relating to loading Jira Cloud, Jira Service Management and Confluence are now in recovery. We'll continue to monitor closely to confirm stability and provide an update within one hour, or sooner as more information becomes available.

4. 2026-08-27T04:33:20.462Z · identified

   Our teams have identified a possible fix for the issues impacting Jira Cloud, Jira Service Management and Confluence. This is now being rolled out to impacted regions and we will update within one hour, or sooner if further information is available.

5. 2026-08-27T04:25:12.081Z · investigating

   We are investigating an issue with accessing products that is impacting Confluence, Jira Cloud and Jira Serivce Management customers. Our team is urgently investigating this issue and we will provide further details within one hour or sooner if information is available.

6. 2026-08-27T04:22:09.586Z · investigating

   Our teams have identified this issue is also impacting Jira Service Management. We will update further as soon as possible.

Product match: components.

Read the provider’s incident report

1. 2026-08-25T14:33:57.169Z · resolved

   On 25th Aug 2026, some users may have experienced increased latency in email, mobile and slack notifications. The issue has now been resolved, and the service is operating normally for all customers.

2. 2026-08-25T13:01:39.218Z · monitoring

   Our teams continue to mitigate the issue and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.

3. 2026-08-25T10:49:57.375Z · investigating

   Our teams have taken few corrective measures to mitigate the issue in one of the impacted regions and are observing some improvements. We continue to monitor the situation and will take necessary actions until the incident is fully recovered. We will provide further updates within next two hours, or sooner if we have significant progress to share.

4. 2026-08-25T09:44:51.896Z · investigating

   Our teams have identified the impacted regions and are actively working to mitigate the issue. We will provide further updates within an hour, or sooner if we have significant progress to share.

5. 2026-08-25T08:42:48.100Z · investigating

   We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and slack notifications for Jira, JSM and Confluence. Our teams are investigating the issue and more information will be shared within the next 1 hour.

Product match: components.

Read the provider’s incident report

1. 2026-08-24T23:15:20.518Z · resolved

   On August 24, 2026, some JIRA, JSM, and Confluence users may have experienced performance degradation resulting in increased latency in email, mobile, and Slack notifications. The issue has been resolved for newly created notifications, and service is operating normally. There may be older notifications that are being processed, and we expect them to be completed in next few hours.

2. 2026-08-24T21:30:42.100Z · identified

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience increased latency in email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will continue to share additional updates here as more information is available.

3. 2026-08-24T20:25:56.652Z · investigating

   Our teams have identified three impacted regions, and continue to investigate the increased latency affecting email, mobile, and Slack notifications for JIRA, JSM, and Confluence.

4. 2026-08-24T19:22:47.398Z · investigating

   We are actively investigating reports of performance degradation resulting in increased latency for email, mobile, and Slack notifications for JIRA, JSM, and Confluence. We will share updates here as more information is available.

Product match: components.

Read the provider’s incident report

1. 2026-08-21T10:10:30.571Z · resolved

   On 21st Aug 2026, between 04:26 UTC and 09:33 UTC, some users may have experienced issues with macros not rendering correctly in Confluence. The issue has now been resolved and the service is operating normally for all customers.

2. 2026-08-21T08:15:38.551Z · identified

   A fix has been identified and is currently being deployed. Users should begin to see the impacted MarketPlace App - Connect macros to start rendering correctly, once the fix has been fully propagated. We will provide further updates within the next 2 hours.

3. 2026-08-21T07:16:32.277Z · identified

   We have identified the root cause of an issue impacting Marketplace App macros in Confluence. Users may experience macros not rendering correctly or displaying errors. Our engineering team has identified the root cause and remediation is underway. We will provide further updates in the next 60 minutes.

Product match: components.

Read the provider’s incident report

1. 2026-08-12T22:13:28.260Z · resolved

   On August 12, 2026 some Confluence users utilizing anonymous access via public links, may have experienced a 'Something went wrong' error message. The issue has now been resolved, and the service is operating normally for all affected customers.

2. 2026-08-12T20:11:34.000Z · identified

   Some Confluence Cloud users visiting public links saw a Something went wrong error page. The issue affected anonymous access paths for public links, and some related Confluence areas could also show the same error message.

Product match: components.

Read the provider’s incident report

1. 2026-07-17T16:59:34.524Z · postmortem

   ## Summary On Jul 6, 2026, between 06:51 and 20:17 UTC, Atlassian customers using cloud products in European (EU) regions experienced service disruptions affecting automation rule execution, user search, user picker, and related workflows. The incident began when a core identity service experienced database saturation in EU regions, increasing latency and error rates. While responders worked to restore capacity, an emergency mitigation was applied which blocked automation rules from accessing t

2. 2026-07-06T13:04:02.024Z · resolved

   On July 6th 2026, between 06:51 UTC to 09:39 UTC some users may have experienced issues related Automation, and  between 08:10 UTC to 11:50 UTC some users may have experienced issues related to user-search, user-picker and assets in the EU-Region. The issues have now been resolved and the services are operating normally for all the customers.

3. 2026-07-06T12:25:51.856Z · monitoring

   We have applied the fix to mitigate the issue and 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.

4. 2026-07-06T11:46:19.044Z · investigating

   We are still seeing some issues with user-search, user-picker and assets across with the EU-Region. We continue to investigate the situation and will provide additional updates in the next one hour or sooner.

5. 2026-07-06T10:04:42.182Z · monitoring

   We have successfully applied the fix and are seeing recovery. Automation capabilities are being restored and should operate normally going forward. Data processing requests submitted during the outage period were not completed due to service unavailability. We continue to monitor the situation and expect full recovery within the next hour. We will provide additional updates in the next one hour or sooner.

6. 2026-07-06T09:23:39.709Z · investigating

   We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.

Product match: components.

Read the provider’s incident report

1. 2026-06-23T18:25:45.496Z · postmortem

   ### 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 e

2. 2026-06-16T15:56:40.613Z · resolved

   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.

3. 2026-06-16T14:53:40.235Z · monitoring

   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.

4. 2026-06-16T14:28:14.966Z · identified

   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.

5. 2026-06-16T13:46:42.198Z · investigating

   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.

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-10-20T03:35:52.000Z.

The displayed rolling 24-hour window contains 0 recorded reports, from 2026-10-19T03:30:00.000Z to 2026-10-20T03:30:00.000Z. This is not a calendar-day total or a count of affected people. Estimated activity is shown separately as an estimate.

An official operational status can coexist with a local network issue, account problem, or feature-specific incident. Compare the mapped components, recent incident updates, and regional diagnostic on this page. Automated website checks test public access, not your signed-in session or every Confluence Cloud feature.

The latest status observation was 2026-10-20T03:32:58.000Z. Only matched product components and incidents are shown. The assessment is recent.

The daily calendar links available incident evidence and retains daily monitoring summaries. Pink marks service issues, green requires sufficient observations with no issues observed, and gray means insufficient coverage. The collected history is incomplete and is not a lifetime outage count or a guarantee of uninterrupted uptime.

Use “Watch this service” to save Confluence Cloud in this browser’s watchlist, then return to compare its status with other saved services. The watchlist does not send notifications. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.