Is Trello down?

Product match: components.

Read the provider’s incident report

1. 2026-06-26T15:42:29.002-04:00 · postmortem

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

2. 2026-05-26T17:12:25.744-04:00 · resolved

   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 as

3. 2026-05-26T09:27:46.060-04:00 · monitoring

   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 res

4. 2026-05-26T09:27:44.000-04:00 · investigating

   The team continues to remediate potential outstanding data issues that occurred on Boards and Cards during the incident

5. 2026-05-22T15:51:09.571-04:00 · monitoring

   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 receiv

6. 2026-05-21T17:29:27.830-04:00 · monitoring

   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.

7. 2026-05-20T15:06:05.429-04:00 · monitoring

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

8. 2026-05-19T14:01:36.626-04:00 · monitoring

   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.

9. 2026-05-19T10:26:04.334-04:00 · monitoring

   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.

10. 2026-05-19T03:03:41.043-04:00 · identified

    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. 2026-05-18T18:45:15.322-04:00 · identified

    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 wi

12. 2026-05-18T14:09:18.177-04:00 · identified

    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.

Product match: components.

Read the provider’s incident report

1. 2026-05-15T14:04:54.544-04:00 · resolved

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

2. 2026-05-15T13:36:54.623-04:00 · monitoring

   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

3. 2026-05-15T12:40:49.041-04:00 · identified

   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. 2026-05-15T11:31:35.485-04:00 · investigating

   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.

5. 2026-05-15T11:14:21.854-04:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2026-05-19T15:10:23.095-04:00 · postmortem

   ### Summary On May 14, 2026, between 04:30 and 05:26 UTC, Atlassian customers experienced widespread service disruption across multiple Atlassian Cloud products. The issue was caused by a race condition in our internal deployment orchestration platform during a routine rollback operation of a core identity service in the us-east region. This race condition resulted in insufficient capacity for the identity service in the affected region which started returning errors to dependent products. The

2. 2026-05-14T02:48:27.724-04:00 · resolved

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

3. 2026-05-14T02:41:35.000-04:00 · monitoring

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

4. 2026-05-14T02:40:47.405-04:00 · monitoring

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

5. 2026-05-14T01:43:24.277-04:00 · monitoring

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

6. 2026-05-14T01:34:14.217-04:00 · identified

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

7. 2026-05-14T01:24:55.084-04:00 · identified

   It is likely if you are experiencing any issues relating to logging in or accessing Atlassian products at this time it is likely due to this ongoing incident. We are continuing to receive reports about expanded product impact resulting from this incident. While our team continues to investigate the issue with urgency, we will continue to provide further updates here with additional information. We will provide further update within one hour, or sooner as further information becomes available.

Product match: components.

Read the provider’s incident report

1. 2026-05-20T02:46:35.733-04:00 · postmortem

   All dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in prod-east which led to Atlassian customers experiencing degraded performance and delays of background operations and automation execution. The incident started on May 8, 2026 at 00:22 and was detected within 4 minutes by automated monitoring systems. Our teams worked to restore core ac

2. 2026-05-08T06:26:50.796-04:00 · resolved

   This incident has been resolved.

3. 2026-05-08T06:25:39.325-04:00 · monitoring

   We are continuing to monitor for any further issues.

4. 2026-05-08T04:03:04.676-04:00 · monitoring

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

5. 2026-05-08T01:53:41.690-04:00 · monitoring

   The underlying issue in public infrastructure which affected asynchronous event processing has been mitigated and all the affected services are recovering. We are now working on clearing the backlog of queued events, which means some actions (such as notifications, automation triggers, and data syncs) may be in degraded state. We will continue to monitor and provide updates as the backlog is cleared.

6. 2026-05-08T00:10:45.846-04:00 · identified

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

7. 2026-05-08T00:10:38.771-04:00 · identified

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

8. 2026-05-08T00:10:31.649-04:00 · identified

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

9. 2026-05-07T23:00:17.138-04:00 · identified

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

10. 2026-05-07T23:00:10.981-04:00 · identified

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

11. 2026-05-07T22:15:41.015-04:00 · identified

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

12. 2026-05-07T21:31:38.443-04:00 · investigating

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

Product match: components.

Read the provider’s incident report

1. 2026-02-21T10:32:19.326-05:00 · resolved

   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

2. 2026-02-21T10:32:17.967-05:00 · investigating

   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

Product match: components.

Read the provider’s incident report

1. 2026-02-19T10:22:14.545-05:00 · resolved

   On February 19, 2026, Trello users may have experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

2. 2026-02-19T10:10:26.007-05:00 · monitoring

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

3. 2026-02-19T10:06:25.271-05:00 · investigating

   We are actively investigating reports of performance degradation affecting Trello. We will share updates here as more information is available.

Product match: components.

Read the provider’s incident report

1. 2026-02-18T03:33:43.333-05:00 · postmortem

   ### **Summary** On Feb 9, 2026, between 07:12 UTC and 08:05 UTC, Atlassian customers were unable to access Trello. The event was triggered by Trello servers reaching maximum memory limits and a subsequent failure to automatically scale for the traffic. The incident was detected within 5 minutes by automated monitoring systems, engaging Trello teams for resolution. Two parallel mitigation efforts were undertaken to restore access: 1\) manual scaling to address concerns with high utilization of h

2. 2026-02-09T03:36:36.805-05:00 · resolved

   Trello users experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.

3. 2026-02-09T03:20:54.237-05:00 · monitoring

   Trello performance was degraded and the performance degradation of Trello has been resolved. All the services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.

Product match: components.

Read the provider’s incident report

1. 2026-01-29T23:09:46.214-05:00 · postmortem

   ### Summary On **December 27, 2025**, between **02:48 UTC and 05:20 UTC**, some Atlassian cloud customers experienced failures in sending and receiving emails and mobile notifications. Core Jira and Confluence functionality remained available. The issue was triggered when **TLS certificates used by Atlassian’s monitoring infrastructure expired**, causing parts of our metrics pipeline to stop accepting traffic. Services responsible for email and mobile notifications had a critical path dependen

2. 2025-12-27T00:20:20.502-05:00 · resolved

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

3. 2025-12-26T23:42:32.178-05:00 · monitoring

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

Provider reports operational. Mapped components are operational in the latest status update; individual experiences can vary. This page was assembled at 2026-11-08T18:21:10.000Z.

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

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

The latest status observation was 2026-11-08T18:20:30.000Z. Only matched product components and incidents are shown. The assessment is recent.

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

Use “Watch this service” to save Trello in this browser’s watchlist, then return to compare its status with other saved services. Optional browser notifications can flag status changes while the watchlist page stays open and visible; background alerts are not sent. Use the problem-report button for an outage report; contact the provider through its official website for account, billing, or private support issues. Iszdown is independent and cannot resolve provider support tickets.