Atlassian Outage History

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 04:55 AM 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 into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 05:39 AM 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 provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM 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 would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM 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.

Read the full incident report →

Started Jun 10, 2026, 04:55 AM UTC· resolved Jun 10, 2026, 06:31 AM UTC

1. investigating Jun 10, 2026, 04:55 AM 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 into this with urgency and we will provide further update within one hour as our investigation continues.

2. identified Jun 10, 2026, 05:39 AM 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 provide further update within one hour or when we have seen a full recovery of all task processing across these products.

3. monitoring Jun 10, 2026, 06:14 AM 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 would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway. We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.

4. resolved Jun 10, 2026, 06:31 AM 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.

Read the full incident report →

Started Jun 09, 2026, 05:29 AM UTC· resolved Jun 09, 2026, 06:28 PM UTC

1. investigating Jun 09, 2026, 05:29 AM UTC

   We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

2. identified Jun 09, 2026, 06:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

3. identified Jun 09, 2026, 06:22 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

4. identified Jun 09, 2026, 09:26 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

5. identified Jun 09, 2026, 09:27 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

6. identified Jun 09, 2026, 10:20 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

7. identified Jun 09, 2026, 10:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

8. monitoring Jun 09, 2026, 10:36 AM UTC

   Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability.

9. resolved Jun 09, 2026, 06:28 PM UTC

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

Read the full incident report →

Started Jun 09, 2026, 05:29 AM UTC· resolved Jun 09, 2026, 06:27 PM UTC

1. investigating Jun 09, 2026, 05:29 AM UTC

   We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

2. identified Jun 09, 2026, 06:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

3. identified Jun 09, 2026, 06:22 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

4. identified Jun 09, 2026, 09:26 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

5. identified Jun 09, 2026, 09:27 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

6. identified Jun 09, 2026, 10:20 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

7. identified Jun 09, 2026, 10:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

8. monitoring Jun 09, 2026, 10:36 AM UTC

   Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability.

9. resolved Jun 09, 2026, 06:27 PM UTC

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

Read the full incident report →

Started Jun 09, 2026, 05:29 AM UTC· resolved Jun 09, 2026, 06:27 PM UTC

1. investigating Jun 09, 2026, 05:29 AM UTC

   We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers. We will provide further updates within one hour.

2. identified Jun 09, 2026, 06:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

3. identified Jun 09, 2026, 06:22 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

4. identified Jun 09, 2026, 09:26 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

5. identified Jun 09, 2026, 09:27 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

6. identified Jun 09, 2026, 10:20 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

7. identified Jun 09, 2026, 10:21 AM UTC

   Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours. We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.

8. monitoring Jun 09, 2026, 10:36 AM UTC

   Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations. We will continue to actively monitor over the next 8 hours to confirm stability.

9. resolved Jun 09, 2026, 06:27 PM UTC

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

Read the full incident report →

Started Jun 08, 2026, 01:53 AM UTC· resolved Jun 08, 2026, 02:56 AM UTC

1. investigating Jun 08, 2026, 01:53 AM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. identified Jun 08, 2026, 02:36 AM UTC

   We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. resolved Jun 08, 2026, 02:56 AM UTC

   On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Started Jun 08, 2026, 01:53 AM UTC· resolved Jun 08, 2026, 02:56 AM UTC

1. investigating Jun 08, 2026, 01:53 AM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. identified Jun 08, 2026, 02:36 AM UTC

   We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. resolved Jun 08, 2026, 02:56 AM UTC

   On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Started Jun 08, 2026, 01:53 AM UTC· resolved Jun 08, 2026, 02:56 AM UTC

1. investigating Jun 08, 2026, 01:53 AM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. identified Jun 08, 2026, 02:36 AM UTC

   We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. resolved Jun 08, 2026, 02:56 AM UTC

   On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions. We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.

Read the full incident report →

Started Jun 06, 2026, 11:21 PM UTC· resolved Jun 07, 2026, 12:13 AM UTC

1. investigating Jun 06, 2026, 11:21 PM UTC

   We are aware of users currently experiencing loading work items across Atlassian products in some regions. We are investigating with urgency and will provide update within one hour.

2. monitoring Jun 07, 2026, 12:07 AM UTC

   A fix has been implemented for the issues some customers have been experiencing with creating and viewing work items in Jira. We are now monitoring for this recovery and will update shortly with further confirmation.

3. resolved Jun 07, 2026, 12:13 AM UTC

   The issues relating to viewing and creating work items in Jira should now be fully resolved.

Read the full incident report →

Started Jun 02, 2026, 03:32 PM UTC· resolved Jun 02, 2026, 04:51 PM UTC

1. investigating Jun 02, 2026, 03:32 PM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. resolved Jun 02, 2026, 04:51 PM UTC

   On June 6, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

Read the full incident report →

Started Jun 02, 2026, 03:32 PM UTC· resolved Jun 02, 2026, 04:51 PM UTC

1. investigating Jun 02, 2026, 03:32 PM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. resolved Jun 02, 2026, 04:51 PM UTC

   On June 6, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

Read the full incident report →

Started Jun 02, 2026, 03:32 PM UTC· resolved Jun 02, 2026, 04:51 PM UTC

1. investigating Jun 02, 2026, 03:32 PM UTC

   We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.

2. resolved Jun 02, 2026, 04:51 PM UTC

   On June 6, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

Read the full incident report →

Started Jun 01, 2026, 08:06 AM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 08:06 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. identified Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:07 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. resolved Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

5. postmortem Jun 12, 2026, 06:49 AM UTC

   **SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences across Jira Software, Jira Service Management, and Jira Work Management. **ROOT CAUSE** The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity. Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected. With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring. - **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 01, 2026, 08:06 AM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 08:06 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. identified Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:07 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. resolved Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

5. postmortem Jun 12, 2026, 06:49 AM UTC

   **SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences across Jira Software, Jira Service Management, and Jira Work Management. **ROOT CAUSE** The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity. Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected. With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring. - **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 01, 2026, 08:06 AM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 08:06 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. identified Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:08 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. resolved Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

5. postmortem Jun 12, 2026, 06:49 AM UTC

   **SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences across Jira Software, Jira Service Management, and Jira Work Management. **ROOT CAUSE** The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity. Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected. With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring. - **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 01, 2026, 08:06 AM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 08:06 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. identified Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:08 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. resolved Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

5. postmortem Jun 12, 2026, 06:49 AM UTC

   **SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences across Jira Software, Jira Service Management, and Jira Work Management. **ROOT CAUSE** The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity. Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected. With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring. - **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started Jun 01, 2026, 07:40 AM UTC· resolved Jun 01, 2026, 01:23 PM UTC

1. investigating Jun 01, 2026, 07:40 AM UTC

   We are investigating cases of partial-outage for Jira-software in the EU Region. We will provide more details within the next hour.

2. identified Jun 01, 2026, 08:06 AM UTC

   We have identified an issue causing degraded performance for Jira Software, Jira Work Management, and Jira Service Management in the EU region. affected users may experience 5XX errors when accessing issues, boards, and navigation. Our engineering team is actively working on a resolution. We will provide an update within the next hour.

3. monitoring Jun 01, 2026, 09:07 AM UTC

   We have implemented a fix for the issue causing degraded performance for Jira Software and Jira Service Management in the EU region. The impact has been mitigated, and we are actively monitoring the stability.

4. resolved Jun 01, 2026, 01:23 PM UTC

   This incident has been resolved. The issue causing degraded performance for Jira Software and Jira Service Management in the EU region has been fully mitigated. We have deployed a fix to prevent recurrence. If you continue to experience issues, please contact Atlassian Support. We apologise for the disruption and thank you for your patience.

5. postmortem Jun 12, 2026, 06:49 AM UTC

   **SUMMARY** On June 01, 2026, between 06:54 and 08:28 UTC, Atlassian customers using Jira, Jira Service Management, and Jira Work Management were unable to view issues, boards, and backlogs, and experienced errors when performing transitions, adding comments, and navigating the product. The event was triggered by caching infrastructure autoscaling failure. The issue only impacted customers hosted in Europe. The incident was detected within 8 minutes by our automated monitoring system and mitigated by progressively scaling the caching clusters manually. The total time to resolution was 1 hour and 34 minutes due to the progressive recovery. **IMPACT** The incident caused service disruption for customers hosted in the Europe region who were unable to access core experiences across Jira Software, Jira Service Management, and Jira Work Management. **ROOT CAUSE** The root cause of the incident was a capacity constraint on our caching infrastructure in one availability zone of our EU Central cloud region. As morning traffic increased, our caching clusters attempted to scale out automatically. However, the cloud infrastructure was unable to provision additional nodes in that availability zone due to insufficient underlying capacity. Our caching infrastructure is designed to scale across multiple availability zones to ensure balanced and resilient capacity. On this occasion, a capacity constraint in one availability zone prevented the scaling operation from completing as expected. With the caching layer unable to grow to meet demand, the clusters began to experience network and/or CPU saturation and could not handle all incoming requests within the expected timeout window. Since a single user request to Jira typically involves multiple cache calls, timeouts compound rapidly. As more threads became blocked waiting on timed-out or slow cache operations, the application nodes reached its busy thread limit and began shedding load. While additional application nodes were added, these also experienced the same thread limit saturation due to the saturation of the cache layer resulting in widespread 503 service unavailable errors for customers. **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. In addition to existing safeguards and monitoring, Atlassian is prioritizing the following actions to help prevent similar incidents in future: - **Increased minimum caching cluster size**: We have increased the minimum number of nodes in all affected caching clusters in the EU Central region. This ensures sufficient capacity headroom to handle peak traffic without relying on autoscaling, reducing the risk of a similar failure occurring. - **Change autoscaling behaviour**: We are working on improvements to our autoscaling behaviour to fall back to other availability zones when capacity is unavailable in a single zone. We apologize to customers whose services were impacted during this incident; we are taking immediate steps to improve the platform’s performance and availability. Thanks, Atlassian Customer Support

Read the full incident report →

Started May 27, 2026, 06:03 AM UTC· resolved May 27, 2026, 07:48 AM UTC

1. investigating May 27, 2026, 06:03 AM 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 available.

2. identified May 27, 2026, 07:06 AM 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 May 27, 2026, 07:48 AM 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.

Read the full incident report →

Started May 26, 2026, 10:40 AM UTC· resolved May 26, 2026, 01:55 PM UTC

1. investigating May 26, 2026, 10:40 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. investigating May 26, 2026, 11:58 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

3. investigating May 26, 2026, 11:58 AM 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 May 26, 2026, 01:55 PM 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.

Read the full incident report →

Started May 26, 2026, 10:40 AM UTC· resolved May 26, 2026, 01:55 PM UTC

1. investigating May 26, 2026, 10:40 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

2. investigating May 26, 2026, 11:58 AM 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 pages is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within an hour or as more information becomes available.

3. investigating May 26, 2026, 11:58 AM 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 May 26, 2026, 01:55 PM 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.

Read the full incident report →

Started May 20, 2026, 12:06 PM UTC· resolved May 20, 2026, 02:14 PM UTC

1. identified May 20, 2026, 12:06 PM UTC

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

2. resolved May 20, 2026, 02:14 PM UTC

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Started May 20, 2026, 10:16 AM UTC· resolved May 20, 2026, 10:16 AM UTC

1. resolved May 20, 2026, 10:16 AM UTC

   Due to an incorrect deployment, a banner stating 'This app may stop working soon' was briefly displayed on the Marketplace Apps. This banner was not intended to appear on these apps. The feature has since been corrected and the banner is no longer appearing. No action is required, the banner was displayed in error and there is no impact to app functionality or availability. We apologise for any confusion this may have caused.

Read the full incident report →

Started May 20, 2026, 09:17 AM UTC· resolved May 20, 2026, 02:14 PM UTC

1. investigating May 20, 2026, 09:17 AM UTC

   Users are reporting an issue with Forge custom fields not getting created on Jira work items page, after deploying an application. Our teams are investigating the issue and more updates will be shared within next 2 hour or sooner.

2. investigating May 20, 2026, 11:20 AM UTC

   Our teams are actively working on the identifying the root cause and we will provide an update within 3 hours, or sooner if there is any significant progress. Thank you for your patience.

3. identified May 20, 2026, 12:06 PM UTC

   Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

4. resolved May 20, 2026, 02:14 PM UTC

   The root cause has been identified and a fix has been applied. Full service restoration has been completed.

Read the full incident report →

Started May 17, 2026, 02:11 PM UTC· resolved May 26, 2026, 09:12 PM UTC

1. investigating May 17, 2026, 02:11 PM UTC

   Users may be experiencing slowdowns across various functions of Trello including creating/deleting comments, editing cards, or creating new attachments. The team is actively working to fix the issue and will provide more updates within the hour.

2. identified May 17, 2026, 03:13 PM UTC

   The team has identified the root cause and is hard at working resolving this issue. Users will see problems creating/updating/deleting comments and loading the activity view for cards at this time. The rest of Trello's features should be working as normal. We will provide more updates within 2h.

3. identified May 17, 2026, 04:25 PM UTC

   Work by the Trello engineering team continues to restore functionality to comments and activity views. Next update will be posted within 4h or on a significant change. Thank you for your patience.

4. identified May 17, 2026, 09:03 PM UTC

   Work by the Trello engineering team continues to restore functionality to comments and activity views. Recovery of the affected systems is taking longer than anticipated. Next update will be posted within 4h or on a significant change. Thank you for your patience.

5. identified May 18, 2026, 12:53 AM UTC

   Trello is experiencing slowdowns and failures affecting comment operations, including creating and deleting comments. Users may also experience delays when loading activity views on cards, viewing attachments, using Power-Ups, or exporting boards. Some users are encountering errors when viewing specific cards. The team is working hard to restore full functionality and will provide another update within 3h.

6. identified May 18, 2026, 03:51 AM UTC

   Trello is experiencing slowdowns and failures affecting comment operations, including creating and deleting comments. Users may also experience delays when loading activity views on cards, viewing attachments, using Power-Ups, exporting boards and 'Updates' on home page. Our team is actively working on the resolution and will likely take up to 7 hours to restore the services back to full functionality. We will provide further update at this time, or earlier if we have additional information to share prior to this resolution.

7. identified May 18, 2026, 10:14 AM UTC

   Trello continues to experience slowdowns and failures that are affecting comment operations, including creating and deleting comments. Our teams continue to work on the issue resolution, while it is taking longer than expected. We will provide more updates within the next 8 hours or sooner once we have further information to share.

8. identified May 18, 2026, 06:09 PM UTC

   Our teams continue to work diligently on the mitigation. During this time, we recommend that you do not move or copy cards or lists between boards. For users whose boards are affected by this issue, you may create and delete cards and edit card descriptions as usual, but you will not be able to see comments or the detailed activity log of the cards. We estimate that the rebuild will take another 24 hours to complete. We will update this page as we have more information.

9. identified May 18, 2026, 10:45 PM UTC

   We want to provide more transparency regarding this incident given its duration. We were optimizing one of our largest databases, specifically the one storing comments and card activity. At the end of this process, a bug caused some database partitions to go live without their indexes. This means queries to those partitions are timing out, which is why approximately 40 percent of boards are experiencing failures. Your data is safe. Any comments added during this incident are being saved and will reappear once the process is complete. We are currently rebuilding the missing indexes. We have allocated significant compute resources to this task to move as quickly as possible, but the data volume is enormous. We estimate it will take approximately 20 more hours to reach full resolution. Most impacted features include, but are not limited to: - Comments (viewing, adding, notifications) - Activity views on cards - Attachments, Power-Ups, board exports - Home page / 'Updates' view - Search - Some cards showing 'Card Not Found' - Moving/copying cards or lists Please avoid moving or copying cards between boards for now. If your board is working normally, you can continue your work, as most boards remain unaffected. We know Trello is where your work lives and we are committed to getting everything back to normal. We will provide next update in eight hours or sooner as we make progress.

10. identified May 19, 2026, 07:03 AM UTC

    We are continuing to monitor the index rebuild process across all affected shards and will provide updates as each phase completes. We will provide next update in eight hours or sooner as we make progress.

11. monitoring May 19, 2026, 02:26 PM UTC

    Index rebuild is complete and functionality should be restored for users. We are aware that cards moved by users during the incident may be in an incomplete state and we are investigating solutions. We have no indication of data loss during the incident. We will continue to monitor and will provide the next updates in 4 hours or sooner.

12. monitoring May 19, 2026, 06:01 PM UTC

    Users should be experiencing restored functionality to their boards and cards. We are running scripts to replay actions that occurred during the incident. We will update once these are complete.

13. monitoring May 20, 2026, 07:06 PM UTC

    Users should be experiencing restored functionality to their boards and cards. The team continues to remediate potential outstanding data issues that occurred on Boards and Cards during the incident. Below is a list of remaining issues that may still be occurring, but we are currently working to resolve via processing on our end. These issues were caused by card moves between boards during the incident. - Missing card labels - Attachment restrictions not being enforced on moved cards - Checklist assignees that are not a member of the current board may incorrectly linger - Card assignees that are not a member of the current board may have incorrectly received due date reminders Please note that cards are safe to edit, but they may be excluded from certain restoration work if they are edited.

We greatly appreciate your patience as we work through these issues. We will provide another update when above issues are resolved. In the meantime, please reach out to our support team if you need further assistance.

14. monitoring May 21, 2026, 09:29 PM UTC

    The team continues to remediate potential outstanding data issues that occurred on Boards and Cards during the incident (details are in yesterday's update). Users should be experiencing restored functionality to their boards and cards. Please note that while cards are safe to edit, they may be excluded from certain restoration work if they are edited. We greatly appreciate your patience as we work through these issues. Please reach out to our support team if you need further assistance.

15. monitoring May 22, 2026, 07:51 PM UTC

    Users should be experiencing restored functionality to their boards and cards. Our team has resolved 'card not found' errors, and continues to remediate potential outstanding data issues that occurred on Boards and Cards during the incident: - Missing card labels - Attachment restrictions not being enforced on moved cards - Checklist assignees that are not a member of the current board may incorrectly linger - Card assignees that are not a member of the current board may have incorrectly received due date reminders Please note that while cards are safe to edit, they may be excluded from certain restoration work if they are edited. We will provide another update when above issues are resolved. In the meantime, please reach out to our support team if you need further assistance.

16. investigating May 26, 2026, 01:27 PM UTC

    Users may be experiencing slowdowns across various functions of Trello including creating/deleting comments, editing cards, or creating new attachments. The team is actively working to fix the issue and will provide more updates within the hour.

17. monitoring May 26, 2026, 01:27 PM UTC

    Our team is still working to fix minor data inconsistencies on cards that were moved between boards during the incident. The following are still being addressed: -Missing card labels -Attachment restrictions are not being enforced on moved cards -Checklist assignee information on some cards. -Incorrect due date reminders sent to some card assignees Your cards are safe to edit. If you make changes to a card before our automated fix reaches it, your edits will be preserved, and the automated restore for that card will be skipped. No data will be lost in either scenario. We will provide another update once the above items are fully resolved. If you need assistance in the meantime, please reach out to our support team.

18. resolved May 26, 2026, 09:12 PM UTC

    Thank you for your patience as our team worked diligently to resolve outstanding issues. Although our team encountered edge scenarios through the weekend, we believe all 'card not found' issues are resolved. Minor data inconsistencies listed below may be present if cards were moved between boards during the incident: - Missing card labels - Attachment restrictions not being enforced on moved cards - Checklist assignee information on some cards - Incorrect due date reminders sent to some card assignees Please be assured that our team continues the work necessary to resolve above issues; however, given the impact and scope of remaining issues, we are now moving the channel of communication to Support rather than this Statuspage. If you believe that you continue to see lingering impacts from this incident, please do not hesitate to reach out to our Support team for further assistance.

19. postmortem Jun 26, 2026, 07:42 PM UTC

    # Summary On May 17th 2026 at 12:00 UTC a subset of Trello users experienced a degradation of some core functionality including but not limited to: issues with comments, viewing activity logs, accessing card details, board exports, Power-Ups, attachments, Home page updates, and search functionality. Some moved cards displayed 'Card Not Found' errors. These issues persisted for multiple days. Most of the issues encountered when interacting with Trello (commenting, viewing activity) were resolved by May 19 2026 at 08:31 UTC, however there was a lingering data integrity issue which manifested as “Card Not Found” errors when trying to open cards. >90% of these cards were repaired by May 28 at 17:20 UTC. The remainder took a little more time and were completely repaired by June 5th 2026 at 21:37 UTC. We wanted to share a more detailed analysis of the issues we encountered, as well as what we’re doing to ensure nothing similar happens in the future. # Root Cause The incident was caused by a bug in our database (MongoDB) which surfaced during a project to optimize the performance and scale of one of our largest collections. The affected collection contains card comments and other activity and is used across much of Trello’s functionality. The optimization project was to reshard the collection onto a new key. This allows us to eliminate a so-called “insert hot spot” which is where all newly created database entries end up on a single database partition (aka shard). After resharding, the load would be spread evenly across the various servers that make up the database cluster. This decreases latency and improves query performance for users. During the final stages of the resharding operation (which is a long-running, automated process), 12 of the 30 relevant shards ran out of disk space while building indexes. Rather than aborting the resharding process, the database bug caused the cluster to put the new database servers into rotation without their indexes, despite logs and metrics saying otherwise. Due to the enormous amount of data in this collection, having no indexes means that there is essentially no way to query for the data you want (i.e. “give me all comments for this card”) without performing an extremely slow and inefficient collection scan. # Remedial Actions Plan The first thing we did was initiate a full rebuild of all the database indexes for the collection. Unfortunately this takes a very long time to complete (multiple days) and is compute-intensive. We scaled all the database servers up in order to help the process move faster, however due to the single-threaded nature of this process, more compute did not equate to more speed. Additionally we enabled a database setting which caused all queries that would result in a full collection scan to fail-fast rather than drag on in the background and consume database resources before ultimately failing. This helped the parts of Trello that were still working stay responsive. Once the reindex process had completed, all functionality was restored. However, we discovered that cards which were moved to a different board during the rebuild were left in a broken state. Their activity logs and comments were essentially stranded on the old board while the card was now on the new board. This manifested as a “Card Not Found” error when trying to open such a card. The team moved into a new phase of writing code to safely remediate all of the remaining data issues in batches, with the final batch of fixes completing by June 5th 2026 at 21:37 UTC. # Next Steps We know that Trello is where your work lives and issues like this can cause a lot of disruption. To ensure we don’t run into this issue again in the future, the team is taking the following actions: - Working closely with our database vendor to ensure the original bug is fixed (update: the fix is shipping in the next version) - Working to create a standard set of tools and processes to ensure index rebuilds proceed as fast as possible in an emergency like this - Designing and implementing changes to make card move operations more atomic (either the whole operation succeeds, or the whole operation fails, rather than a partial failure)

Read the full incident report →

Started May 15, 2026, 03:14 PM UTC· resolved May 15, 2026, 06:04 PM UTC

1. investigating May 15, 2026, 03:14 PM UTC

   We are investigating degraded performance of some Trello features. We will provide more details within the next hour.

2. investigating May 15, 2026, 03:31 PM UTC

   Trello engineers are actively working on resolving issues that our users may be seeing around commenting on cards, deleting comments, and adding new attachments. Users may also find that recent changes to cards are not reflected in search results. We are continuing to work on it and will provide more updates within the hour.

3. identified May 15, 2026, 04:40 PM UTC

   The Trello team has identified and mitigated most of the issues with cards and comments. Users may still see delays in search indexing for short time while it catches up to realtime.

4. monitoring May 15, 2026, 05:36 PM UTC

   The team has resolved the previous issues and is now monitoring the system to ensure a full return to baseline. Search indexing is still approximately 1h delayed, but will be up to date shortly. Thank you for your patience

5. resolved May 15, 2026, 06:04 PM UTC

   Search is now fully up to date for all users, and all issues with previous degraded functionality have been resolved.

Read the full incident report →