Confluence

Affected: Confluence Automations

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-01 02:55 UTC

   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...

2. identified 2026-10-01 03:47 UTC

   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.

3. identified 2026-10-01 04:03 UTC

   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.

4. identified 2026-10-01 05:00 UTC

   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...

5. identified 2026-10-01 07:01 UTC

   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...

6. resolved 2026-10-01 07:51 UTC

   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...

7. postmortem 2026-10-09 18:24 UTC

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

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-08-27 04:22 UTC

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

2. investigating 2026-08-27 04:25 UTC

   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.

3. identified 2026-08-27 04:33 UTC

   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.

4. monitoring 2026-08-27 04:51 UTC

   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.

5. resolved 2026-08-27 05:16 UTC

   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...

6. postmortem 2026-09-07 02:53 UTC

   **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...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-25 08:42 UTC

   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.

2. investigating 2026-08-25 09:44 UTC

   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.

3. investigating 2026-08-25 10:49 UTC

   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...

4. monitoring 2026-08-25 13:01 UTC

   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...

5. resolved 2026-08-25 14:33 UTC

   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.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-24 19:22 UTC

   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.

2. investigating 2026-08-24 20:25 UTC

   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.

3. identified 2026-08-24 21:30 UTC

   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...

4. resolved 2026-08-24 23:15 UTC

   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...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-21 07:16 UTC

   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...

2. identified 2026-08-21 08:15 UTC

   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. resolved 2026-08-21 10:10 UTC

   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.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-08-12 20:11 UTC

   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.

2. resolved 2026-08-12 22:13 UTC

   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.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-07-06 09:23 UTC

   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.

2. monitoring 2026-07-06 10:04 UTC

   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...

3. investigating 2026-07-06 11:46 UTC

   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.

4. monitoring 2026-07-06 12:25 UTC

   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.

5. resolved 2026-07-06 13:04 UTC

   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...

6. postmortem 2026-07-17 16:59 UTC

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

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-16 13:46 UTC

   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.

2. identified 2026-06-16 14:28 UTC

   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...

3. monitoring 2026-06-16 14:53 UTC

   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. resolved 2026-06-16 15:56 UTC

   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.

5. postmortem 2026-06-23 18:25 UTC

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

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content, Create and Edit

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-06-12 07:39 UTC

   Users are experiencing experiencing degraded performance in Confluence Cloud affecting view page and edit page functionality. Our teams are actively investigating and will be sharing more updates in next 1 hour or sooner.

2. investigating 2026-06-12 08:45 UTC

   Users are experiencing degraded performance with view content, create and edit functionality on Confluence Cloud primarily in the EU region. Our teams are actively working to identify the root cause of the issue. We will share additional updates in next 2 hours or sooner as more...

3. identified 2026-06-12 10:29 UTC

   Our teams have identified the root cause of this issue and implemented a fix. We are beginning to observe signs of recovery, with some affected users regaining access to view, create, and edit content on Confluence Cloud. We will provide a further update within one hour, or...

4. resolved 2026-06-12 11:15 UTC

   On June 12th 2026, between 07:04 to 11:06 UTC, some Confluence users may have experienced service disruptions. The issue has now been resolved and the service is operating normally for all affected customers.

5. postmortem 2026-06-23 18:28 UTC

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

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-10 06:14 UTC

   We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps. Our team is looking...

2. identified 2026-06-10 06:14 UTC

   Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products. At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers. We will...

3. monitoring 2026-06-10 06:14 UTC

   Our team has now determined that performance has returned to expected levels for those impacted by this incident. Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products...

4. resolved 2026-06-10 06:31 UTC

   We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-27 06:03 UTC

   We are investigating an issue where customers attempting to view Calendars receive an error message on Confluence Cloud pages. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes...

2. identified 2026-05-27 07:06 UTC

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 1 hours, or sooner if we have any meaningful developments to report.

3. resolved 2026-05-27 07:48 UTC

   Between 00:50 UTC and 07:30 UTC on 27 May 2026, some users were facing errors when attempting to view Calendars in Confluence. Our engineering team identified and resolved the underlying issue, and this incident has been fully restored.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-26 10:40 UTC

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published...

2. investigating 2026-05-26 11:58 UTC

   We are investigating an issue where some custom extensions may fail to load when editing Confluence Cloud pages. Affected users may see 'Error loading the extension!' messages or notice that certain macros are missing from the editor's extension selection menu. Viewing published...

3. investigating 2026-05-26 11:58 UTC

   We are actively investigating an issue affecting the editing macros in Confluence Cloud editor. Our team is working to identify the root cause. We will provide an update within approximately one hour.

4. resolved 2026-05-26 13:55 UTC

   Between 08:30 UTC and 13:51 UTC on 26 May 2026, some users were unable to load or edit certain macros in the Confluence Cloud page editor. Our engineering team identified and resolved the underlying issue, and macro functionality has been fully restored.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-14 04:54 UTC

   We are investigating an issue with multiple Atlassian products that is impacting a large number of Confluence and Jira Cloud customers. We are continuing to investigate and will add further details about additional impact as our investigation continues. We will provide more...

2. investigating 2026-05-14 05:03 UTC

   We are aware that the current issues with accessing Atlassian products are impacting additional products. We have now expanded the impact of the incident to cover the known impacted products at this time. We will provide further update within one hour or sooner as information is...

3. identified 2026-05-14 05:11 UTC

   Further confirmations of impacted products have now been added to the incident. Our team is investigating the issue with urgency and we will provide further update as soon as it becomes available.

4. identified 2026-05-14 05:24 UTC

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team...

5. identified 2026-05-14 05:34 UTC

   Our team has identified the root cause of this issue and is now actively working on mitigating the issue with accessing Atlassian products. At this time, Atlassian customers should also be able to once again raise support requests with our team. We will provide further update...

6. monitoring 2026-05-14 05:43 UTC

   Our team has implemented a mitigation for this issue and we are now seeing recovery across Atlassian products. We will continue to monitor this issue for any ongoing concerns, and provide further updates here within an hour as we are able to confirm a full recovery has taken...

7. monitoring 2026-05-14 06:40 UTC

   We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been...

8. monitoring 2026-05-14 06:41 UTC

   We are approaching full system recovery at this time, and are performing final confirmations that services are restored.

9. resolved 2026-05-14 06:48 UTC

   All products and services impacted by this incident should now be fully recovered, and this incident is resolved.

10. postmortem 2026-05-19 19:04 UTC

    ### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A zone, region or data center became unavailable. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-08 01:31 UTC

   We are experiencing issues with multiple Atlassian products. Our teams are investigating further and more updates including will be shared within 1 hour.

2. identified 2026-05-08 02:15 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

3. identified 2026-05-08 03:00 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

4. identified 2026-05-08 03:00 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

5. identified 2026-05-08 04:10 UTC

   We have identified that the root cause of the issue is related to an infrastructure outage from our public cloud provider. We are working closely with them to mitigate this issue. We will provide further updates when they become available.

6. identified 2026-05-08 04:10 UTC

   Our teams continue to work on mitigating the infrastructure outage from our public cloud provider. We will provide further updates when they are available.

7. identified 2026-05-08 04:10 UTC

   We are continuing to work with our public cloud provider to mitigate this issue. We are starting to see some recovery in regions outside of Eastern USA, however, users globally may still be experiencing issues with certain product features. These are listed at the bottom of each...

8. monitoring 2026-05-08 05:53 UTC

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation...

9. monitoring 2026-05-08 08:03 UTC

   We continue to monitor the situation as services recover. We are currently in the process of clearing the backlog of queued events. We will provide a further update in approximately one hour.

10. monitoring 2026-05-08 11:12 UTC

    Our services are now fully operational. We continue to replay any events that were missed during the incident, and are making good progress. We will provide a further update once replays are complete. If you experience any ongoing issues, please contact our support team. We...

11. resolved 2026-05-08 19:45 UTC

    On May 8, 2026, some customers utilizing Atlassian products experienced elevated error rates and degraded performance. The issue has now been resolved, and the service is operating normally for all affected customers.

12. postmortem 2026-05-20 06:55 UTC

    All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-14 12:25 UTC

   We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more...

2. investigating 2026-04-14 12:25 UTC

   We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more.

3. identified 2026-04-14 14:11 UTC

   We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available.

4. monitoring 2026-04-14 15:46 UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.

5. resolved 2026-04-14 16:11 UTC

   On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-04-13 07:29 UTC

   Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact. Our team is investigating with urgency, and we...

2. monitoring 2026-04-13 08:33 UTC

   Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.

3. resolved 2026-04-13 10:17 UTC

   On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.

4. postmortem 2026-04-21 02:33 UTC

   ### Summary On April 13, 2026, between 05:49 and 06:29 UTC, customers experienced failures when attempting to log in, sign up, reset passwords, and complete multi-factor authentication flows across Atlassian cloud products. Approximately 90% of authentication requests failed...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-04-08 05:41 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

2. investigating 2026-04-08 06:01 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

3. investigating 2026-04-08 06:01 UTC

   The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard. Our team is continuing to investigate with urgency and we will provide further...

4. investigating 2026-04-08 06:24 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

5. investigating 2026-04-08 06:25 UTC

   Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.

6. identified 2026-04-08 06:25 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

7. identified 2026-04-08 07:40 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

8. identified 2026-04-08 07:40 UTC

   Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.

9. identified 2026-04-08 08:33 UTC

   We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

10. identified 2026-04-08 08:33 UTC

    We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update...

11. identified 2026-04-08 09:03 UTC

    We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus. Our team have identified the potential root cause of the issue and our teams are working with urgency on a...

12. monitoring 2026-04-08 09:03 UTC

    The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.

13. resolved 2026-04-08 11:43 UTC

    The issue has now been resolved, and the service is operating normally for all affected customers.

14. postmortem 2026-04-17 16:24 UTC

    ### Summary On April 8, 2026, between 04:46 UTC and 12:09 UTC, search functionality was unavailable or degraded across several Atlassian Cloud products, including Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-12 11:42 UTC

   Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing the message Error rendering macro 'static-macro': Page loading failed. Our team is actively investigating this issue. We will provide another update within 2...

2. investigating 2026-03-12 13:38 UTC

   Confluence Cloud users may experience errors when accessing certain Marketplace macros. Affected customers are seeing the message Error rendering macro 'static-macro': Page loading failed. Our team is actively investigating this issue. We will provide another update within 2...

3. identified 2026-03-12 13:38 UTC

   Our team has identified the cause of this issue, and a fix is currently being deployed. We are monitoring the deployment, and we will provide another update within 2 hours, or sooner if needed.

4. resolved 2026-03-13 00:26 UTC

   On March 12, 2026, affected Confluence Cloud users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-10 00:15 UTC

   We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.

2. identified 2026-03-10 00:15 UTC

   Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed.

3. monitoring 2026-03-10 00:51 UTC

   The performance degradation of automations has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

4. resolved 2026-03-10 00:59 UTC

   On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-02-20 04:14 UTC

   Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users and products. We anticipate our next update to be...

2. identified 2026-02-20 07:13 UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users...

3. identified 2026-02-20 12:26 UTC

   We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields. We are continuing to work towards mitigating this issue for all users...

4. resolved 2026-02-20 12:26 UTC

   This issue has been resolved and all services are functional.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-02-19 15:44 UTC

   We have received and investigated reports of a partial service disruption affecting Confluence Cloud for some customers in AP South, APSE, APSE2, East, and Central. The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to...

2. resolved 2026-02-19 17:47 UTC

   On February 19 2026, affected Confluence Cloud users may have experienced some service disruption in AP South, APSE, APSE2, East, and Central regions. The issue has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-02-18 10:57 UTC

   Org Admins are unable to click on any group from Groups page in Atlassian administration (admin.atlassian.com). Admins are unable to adding/removing users and app access from the groups while accessing from admin.atlassian.com. We are currently investigating the problem. Next...

2. monitoring 2026-02-18 11:28 UTC

   We have identified the root cause, and fix has been rolled out to mitigate the problem. We are monitoring the progress.

3. resolved 2026-02-18 11:30 UTC

   We have implemented the fix and the group page in the Admin Hub is now functioning as expected.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-03 10:19 UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or...

2. investigating 2026-02-03 10:24 UTC

   Customers utilizing Confluence and Jira Mobile may experience disruptions in OAuth authentication flows. Forge installations and invocations might also be disrupted. Our team is actively investigating the same and we shall keep you informed of the progress within next 60 mins or...

3. resolved 2026-02-03 10:50 UTC

   Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-08 15:27 UTC

   We are actively investigating reports of a partial service disruption affecting Confluence Cloud for some customers. We'll share updates here in an hour or as more information is available.

2. monitoring 2026-01-08 16:35 UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

3. monitoring 2026-01-08 16:36 UTC

   The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.

4. resolved 2026-01-08 19:09 UTC

   On Thursday, January 8, 2026, affected Confluence Cloud users in us-east-1 region may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem 2026-01-28 01:49 UTC

   ### Summary On Jan 08, 2026 between 14:54 UTC and 16:30 UTC, Atlassian customers using Confluence Cloud product\(s\) experienced degraded service with view/edit page experiences. The event was triggered by database overload due to an unexpected large burst of traffic. The...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Notifications

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A configuration change. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-27 02:48 UTC

   We have identified an issue with outbound email delivery and mobile push notifications that is impacting Atlassian Cloud customers across all products. Importantly, customer support tickets are unable to be generated during this time. We apologise for any inconvenience this may...

2. investigating 2025-12-27 03:28 UTC

   We are actively investigating this issue and will share additional updates as soon as more information becomes available. We sincerely apologize for the inconvenience this has caused.

3. monitoring 2025-12-27 04:42 UTC

   We have taken steps to mitigate the issue and are seeing recovery in the affected services. Our teams will continue to closely monitor the situation and are actively working to confirm that all services are fully restored. We will provide further updates as we make additional...

4. resolved 2025-12-27 05:20 UTC

   We have successfully mitigated the incident and all affected services are now fully operational. Our teams have verified that normal functionality has been restored across all areas. Thank you for your patience and understanding while we worked to resolve this issue.

5. postmortem 2026-01-30 04:06 UTC

   ### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-12-15 16:26 UTC

   We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.

2. identified 2025-12-15 16:47 UTC

   We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.

3. identified 2025-12-15 17:47 UTC

   Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements. We will continue to provide updates here in 60 minutes or as more information becomes available.

4. resolved 2025-12-15 19:01 UTC

   On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps....

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-11 01:08 UTC

   We are aware that customers are currently experiencing installation failures when attempting to install Connect on Forge apps into Confluence. Our team is investigating with urgency and we will provide an update within the hour.

2. identified 2025-12-11 02:08 UTC

   Our team has identified a root cause for this issue, and have now commenced a rollback of the problematic change and verifying that this is resolved. There should not be any impact to currently installed apps as a result of this incident. However, we are aware that cloud...

3. resolved 2025-12-11 04:37 UTC

   The rollback required to resolve this issue is now completed, and we have verified across the impacted products that App installation behaviour is now working as expected. We apologize for any inconvenience this may have caused.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

1. investigating 2025-11-21 14:55 UTC

   Multiple Atlassian services are seeing outages and we are investigating the same. We shall keep you posted on the progress in 60 minutes, if not sooner

2. investigating 2025-11-21 15:30 UTC

   Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.

3. monitoring 2025-11-21 16:14 UTC

   The Trello performance degradation affecting some customers has been resolved. A subset of customers may have experienced intermittent errors on some of our other products, but these should also now be resolved too. We'll continue to monitor closely to confirm stability.

4. resolved 2025-11-21 16:49 UTC

   The Trello performance degradation has been resolved. Also, some intermittent errors on some of our other products, has also now been resolved. The issue has now been resolved, and the service is operating normally for all affected customers.

5. postmortem 2025-12-08 05:25 UTC

   ### Summary On November 21, 2025, between 13:44 and 15:16 UTC, Trello customers were intermittently unable to view and update data on their boards. Customers also may have experienced issues authenticating with Atlassian products, and creating new GitHub and Slack integrations....

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 13:32 UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

2. investigating 2025-11-18 13:35 UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

3. investigating 2025-11-18 13:37 UTC

   We are aware of a global Cloudflare issue affecting Confluence Whiteboards and are currently looking into the issue.

4. investigating 2025-11-18 14:40 UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. You may notice elevated server errors in Confluence Whiteboards and Databases. Cloudflare is actively working to restore its services, and we are closely monitoring its progress. We understand how...

5. identified 2025-11-18 15:58 UTC

   We are aware of a global Cloudflare issue that is currently impacting Confluence. Cloudflare is reporting that a fix has been implemented and services are restoring. Our engineering teams continue to monitor the restoration of services. It is possible that you may still...

6. resolved 2025-11-18 16:57 UTC

   Elevated Errors in Confluence Whiteboards and Databases Due to Cloudflare Outage Cloudflare successfully deployed a fix for the issue that was impacting Confluence. We are no longer seeing Confluence system performance degradation and Confluence systems have been fully restored....

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-18 02:55 UTC

   We are aware of some customers being impacted by an error in Confluence while attempting to edit content stating 'We've lost our connection to you. Your changes will be saved when we reconnect. Trying to reconnect...'. Our team is investigating with urgency and will provide...

2. monitoring 2025-11-18 03:16 UTC

   Our team has reverted a recent change that is suspected to have caused these errors, and have seen instances of these error messages to decrease. We are continuing to monitor and will update when this issue is confirmed to be resolved.

3. resolved 2025-11-18 03:35 UTC

   Our team has been able to confirm that customers should no longer be experiencing the error while attempting to edit using Confluence. We apologize for any inconvenience this may have caused. This issue is now resolved.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Confluence Automations

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-03 16:11 UTC

   We are investigating reports of degraded performance and intermittent errors for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

2. investigating 2025-11-03 17:15 UTC

   We are continuing to investigate the cause of degraded performance and intermittent errors impacting Automations and the Automation UI for some Confluence, Jira Service Management, and Jira Cloud customers. We will provide more details in one hour, if not sooner.

3. resolved 2025-11-03 18:08 UTC

   On November 3, 2025, some Confluence, Jira Service Management, and Jira Cloud users may have experienced performance degradation and errors in the Global Automation UI page. Automation executions were not impacted by this incident. The issue has now been resolved, and the...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: CDN or edge layer failed or served bad content. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-29 06:47 UTC

   We have reports of some users in Australia seeing degraded performance of Atlassian cloud. Our team is investigating this and we shall keep you informed in next 60 minutes or sooner.

2. investigating 2025-10-29 06:57 UTC

   Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide...

3. investigating 2025-10-29 06:58 UTC

   Considering the complexity and intermittent nature of this issue. Atlassian team believes that further investigation of this issue is required and we will reach out to some of the impacted customers for specific information. Based on the above, we shall be able to provide...

4. investigating 2025-10-30 02:08 UTC

   Working with our infrastructure provider, our team has been able to identify specific CDN hardware changes that were rolling out this week, and are expected to be correlated to the performance issues some customers have seen loading pages in Jira and Confluence in specific...

5. resolved 2025-10-30 02:09 UTC

   Incident has been resolved.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content, Create and Edit

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-10-24 06:31 UTC

   Multiple customers in APSE region are experience failure accessing Confluence application. We are currently investigating.

2. investigating 2025-10-24 07:04 UTC

   We have an active line of investigation. Will update with results within 30 minutes.

3. investigating 2025-10-24 07:42 UTC

   Addressed one potential cause of load in the affected region. Monitoring for results and continuing to pursue other leads.

4. investigating 2025-10-24 08:26 UTC

   We are seeing reduced error volumes now which indicate improvement in Confluence availability. Continuing to monitor and investigate/validate root causes.

5. investigating 2025-10-24 09:10 UTC

   We have addressed an issue causing increased database load and seeing recovery of user experience. Will continue to monitor before resolving issue.

6. investigating 2025-10-24 09:18 UTC

   We see a full recovery in Confluence application experience in the affected AP SouthEast region now.

7. resolved 2025-10-24 09:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Confluence Automations

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-22 06:20 UTC

   We understand that our customers are experiencing delay in execution of Automation rules. While our team is investigating further on this, it looks like a follow-on effect of the recent AWS outage. We continue to investigate further on this and we shall keep you informed of the...

2. identified 2025-10-22 06:34 UTC

   Atlassian team has identified the cause of the issue that led to delay in execution of Automation rules. This is a follow-on effect of the recent AWS outage. We shall keep you informed of the progress every hour, if not sooner.

3. resolved 2025-10-22 06:47 UTC

   Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as resolved.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:56 UTC

   We have noticed that Atlassian Cloud services are impacted and our teams are actively investigating the same. We shall keep you informed of the progress every hour.

2. investigating 2025-10-20 08:24 UTC

   Atlassian Cloud services are impacted and we are aware that our customers might not be able to create support tickets. Our teams are actively investigating the same. We shall keep you informed of the progress every hour.

3. investigating 2025-10-20 09:23 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

4. investigating 2025-10-20 09:24 UTC

   We are experiencing an outage due to some issue at the end of our public cloud provider. We are working closely with them to get this resolved or mitigated as quickly as possible. ETA of the same is not know at the moment. We shall continue to share updates every hour, if not...

5. identified 2025-10-20 09:58 UTC

   We understand that our public cloud provider has identified the cause of the issue. We are starting to see some recovery and is working towards mitigation. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

6. identified 2025-10-20 11:07 UTC

   We continue to work with our public cloud provider towards mitigating the issue at the earliest. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

7. identified 2025-10-20 12:06 UTC

   Atlassian team is actively engaged and continues to work with our public cloud provider to mitigate this issue at the earliest. We are starting to see partial operations succeed. We appreciate your patience. We shall continue to share updates every hour, if not sooner.

8. identified 2025-10-20 13:07 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

9. identified 2025-10-20 13:56 UTC

   Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

10. identified 2025-10-20 13:58 UTC

    Our public cloud provider is working to mitigate this issue quickly. We are seeing some early positive indicators and are continuing to monitor. We appreciate your patience and will continue to provide updates every hour or sooner.

11. identified 2025-10-20 14:02 UTC

    We understand your pain and mitigating or fixing this issue is of utmost importance. Our public cloud provider is actively working to mitigate this issue on priority. We have been seeing partial operational success. We appreciate your patience and will continue to provide...

12. identified 2025-10-20 15:20 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

13. identified 2025-10-20 15:22 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

14. identified 2025-10-20 16:35 UTC

    Update - Thank you for your continued patience. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is still actively working to mitigate this issue with urgency and...

15. identified 2025-10-20 17:27 UTC

    Update - We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority. Our public cloud provider is actively working to mitigate this issue with urgency. While we do not have a definitive ETA at this...

16. identified 2025-10-20 17:43 UTC

    We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS. We understand the impact this issue is having on your operations and want to assure you that resolving this matter is our highest priority and...

17. monitoring 2025-10-20 18:38 UTC

    There have been no changes since our last update. We will provide our next updated by 9:00PM UTC or sooner as new information becomes available. We are currently aware of an ongoing incident impacting Atlassian Cloud services due to an outage with our public cloud provider, AWS....

18. monitoring 2025-10-20 21:26 UTC

    Monitoring - We've started seeing continued product experience improvement. While we still have a backlog of event processing, we are seeing improvements in systems operational capabilities across all products. We estimate a significant improvement with the next few hours and...

19. monitoring 2025-10-20 22:58 UTC

    Our teams are continuing to monitor the recovery of systems across Atlassian products. This update is to inform that the Atlassian Support portal is fully operational at this time for customers that wish to contact support.

20. monitoring 2025-10-21 00:03 UTC

    Our team is now seeing recovery across all impacted Atlassian products. We are continuing to monitor for individual products that may still be processing backlogged items now that services are restored. The Atlassian Support portal is currently still displaying a message...

21. monitoring 2025-10-21 01:07 UTC

    We continue to see recovery progressing across all impacted products as backlogged items continue to be processed. The Atlassian Support portal is currently displaying a message directing customers to our temporary support channel. Please note that our support portal is...

22. monitoring 2025-10-21 03:24 UTC

    The issue relating to the Atlassian Support portal displaying a message to customers to use our temporary support channel has now been resolved. The Atlassian Support portal is fully functional for any ongoing support issues. With regards to other Atlassian products, we continue...

23. resolved 2025-10-21 05:24 UTC

    Our team is now able to see full recovery across the vast majority of Atlassian products. We are aware of some ongoing issues with specific components such as migrations and JSM virtual service agents, and our team is continuing to investigate with urgency. We apologise for the...

24. postmortem 2025-10-24 17:48 UTC

    ### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance between Oct 20, 2025 06:48 and Oct 21, 2025 04:05. The service...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Confluence Automations

Failure mode: Traffic surge or denial-of-service attack. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-15 13:43 UTC

   UI based Customer interactions are currently degraded and our team is actively investigating the same. We shall keep you informed of the progress in next 2 hours.

2. investigating 2025-10-15 14:34 UTC

   Atlassian team is actively investigating the issue with UI based Customer interactions. Existing automation rules continue to run without any issue. Accessing automation rules and creating new automation rules could lead to intermittent failures. We shall keep you informed of...

3. monitoring 2025-10-15 15:26 UTC

   We have recovered from a issue which saw degraded Automation experience. Impact Some Customers using Jira, Confluence, and Jira Service Management were not able to create or update Automation rules, and some Automation rules which triggered webhooks might have been throttled and...

4. resolved 2025-10-15 16:16 UTC

   Between 14:00 UTC to 16:00 UTC, we experienced automation rule functionality degradation for Confluence, Jira Work Management, Jira Service Management, and Jira. Impact Some customers using Jira, Confluence, and Jira Service Management were not able to create or update...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Marketplace Apps

Failure mode: A configuration change caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-09-30 17:15 UTC

   On September 29-30 2025, for about 24 hours, Confluence Cloud experienced an incident due to the unintended deprecation of ACJS methods (https://developer.atlassian.com/cloud/confluence/about-the-connect-javascript-api/#connect-javascript-api) linked to retired V1 APIs...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-22 05:09 UTC

   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...

2. identified 2025-09-22 05:38 UTC

   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.

3. identified 2025-09-22 05:59 UTC

   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...

4. monitoring 2025-09-22 06:55 UTC

   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.

5. resolved 2025-09-22 07:17 UTC

   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.

6. postmortem 2025-10-01 06:20 UTC

   ### **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...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content, Create and Edit, Comments

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-09-09 10:23 UTC

   We are investigating cases of degraded performance for Confluence and Jira Cloud customers using Microsoft Edge. We will provide more details as they emerge.

2. identified 2025-09-09 11:40 UTC

   Important Update on Attachment Issues with Edge 140 and Atlassian Products We've identified an issue affecting images, media, and Whiteboards in Confluence and Jira for users who have upgraded to Microsoft Edge version 140.0.3485.54 with Strict tracking prevention enabled. These...

3. identified 2025-09-10 00:55 UTC

   Our team is aware that the incorrect classification of Atlassian sites as advertising has been resolved, however these changes will take some time to propagate out to users since we are waiting for Edge from Microsoft to incorporate the changes. We are continuing to monitor the...

4. identified 2025-09-10 18:35 UTC

   We continue to work on resolving the Microsoft Edge 140 tracking prevention issue for Confluence, Jira Work Management, Jira Service Management, Jira, Jira Align, and Jira Product Discovery. We have identified the root cause and are working on solutions for each product. We will...

5. monitoring 2025-09-10 20:34 UTC

   We have identified the root cause of the Microsoft Edge 140 tracking prevention issue and have mitigated the problem and we continue monitoring closely. The issue has been mitigated however it will not be considered resolved until Microsoft issues an updated version of the Edge...

6. resolved 2025-09-15 06:40 UTC

   An update has been released by Microsoft to resolve this issue for users of the Edge browser. To verify that you are running the required version of Edge, you can navigate to edge://components/ in the address bar, click the 'Check for update' button for the 'Trust Protections...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Administration

Failure mode: A configuration change caused the failure. Root cause: A configuration change. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-08-04 23:44 UTC

   Our team is aware of issues with users not currently receiving product invitation emails as expected. We are investigating with urgency and will provide an update as soon as possible. Please note that invitations within the product are still successful, only the email...

2. resolved 2025-08-05 04:19 UTC

   Between 2025-08-03T21:34 and 2025-08-05T03:43 UTC some users would not have received the emails for product invitations. The change that caused these emails to stop being sent has been rolled back. New invitation emails should now be sent correctly for all products. For users...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: View Content, Create and Edit

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-30 07:10 UTC

   We are investigating an issue causing a degraded experience when adding attachments or accessing existing media content.

2. resolved 2025-07-30 07:31 UTC

   We have resolved the issue impacting adding/accessing media attachments across products. We will continue to monitor the situation.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-07-10 08:32 UTC

   We are investigating reports of intermittent errors for some Confluence, Jira Work Management, Jira Service Management, Jira, and Compass Cloud customers failing invocation, mostly scheduled triggers and smart links from 5:44 am UTC to 7:44 am UTC. We have put mitigations in...

2. resolved 2025-07-10 08:55 UTC

   Between 10th July 5:44 am UTC to 7:44 am UTC, we experienced intermittent failure in some app funstionality(smart links, scheduled triggers) for Confluence, Jira Work Management, Jira Service Management, Jira, and Compass. The issue has been resolved and the service is operating...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Authentication and User Management

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-25 09:38 UTC

   We are investigating reports of errors loading Users and Groups pages in Atlassian Administration, and errors affecting user IDP syncing. We will provide more details once we identify the root cause.

2. identified 2025-06-25 10:21 UTC

   We continue to work on resolving the user syncing functionality for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. We have identified the root cause and expect recovery shortly.

3. monitoring 2025-06-25 10:41 UTC

   We have identified the root cause of the issue and have mitigated the problem. We are now monitoring closely.

4. resolved 2025-06-25 10:57 UTC

   Between 07:40 UTC and 10:31 UTC, we experienced issues affecting user syncing in Atassian Administration. This affected Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Guard. The issue has been resolved and the service is operating normally.

Excerpts are shortened. Read the full incident on Confluence's status page.

Failure mode: A schema or data migration caused the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. resolved 2025-06-24 10:35 UTC

   We have resolved an issue that affected attachment loading during C2C and Sandbox data copy migrations from 19-06-2025 18:00 UTC to 24-06-2025 08:49 UTC. If you encountered this issue, please delete the affected projects from the destination site and re-run the migration. For...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-10 21:41 UTC

   We are investigating an issue impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. We will provide more details within the next hour.

2. resolved 2025-06-10 22:34 UTC

   Between 21:39 UTC on June 09, 2025 and 21:35 UTC on June 10, 2025, we experienced a forge invocation errors impacting a subset of market place apps for some Confluence, Jira Service Management, and Jira, and Atlassian Developer Cloud customers in the Singapore region. The issue...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Search

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-06-05 08:33 UTC

   We are investigating an issue affecting the search functionality in Confluence for some users in Europe. Our team is working diligently to resolve the degradation and restore services promptly. We will keep you updated with further information.

2. investigating 2025-06-05 09:32 UTC

   We are continuing to address an issue affecting the search functionality in Confluence for some users in Europe. Our team is actively working to mitigate the impact and restore services promptly. We will keep you updated with further information.

3. monitoring 2025-06-05 10:41 UTC

   The issues affecting the search functionality in Confluence have been resolved, and services now operate normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

4. resolved 2025-06-05 11:02 UTC

   The issues affecting the search functionality in Confluence have been resolved, and services now operate normally for all affected customers.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-06-04 17:17 UTC

   We were experiencing cases of degraded performance for outgoing emails from Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas and Compass Cloud customers. The system is recovering and...

2. resolved 2025-06-04 20:59 UTC

   Between 2025-06-04 14:11 UTC to 20:18 UTC, we experienced delays in delivering emails for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, Guard, Jira Align, Jira Product Discovery, Atlas, Compass. The issue has been resolved and the...

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Administration

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-27 06:53 UTC

   We are aware of an issue where users are receiving a 403 error when attempting to reach Administration. Our team is looking into this issue with urgency and will provide an update as soon as possible.

2. monitoring 2025-05-27 07:33 UTC

   The issues causing access problems to Administration have been resolved, and services are now functioning normally for all affected customers. We will monitor it closely for the next 30 minutes to ensure stability.

3. resolved 2025-05-27 07:56 UTC

   The issue with the Administration accessibility has now been resolved, and the service is operating normally for all affected customers.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: 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

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-05-26 05:19 UTC

   We are aware of issues relating to authentication resulting in 503 gateway error messages. Our team is investigating with urgency and will provide an update when available.

2. monitoring 2025-05-26 05:57 UTC

   A fix for the issue causing authentication errors across multiple apps has been rolled out. We will provide further update when can confirm the issue has been fully resolved.

3. resolved 2025-05-26 06:27 UTC

   Monitoring has indicated that users are no longer receiving the error messages caused by this issue and it should now be fully resolved.

Excerpts are shortened. Read the full incident on Confluence's status page.

Affected: Search

Failure mode: AI model returned degraded, wrong or empty output (not errors or timeouts). Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-05-06 01:11 UTC

   We are investigating reports of intermittent errors for Atlassian Intelligence Confluence Cloud customers. We have identified the root cause and are preparing a hotfix

2. monitoring 2025-05-06 04:38 UTC

   We have identified the root cause of the intermittent errors for Smart Answers and AI definitions in Confluence Cloud Atlassian Intelligence customers are progressively rollout out a fix to customers, with a fix expected to reach all customers over the next 2 hours. We are...

3. resolved 2025-05-06 05:55 UTC

   Between 2025/05/03 21:38 UTC to 2025/05/06 05:26 UTC, we experienced an outage in Smart Answers in search and AI definitions for all Confluence Cloud Atlassian Intelligence customers. Rovo experiences were not impacted. The issue has been resolved and the service is operating...

Excerpts are shortened. Read the full incident on Confluence's status page.