Atlassian Outage History

Started Apr 08, 2026, 05:41 AM UTC· resolved Apr 08, 2026, 11:43 AM UTC

1. investigating Apr 08, 2026, 05:41 AM 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 Apr 08, 2026, 06:01 AM 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 Apr 08, 2026, 06:01 AM 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 update within 1 hour.

4. investigating Apr 08, 2026, 06:24 AM 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 Apr 08, 2026, 06:25 AM 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 Apr 08, 2026, 06:25 AM 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 resolution. We will provide further update within 1 hour.

7. identified Apr 08, 2026, 07:40 AM 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 resolution. We will provide further update within 1 hour.

8. identified Apr 08, 2026, 07:40 AM 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 Apr 08, 2026, 08:33 AM 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 resolution. We will provide further update within 1 hour.

10. identified Apr 08, 2026, 08:33 AM 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 this page as performance fully recovers.

11. identified Apr 08, 2026, 09:03 AM 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 resolution. We will provide further update within 1 hour.

12. monitoring Apr 08, 2026, 09:03 AM 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 Apr 08, 2026, 11:43 AM UTC

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

14. postmortem Apr 17, 2026, 04:25 PM 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 Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC. ### **IMPACT** During the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period. Impacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context. **Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions. **Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue. **Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC. **Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\) was unavailable for portions of the window and fully restored at 11:37 UTC. **Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC. ### **ROOT CAUSE** Atlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. An infrastructure configuration change increased resource reservations \(CPU & Memory\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products. The change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst‑affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: * **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly. * **Strengthen automated pre‑deploy validation for resource changes** Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads. * **Improve post‑deploy verification and alerting** Enhance monitoring and post‑deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod‑IP headroom closely correlated with new configuration being rolled out. * **Align autoscaling behavior with capacity and safety limits** Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts. * **Enhance recovery automation** Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability and to reduce the risk and impact of similar issues in future. Thanks, Atlassian Customer Support

Read the full incident report →

Started Apr 08, 2026, 05:41 AM UTC· resolved Apr 08, 2026, 11:43 AM UTC

1. investigating Apr 08, 2026, 05:41 AM 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 Apr 08, 2026, 06:01 AM 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 Apr 08, 2026, 06:01 AM 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 update within 1 hour.

4. investigating Apr 08, 2026, 06:24 AM 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 Apr 08, 2026, 06:25 AM 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 Apr 08, 2026, 06:25 AM 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 resolution. We will provide further update within 1 hour.

7. identified Apr 08, 2026, 07:40 AM 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 resolution. We will provide further update within 1 hour.

8. identified Apr 08, 2026, 07:40 AM 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 Apr 08, 2026, 08:33 AM 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 resolution. We will provide further update within 1 hour.

10. identified Apr 08, 2026, 08:33 AM 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 this page as performance fully recovers.

11. identified Apr 08, 2026, 09:03 AM 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 resolution. We will provide further update within 1 hour.

12. monitoring Apr 08, 2026, 09:03 AM 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 Apr 08, 2026, 11:43 AM UTC

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

14. postmortem Apr 17, 2026, 04:24 PM 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 Atlassian Administration. A configuration change increased the resources reserved for a core system component that runs on nodes in our compute platform. On a subset of clusters configured for high‑density workloads, the increased reservations exceeded available node capacity interrupting search and related experiences for affected customers. The root cause was identified and a rollback was merged at 05:42 UTC with some systems seeing recovery by 07:33 UTC**.** Core search functionality was restored approximately by 08:55 UTC, and full downstream recovery completed by 12:09 UTC. ### **IMPACT** During the impact period, some customers experienced outages or degradation in search across Jira, Confluence, Jira Service Management, Rovo, Rovo Dev, Loom, Guard Standard, Customer Service Management and Atlassian Administration. Other experiences that rely on search such as quick find, navigation, AI assistants, dashboards, were also intermittently affected during this period. Impacted customers may have been unable to find pages or recordings and experienced degraded performance in finding issues; received empty or delayed search results; or experienced AI assistants and dashboards that could not retrieve relevant context. **Jira, Jira Service Management and Customer Service Management:** Search and experiences that depend on search like finding issues and agent responses in CSM remained available but with degraded performance in fallback mode. By 12:09 UTC, search indexes and search performance was fully restored from fallback to full capacity across all regions. **Guard Standard and Atlassian Administration:** Search functionality was unavailable for parts of the incident window. As a result, Domain Claims, usage tracking, and managed accounts were degraded for portions of the window. These services were restored to operational status by 07:33 UTC. Guard Premium was not impacted by this issue. **Confluence:** Search functionality was unavailable for parts of the incident window. Recovery began at 07:30 UTC as backend search clusters were restored. Full recovery, including search index replay, completed at 11:37 UTC. **Loom:** Search functionality and some experiences that rely on Confluence Search, such as sharing to spaces\) was unavailable for portions of the window and fully restored at 11:37 UTC. **Rovo and Rovo Dev:** Rovo agents remained responsive but experienced degraded functionality due to loss of search capabilities in underlying services. They were unable to reliably return context about work items or pages. Functionality was fully restored at 11:37 UTC. ### **ROOT CAUSE** Atlassian products rely on OpenSearch clusters to power their search capabilities including issue search, content search, and AI-powered search features. An infrastructure configuration change increased resource reservations \(CPU & Memory\) for a system component that runs across our compute platform. On a subset of clusters configured for high-density workloads, the increased reservations exceeded available node capacity. This caused search workloads to be evicted and, in some clusters, could not reschedule onto any available nodes impacting search functionality across affected products. The change was deployed across multiple production clusters in a short time frame, limiting the opportunity to detect the capacity conflict in a smaller subset of clusters before it reached the wider fleet. Automated scaling systems attempted to recover by provisioning additional capacity but in the worst‑affected clusters this led to runaway node scaling and exhaustion of available network resources, prolonging recovery time. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that service disruptions impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritizing the following actions to help reduce the likelihood and impact of similar incidents in the future and to speed up recovery when issues occur: * **Enforce smaller deployment cohorts and larger soak for critical platform changes for these cluster types** Implement smaller deployment cohorts, mandatory soak periods between environments, and automated health gates so that changes are validated on a limited set of clusters before being promoted more broadly. * **Strengthen automated pre‑deploy validation for resource changes** Add validation checks to ensure resource changes for system components are compatible with node capacity and reserved headroom, preventing system workloads from crowding out customer workloads. * **Improve post‑deploy verification and alerting** Enhance monitoring and post‑deployment verification to detect patterns such as spikes in pending pods, runaway node scaling, and low pod‑IP headroom closely correlated with new configuration being rolled out. * **Align autoscaling behavior with capacity and safety limits** Align autoscaling capacity calculations with node reservations and introduce safeguards and circuit breakers to prevent runaway scaling and to enforce safe limits on node and pod IP counts. * **Enhance recovery automation** Improve automation and runbooks so we can safely disable autoscaling, remove empty nodes in bulk, and restore normal operations faster across multiple clusters in parallel. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability and to reduce the risk and impact of similar issues in future. Thanks, Atlassian Customer Support

Read the full incident report →

Started Apr 08, 2026, 04:29 AM UTC· resolved Apr 08, 2026, 07:34 AM UTC

1. identified Apr 08, 2026, 04:29 AM UTC

   We are aware of an issue that is causing Rovo Dev code review to be unavailable for users. Our team has identified the cause of this issue and is working with urgency to resolve, and we will provide an update within 1 hour.

2. identified Apr 08, 2026, 05:22 AM UTC

   Our team is continuing to work on restoring the Rovo Dev code reviews functionality with urgency. We will provide further update within 1 hour or sooner if we see reviews commencing to run successfully prior to that time.

3. identified Apr 08, 2026, 06:33 AM UTC

   Our team has now discovered the root cause of this issue and is working on deploying a change to resolve the issue. We will provide further update within 1 hour.

4. resolved Apr 08, 2026, 07:34 AM UTC

   This issue has been resolved and Rovo Dev code review is now working as expected.

Read the full incident report →

Started Apr 02, 2026, 08:46 PM UTC· resolved Apr 02, 2026, 10:36 PM UTC

1. investigating Apr 02, 2026, 08:46 PM UTC

   We are actively investigating reports of a partial service disruption affecting Forge Remote applications integrating with JIRA. We will share updates here as more information is available.

2. resolved Apr 02, 2026, 10:36 PM UTC

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

Read the full incident report →

Started Apr 02, 2026, 01:49 AM UTC· resolved Apr 02, 2026, 02:39 AM UTC

1. investigating Apr 02, 2026, 01:49 AM UTC

   Our team is investigating an issue relating to 503 errors being displayed when attempting to load confluence.atlassian.com. We are investigating this issue with urgency and will provide an update within 1 hour.

2. monitoring Apr 02, 2026, 02:23 AM UTC

   We are now seeing recovery across confluence.atlassian.com and ja.confluence.atlassian.com sites. We are continuing to monitor the recovery and will update when we are satisfied that this incident is fully resolved.

3. resolved Apr 02, 2026, 02:39 AM UTC

   Our team has been able to successfully recover all services from confluence.atlassian.com and ja.confluence.atlassian.com and these sites are now performing as expected. This incident is now resolved. We apologize for any inconvenience that this issue may have caused.

Read the full incident report →

Started Mar 24, 2026, 07:59 AM UTC· resolved Mar 24, 2026, 08:44 AM UTC

1. identified Mar 24, 2026, 07:59 AM UTC

   We are receiving reports of degraded performance on the Connect APIs impacting Connect apps. We have identified the cause and are rolling out a fix now. We are monitoring the deployment and will provide another update within two hours, or sooner

2. resolved Mar 24, 2026, 08:44 AM UTC

   On March 24, 2026, between 04:14 AM UTC and 08:40 AM UTC, Connect Apps using connect API's experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Mar 18, 2026, 11:32 AM UTC· resolved Mar 19, 2026, 04:08 AM UTC

1. investigating Mar 18, 2026, 11:32 AM UTC

   We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

2. investigating Mar 18, 2026, 11:32 AM UTC

   Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

3. investigating Mar 18, 2026, 12:24 PM UTC

   Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

4. investigating Mar 18, 2026, 01:07 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

5. investigating Mar 18, 2026, 02:01 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

6. monitoring Mar 18, 2026, 02:03 PM UTC

   We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

7. monitoring Mar 18, 2026, 02:53 PM UTC

   We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

8. monitoring Mar 18, 2026, 09:44 PM UTC

   We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

9. monitoring Mar 18, 2026, 11:44 PM UTC

   Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

10. resolved Mar 19, 2026, 04:08 AM UTC

    The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

11. postmortem Apr 02, 2026, 07:07 AM UTC

    ### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled triggers, manual triggers, and incoming webhooks, continued to operate normally. The incident was caused by an internal configuration change that inadvertently disabled the event delivery pathway used to notify the automation platform of changes in Jira. The incident was identified through customer support tickets and verified through our monitoring; engineering teams were engaged for resolution. Once the root cause was identified, the configuration was corrected and normal automation processing resumed. Following restoration, the delayed events began flowing to the automation platform for processing. This backlog took approximately 14 hours to fully clear. During this recovery window, some automation rules ran on Work Items whose data had changed due to user actions, customer mitigation, or other causes. Since rule execution usually follows triggering events closely, many customer rules assume immediate execution on the Work Item. The delay allowed other changes —such as updates or customer actions to mitigate the incident's impact — to occur, causing unintended consequences when the rule executed later. ### **IMPACT** During the impact window, Jira Cloud customers were unable to rely on timely execution of event‑triggered automation rules. Rules that depended on Jira Work Item events - including Work Item created, Work Item updated, comment added, sprint changes, and version changes - ran with significant delays. This affected automated workflows responsible for Work Item routing, notifications, field updates, and other rule‑driven actions throughout the outage. Automation rules that used scheduled, manual, or incoming webhook triggers remained unaffected. Following mitigation, a recovery period of approximately 14 hours was required to process the backlog of delayed events. During this window, processing delays peaked at approximately 12 hours from event occurrence to rule completion. In some cases, rules executing against Work Item data several hours after the rule trigger occurred, caused problems due to the rules being built with the expectation in mind that little time would pass between trigger and execution. This resulted in Work Items ending up in an unintended state; especially as some customers undertook manual intervention given the situation. ### **ROOT CAUSE** The incident was caused by a configuration change to an internal feature flag used to control event delivery to the automation platform. A code change had been prepared to remove a feature flag from the event delivery system. However, this code change had not yet been deployed to production. When the feature flag was subsequently retired through our feature flag management system, the retirement process relied on usage telemetry that incorrectly indicated the flag was no longer active. This inadvertently created a blind spot where the flag appeared unused when it was in fact being actively evaluated. When the flag was retired, the event delivery system interpreted its absence as an instruction to stop delivering Jira events to the automation platform, causing all event-triggered automation rules to stop firing. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritising the following actions to help reduce the likelihood and impact of similar incidents in the future: * **Strengthen feature flag lifecycle safety controls** * Address the telemetry gap by removing feature flagged code from the hot path of our event processing framework where it was being surpressed, ensuring we have good telemetry on feature flag use across our systems. This will prevent inadvertent archival of feature flags in future. * Refine feature flag retirement processes so that flags cannot be retired without verifying actual production usage, independent of standard telemetry signals. * **Improve event delivery monitoring and alerting** * Refine monitoring to detect drops in automation event delivery rates within minutes, and add automated alerting on automation execution volume anomalies to enable faster detection of disruptions. * **Improve our ability to clear delayed events faster and deliver controls for customers to decide alternative workflows for events based on delay.** * Refine replay infrastructure to recover faster from the pent up backlog that can be created due to delays. * Provide workflow components that allow users to decide what to do for varying delays between the triggering event and when the rule gets executed to reduce the risk of unintended changes during recovery. We recognise the importance of Jira Automation to our customers' workflows and are committed to ongoing improvements to the reliability and resilience of our platform. We sincerely apologize for the disruption this incident caused, and we will continue to invest in measures that support a stable and dependable service. Thanks, Atlassian Customer Support

Read the full incident report →

Started Mar 18, 2026, 11:32 AM UTC· resolved Mar 19, 2026, 04:08 AM UTC

1. investigating Mar 18, 2026, 11:32 AM UTC

   We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

2. investigating Mar 18, 2026, 11:32 AM UTC

   Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

3. investigating Mar 18, 2026, 12:24 PM UTC

   Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

4. investigating Mar 18, 2026, 01:07 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

5. investigating Mar 18, 2026, 02:01 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

6. monitoring Mar 18, 2026, 02:03 PM UTC

   We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

7. monitoring Mar 18, 2026, 02:53 PM UTC

   We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

8. monitoring Mar 18, 2026, 09:44 PM UTC

   We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

9. monitoring Mar 18, 2026, 11:44 PM UTC

   Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

10. resolved Mar 19, 2026, 04:08 AM UTC

    The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

11. postmortem Apr 02, 2026, 07:07 AM UTC

    ### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled triggers, manual triggers, and incoming webhooks, continued to operate normally. The incident was caused by an internal configuration change that inadvertently disabled the event delivery pathway used to notify the automation platform of changes in Jira. The incident was identified through customer support tickets and verified through our monitoring; engineering teams were engaged for resolution. Once the root cause was identified, the configuration was corrected and normal automation processing resumed. Following restoration, the delayed events began flowing to the automation platform for processing. This backlog took approximately 14 hours to fully clear. During this recovery window, some automation rules ran on Work Items whose data had changed due to user actions, customer mitigation, or other causes. Since rule execution usually follows triggering events closely, many customer rules assume immediate execution on the Work Item. The delay allowed other changes —such as updates or customer actions to mitigate the incident's impact — to occur, causing unintended consequences when the rule executed later. ### **IMPACT** During the impact window, Jira Cloud customers were unable to rely on timely execution of event‑triggered automation rules. Rules that depended on Jira Work Item events - including Work Item created, Work Item updated, comment added, sprint changes, and version changes - ran with significant delays. This affected automated workflows responsible for Work Item routing, notifications, field updates, and other rule‑driven actions throughout the outage. Automation rules that used scheduled, manual, or incoming webhook triggers remained unaffected. Following mitigation, a recovery period of approximately 14 hours was required to process the backlog of delayed events. During this window, processing delays peaked at approximately 12 hours from event occurrence to rule completion. In some cases, rules executing against Work Item data several hours after the rule trigger occurred, caused problems due to the rules being built with the expectation in mind that little time would pass between trigger and execution. This resulted in Work Items ending up in an unintended state; especially as some customers undertook manual intervention given the situation. ### **ROOT CAUSE** The incident was caused by a configuration change to an internal feature flag used to control event delivery to the automation platform. A code change had been prepared to remove a feature flag from the event delivery system. However, this code change had not yet been deployed to production. When the feature flag was subsequently retired through our feature flag management system, the retirement process relied on usage telemetry that incorrectly indicated the flag was no longer active. This inadvertently created a blind spot where the flag appeared unused when it was in fact being actively evaluated. When the flag was retired, the event delivery system interpreted its absence as an instruction to stop delivering Jira events to the automation platform, causing all event-triggered automation rules to stop firing. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritising the following actions to help reduce the likelihood and impact of similar incidents in the future: * **Strengthen feature flag lifecycle safety controls** * Address the telemetry gap by removing feature flagged code from the hot path of our event processing framework where it was being surpressed, ensuring we have good telemetry on feature flag use across our systems. This will prevent inadvertent archival of feature flags in future. * Refine feature flag retirement processes so that flags cannot be retired without verifying actual production usage, independent of standard telemetry signals. * **Improve event delivery monitoring and alerting** * Refine monitoring to detect drops in automation event delivery rates within minutes, and add automated alerting on automation execution volume anomalies to enable faster detection of disruptions. * **Improve our ability to clear delayed events faster and deliver controls for customers to decide alternative workflows for events based on delay.** * Refine replay infrastructure to recover faster from the pent up backlog that can be created due to delays. * Provide workflow components that allow users to decide what to do for varying delays between the triggering event and when the rule gets executed to reduce the risk of unintended changes during recovery. We recognise the importance of Jira Automation to our customers' workflows and are committed to ongoing improvements to the reliability and resilience of our platform. We sincerely apologize for the disruption this incident caused, and we will continue to invest in measures that support a stable and dependable service. Thanks, Atlassian Customer Support

Read the full incident report →

Started Mar 18, 2026, 11:29 AM UTC· resolved Mar 19, 2026, 04:08 AM UTC

1. investigating Mar 18, 2026, 11:29 AM UTC

   We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

2. investigating Mar 18, 2026, 11:32 AM UTC

   Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

3. investigating Mar 18, 2026, 12:24 PM UTC

   Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

4. investigating Mar 18, 2026, 01:07 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

5. investigating Mar 18, 2026, 02:01 PM UTC

   We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

6. monitoring Mar 18, 2026, 02:03 PM UTC

   We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

7. monitoring Mar 18, 2026, 02:53 PM UTC

   We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

8. monitoring Mar 18, 2026, 09:44 PM UTC

   We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

9. monitoring Mar 18, 2026, 11:44 PM UTC

   Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

10. resolved Mar 19, 2026, 04:08 AM UTC

    The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

11. postmortem Apr 02, 2026, 07:08 AM UTC

    ### Summary On March 18, 2026, between 10:06 and 13:47 UTC, customers experienced delays in Automation rules executing when triggered by Jira events such as Work Item creation, Work Item updates, and comments. Automation rules using other trigger types, including scheduled triggers, manual triggers, and incoming webhooks, continued to operate normally. The incident was caused by an internal configuration change that inadvertently disabled the event delivery pathway used to notify the automation platform of changes in Jira. The incident was identified through customer support tickets and verified through our monitoring; engineering teams were engaged for resolution. Once the root cause was identified, the configuration was corrected and normal automation processing resumed. Following restoration, the delayed events began flowing to the automation platform for processing. This backlog took approximately 14 hours to fully clear. During this recovery window, some automation rules ran on Work Items whose data had changed due to user actions, customer mitigation, or other causes. Since rule execution usually follows triggering events closely, many customer rules assume immediate execution on the Work Item. The delay allowed other changes —such as updates or customer actions to mitigate the incident's impact — to occur, causing unintended consequences when the rule executed later. ### **IMPACT** During the impact window, Jira Cloud customers were unable to rely on timely execution of event‑triggered automation rules. Rules that depended on Jira Work Item events - including Work Item created, Work Item updated, comment added, sprint changes, and version changes - ran with significant delays. This affected automated workflows responsible for Work Item routing, notifications, field updates, and other rule‑driven actions throughout the outage. Automation rules that used scheduled, manual, or incoming webhook triggers remained unaffected. Following mitigation, a recovery period of approximately 14 hours was required to process the backlog of delayed events. During this window, processing delays peaked at approximately 12 hours from event occurrence to rule completion. In some cases, rules executing against Work Item data several hours after the rule trigger occurred, caused problems due to the rules being built with the expectation in mind that little time would pass between trigger and execution. This resulted in Work Items ending up in an unintended state; especially as some customers undertook manual intervention given the situation. ### **ROOT CAUSE** The incident was caused by a configuration change to an internal feature flag used to control event delivery to the automation platform. A code change had been prepared to remove a feature flag from the event delivery system. However, this code change had not yet been deployed to production. When the feature flag was subsequently retired through our feature flag management system, the retirement process relied on usage telemetry that incorrectly indicated the flag was no longer active. This inadvertently created a blind spot where the flag appeared unused when it was in fact being actively evaluated. When the flag was retired, the event delivery system interpreted its absence as an instruction to stop delivering Jira events to the automation platform, causing all event-triggered automation rules to stop firing. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We understand that outages impact your productivity. In addition to our existing testing and preventative processes, Atlassian is prioritising the following actions to help reduce the likelihood and impact of similar incidents in the future: * **Strengthen feature flag lifecycle safety controls** * Address the telemetry gap by removing feature flagged code from the hot path of our event processing framework where it was being surpressed, ensuring we have good telemetry on feature flag use across our systems. This will prevent inadvertent archival of feature flags in future. * Refine feature flag retirement processes so that flags cannot be retired without verifying actual production usage, independent of standard telemetry signals. * **Improve event delivery monitoring and alerting** * Refine monitoring to detect drops in automation event delivery rates within minutes, and add automated alerting on automation execution volume anomalies to enable faster detection of disruptions. * **Improve our ability to clear delayed events faster and deliver controls for customers to decide alternative workflows for events based on delay.** * Refine replay infrastructure to recover faster from the pent up backlog that can be created due to delays. * Provide workflow components that allow users to decide what to do for varying delays between the triggering event and when the rule gets executed to reduce the risk of unintended changes during recovery. We recognise the importance of Jira Automation to our customers' workflows and are committed to ongoing improvements to the reliability and resilience of our platform. We sincerely apologize for the disruption this incident caused, and we will continue to invest in measures that support a stable and dependable service. Thanks, Atlassian Customer Support

Read the full incident report →

Started Mar 17, 2026, 10:59 AM UTC· resolved Mar 17, 2026, 11:37 AM UTC

1. investigating Mar 17, 2026, 10:59 AM UTC

   Impact The outage is impacting our Forge apps and Developer console, specifically due to cs-apps APIs, resulting in 500 error messages for customers attempting to use these services. This incident is causing disruption in creating, updating, and deploying applications, although direct app usage is not affected. Similarly, developer console is impacted. Current Status Our teams are actively working to restore full functionality. The current focus is on addressing a database connectivity issue that seems to be causing the errors. Investigation is ongoing, with efforts concentrated on isolating the root cause through various technical checks. Next Steps The incident team is prioritising the investigation of database connectivity to rectify the errors impacting cs-apps APIs.

2. investigating Mar 17, 2026, 10:59 AM UTC

   We are investigating an incident impacting Forge app management and related developer tooling. Customers may experience errors when attempting to: -Install, upgrade, or deploy Forge apps -Use Forge app tunnelling (particularly newly created tunnels and tunnels older than 30 minutes) -Access or manage apps via the Atlassian Developer Console In addition, some underlying app platform capabilities used by Forge and related services are affected, including: -Certain app data residency operations -Rovo MCP consent flows and other app management operations that rely on the app platform At this time, existing Forge apps continue to run, and app invocations are not impacted. Our engineering teams are actively investigating the issue and working to restore normal operation. We will provide the next update in 60 mins or sooner if we have significant progress to share.

3. resolved Mar 17, 2026, 11:37 AM UTC

   On March 17th, 2026, between 9:05 AM UTC and 11:10 AM UTC, Forge app management and related developer tooling experienced some service disruption. The issue has now been resolved, and the service is operating normally for affected customers.

Read the full incident report →

Started Mar 17, 2026, 10:05 AM UTC· resolved Mar 17, 2026, 11:37 AM UTC

1. investigating Mar 17, 2026, 10:05 AM UTC

   We are actively investigating reports of performance degradation affecting Forge apps and Developer console will share updates here as more information becomes available.

2. investigating Mar 17, 2026, 10:34 AM UTC

   We are continuing to investigate this issue.

3. investigating Mar 17, 2026, 10:59 AM UTC

   We are investigating an incident impacting Forge app management and related developer tooling. Customers may experience errors when attempting to: -Install, upgrade, or deploy Forge apps -Use Forge app tunnelling (particularly newly created tunnels and tunnels older than 30 minutes) -Access or manage apps via the Atlassian Developer Console In addition, some underlying app platform capabilities used by Forge and related services are affected, including: -Certain app data residency operations -Rovo MCP consent flows and other app management operations that rely on the app platform At this time, existing Forge apps continue to run, and app invocations are not impacted. Our engineering teams are actively investigating the issue and working to restore normal operation. We will provide the next update in 60 mins or sooner if we have significant progress to share.

4. resolved Mar 17, 2026, 11:37 AM UTC

   On March 17th, 2026, between 9:05 AM UTC and 11:10 AM UTC, Forge app management and related developer tooling experienced some service disruption. The issue has now been resolved, and the service is operating normally for affected customers.

Read the full incident report →

Started Mar 12, 2026, 11:42 AM UTC· resolved Mar 13, 2026, 12:26 AM UTC

1. investigating Mar 12, 2026, 11:42 AM 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 hours, or sooner.

2. investigating Mar 12, 2026, 01:38 PM 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 hours, or sooner.

3. identified Mar 12, 2026, 01:38 PM 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 Mar 13, 2026, 12:26 AM 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.

Read the full incident report →

Started Mar 12, 2026, 11:42 AM UTC· resolved Mar 13, 2026, 12:26 AM UTC

1. investigating Mar 12, 2026, 11:42 AM 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 hours, or sooner.

2. investigating Mar 12, 2026, 01:38 PM 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 hours, or sooner.

3. identified Mar 12, 2026, 01:38 PM 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 Mar 13, 2026, 12:26 AM 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.

Read the full incident report →

Started Mar 12, 2026, 08:48 AM UTC· resolved Mar 12, 2026, 12:33 PM UTC

1. investigating Mar 12, 2026, 08:48 AM UTC

   We are actively investigating a service disruption impacting Bitbucket for some customers. We'll share updates here as more information is available.

2. investigating Mar 12, 2026, 09:40 AM UTC

   We are actively investigating reports of a service disruption affecting Bitbucket Cloud. We'll share updates here within the next hour or as more information is available.

3. investigating Mar 12, 2026, 10:52 AM UTC

   Our engineers are actively working to resolve the Bitbucket Cloud disruption. No new updates at this moment. We will share more details within the next hour or as soon as we more information is available.

4. investigating Mar 12, 2026, 12:05 PM UTC

   Our engineers continue to work actively to identify the root cause. Meanwhile, the affected service is now stable and the error rate has decreased. We will share more details within the next hour, or sooner if more information becomes available.

5. resolved Mar 12, 2026, 12:33 PM UTC

   We have successfully mitigated the incident, and the affected service is now fully operational. Our teams have verified that normal functionality has been restored and the service is performing as expected.

Read the full incident report →

Started Mar 10, 2026, 12:15 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 10, 2026, 12:06 AM UTC· resolved Mar 10, 2026, 12:59 AM UTC

1. investigating Mar 10, 2026, 12:06 AM 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 Mar 10, 2026, 12:15 AM 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 Mar 10, 2026, 12:51 AM 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 Mar 10, 2026, 12:59 AM 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 affected customers.

Read the full incident report →

Started Mar 02, 2026, 04:15 PM UTC· resolved Mar 04, 2026, 03:04 AM UTC

1. monitoring Mar 02, 2026, 04:15 PM UTC

   Since Feb 27, 2026 some Marketplace Partners may see incorrect install counts in their Marketplace Partner Portal and listing for their apps. The Marketplace team has identified the bug and is working to correct the same. Please note, the actual customer installs for these apps remain unaffected. As next Steps, the Marketplace team is working on a fix and expects to restore accurate install counts by Mar 3, 2026, EOD.

2. monitoring Mar 03, 2026, 05:06 PM UTC

   We are providing an update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The install counts displayed on app listings are now accurate for the impacted apps. - The Active Installations tab in the Marketplace Partner Portal may still reflect incorrect counts for some apps; this will be corrected following tonight's scheduled update at 12:00 AM UTC on Mar 4, 2026. - Please note that actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps. We will share another update once the Partner Portal Active Installations tab has been fully corrected and validated. Thank you for your patience and understanding.

3. resolved Mar 04, 2026, 03:04 AM UTC

   We are providing a further update regarding the install count discrepancy that some partners may have observed for some apps since Feb 27, 2026. - The Active Installations tab in the Marketplace Partner Portal is now showing accurate install counts for impacted apps from Mar 3, 2026 onward. - The install counts displayed on app listings remain accurate for impacted apps. - Please note that data from Mar 3, 2026 onward will remain accurate going forward. - You may notice a temporary dip in install counts for Mar 2, 2026. We are backfilling the data, and counts for that date will be restored once complete. - Actual customer installs were not impacted; only the reported counts displayed in the Partner Portal and on app listings were affected for some apps, and this is now fully functional. Thank you for your patience and understanding.

Read the full incident report →

Started Feb 26, 2026, 01:22 PM UTC· resolved Feb 26, 2026, 06:55 PM UTC

1. investigating Feb 26, 2026, 01:22 PM UTC

   Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.

2. investigating Feb 26, 2026, 02:25 PM UTC

   We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.

3. investigating Feb 26, 2026, 04:21 PM UTC

   We continue to investigate the issue, and will share an update within next 2 hours or sooner.

4. identified Feb 26, 2026, 06:05 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available.

5. monitoring Feb 26, 2026, 06:33 PM UTC

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

6. resolved Feb 26, 2026, 06:55 PM UTC

   On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 26, 2026, 01:22 PM UTC· resolved Feb 26, 2026, 06:55 PM UTC

1. investigating Feb 26, 2026, 01:22 PM UTC

   Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.

2. investigating Feb 26, 2026, 02:25 PM UTC

   We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.

3. investigating Feb 26, 2026, 04:21 PM UTC

   We continue to investigate the issue, and will share an update within next 2 hours or sooner.

4. identified Feb 26, 2026, 06:05 PM UTC

   We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM. We will continue to share additional updates here as more information is available.

5. monitoring Feb 26, 2026, 06:33 PM UTC

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

6. resolved Feb 26, 2026, 06:55 PM UTC

   On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.

Read the full incident report →

Started Feb 21, 2026, 03:32 PM UTC· resolved Feb 21, 2026, 03:32 PM UTC

1. investigating Feb 21, 2026, 03:32 PM UTC

   Impact Trello users are experiencing issues with websocket connections, leading to difficulties in maintaining active sessions. Affected users may notice disruptions in service as connections are intermittently dropping. Current Status Efforts are underway to restore normal service. Teams are actively engaged in identifying the best path to full resolution. Next Steps The incident team is focusing on pinpointing the root cause and implementing necessary fixes. The next communication will be shared in 30 minutes.

2. resolved Feb 21, 2026, 03:32 PM UTC

   Impact Trello users are experiencing issues with websocket connections, leading to difficulties in maintaining active sessions. Affected users may notice disruptions in service as connections are intermittently dropping. Current Status Efforts are underway to restore normal service. Teams are actively engaged in identifying the best path to full resolution. Next Steps The incident team is focusing on pinpointing the root cause and implementing necessary fixes. The next communication will be shared in 30 minutes.

Read the full incident report →