Trello

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2026-05-17 14:11 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 2026-05-17 15:13 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...

3. identified 2026-05-17 16:25 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 2026-05-17 21:03 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 2026-05-18 00:53 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...

6. identified 2026-05-18 03:51 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...

7. identified 2026-05-18 10:14 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...

8. identified 2026-05-18 18:09 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...

9. identified 2026-05-18 22:45 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...

10. identified 2026-05-19 07:03 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 2026-05-19 14:26 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...

12. monitoring 2026-05-19 18:01 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 2026-05-20 19:06 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...

14. monitoring 2026-05-21 21:29 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...

15. monitoring 2026-05-22 19:51 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...

16. investigating 2026-05-26 13:27 UTC

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

17. monitoring 2026-05-26 13:27 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...

18. resolved 2026-05-26 21:12 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...

19. postmortem 2026-06-26 19:42 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...

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. investigating 2026-05-15 15:14 UTC

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

2. investigating 2026-05-15 15:31 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...

3. identified 2026-05-15 16:40 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 2026-05-15 17:36 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 2026-05-15 18:04 UTC

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

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

Failure mode: Login, tokens, certificates or credentials failed. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

10. monitoring 2026-05-08 10:25 UTC

    We are continuing to monitor for any further issues.

11. resolved 2026-05-08 10:26 UTC

    This incident has been resolved.

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

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

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. investigating 2026-02-21 15:32 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...

2. resolved 2026-02-21 15:32 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...

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. investigating 2026-02-19 15:06 UTC

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

2. monitoring 2026-02-19 15:10 UTC

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

3. resolved 2026-02-19 15:22 UTC

   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.

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. monitoring 2026-02-09 08:20 UTC

   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.

2. resolved 2026-02-09 08:36 UTC

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

3. postmortem 2026-02-18 08:33 UTC

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

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

Affected: Atlassian Support Ticketing

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

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

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

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

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

3. postmortem 2026-01-30 04:09 UTC

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

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. investigating 2025-12-12 06:40 UTC

   We are actively investigating reports of a service disruption affecting Trello users. We'll share updates here as they become available or within the hour.

2. monitoring 2025-12-12 07:28 UTC

   Our engineering team has implemented a fix, and services have now recovered. We will continue to closely monitor the situation.

3. resolved 2025-12-12 07:41 UTC

   On December 12, 2025, from 05:51 UTC to 08:09 UTC, Trello users may have experienced service disruptions on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.

4. postmortem 2026-01-06 17:06 UTC

   ### Summary On December 12, 2025, between 05:31 UTC and 07:11 UTC, Trello customers experienced errors or slow loading times due to a dependency library upgrade that caused high resource usage. The incident was detected within 1 minute by the automated monitoring system and...

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

Failure mode: CDN or edge layer failed or served bad content. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: GitHub.

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

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

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

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

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

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

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

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

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

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

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

Affected: Trello.com

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

1. investigating 2025-11-14 17:43 UTC

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

2. identified 2025-11-14 19:02 UTC

   We have identified the cause of the issue, and our teams are diligently working on applying mitigations. We are seeing good signs of recovery, however, some users may experience some delays in Trello Automations executing. We’ll share additional updates at 19:45 UTC, or sooner,...

3. monitoring 2025-11-14 19:49 UTC

   We have applied mitigations and continue to see improvements in Trello Automation processing times. However, some users may still experience delays in automation execution. We will provide another update by 20:45 UTC, or sooner if more information becomes available.

4. resolved 2025-11-14 20:30 UTC

   On November 14, 2025 Trello users may have experienced delays on the execution of Trello automations. The issue has now been resolved, and the service is operating normally for all affected customers. Note: All automations identified as impacted by this incident will be...

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

Names an upstream provider: AWS.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

15. identified 2025-10-20 16:36 UTC

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

25. postmortem 2025-10-24 17:55 UTC

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

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

Affected: Trello.com

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

1. monitoring 2025-09-11 13:56 UTC

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

2. resolved 2025-09-11 14:18 UTC

   On Thursday, September 11, 2025 1:00PM UTC, Trello users may have experienced performance degradation. The issues has now been resolved, and the service is operating normally for all affected customers.

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

Affected: Trello.com

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-27 19:39 UTC

   We're receiving reports of connectivity problems while accessing Trello. You may see a "You are disconnected from Trello message" in the bottom left corner of your window notifying you that you've been disconnected. We're currently investigating the cause, and will post updates...

2. monitoring 2025-08-27 21:01 UTC

   We are now seeing recovery and monitoring.

3. resolved 2025-08-27 21:12 UTC

   This incident has been resolved.

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

Affected: Trello.com

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

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

   We are currently investigating this issue.

2. resolved 2025-07-30 08:13 UTC

   We have resolved this incident.

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. investigating 2025-07-15 03:43 UTC

   We are aware of some users experiencing issues where Email to Board functionality is failing with an error message similar to 'This message could not be delivered due to a recipient error. Please try again later.' Our team is investigating with urgency and will provide an update...

2. investigating 2025-07-15 05:17 UTC

   Our team is continuing to investigate the cause of errors relating to Email to Board actions in Trello. For those continuing to experience issues with Email to Board we encourage users to manually create their cards in Trello directly in the meantime. We apologise for any...

3. resolved 2025-07-15 05:45 UTC

   Our team has been able to identify a faulty configuration internally that was causing the errors relating to Email to Board functionality in Trello. The faulty configuration has now been reverted and Email to Board functionality should now be working as expected. For those that...

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

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

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

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

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

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

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

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

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

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

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

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

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

2. resolved 2025-06-05 00:59 UTC

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

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

Affected: Trello.com

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

1. investigating 2025-06-02 12:08 UTC

   We are currently experiencing an issue with Trello, as the search bar functionality is not working properly. Our team is diligently working to restore services as quickly as possible. We will keep you updated with further developments.

2. identified 2025-06-02 12:58 UTC

   We are currently experiencing an issue with Trello, as the search bar functionality is not working properly. We have identified the issue and are in the process of mitigating the impact. We'll keep you posted with further updates.

3. monitoring 2025-06-02 13:19 UTC

   The issues causing Trello’s search bar functionality to malfunction have been resolved, and services are now operating normally for all affected customers. We will monitor it closely to ensure stability.

4. resolved 2025-06-02 13:24 UTC

   On June 2nd, Trello's search bar functionality was not working correctly. The issue has now been resolved, and the service operates normally for all affected customers.

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

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

1. identified 2025-05-15 14:27 UTC

   We are aware that Trello was temporarily inaccessible for all customers. The system has already been recovered, and we are monitoring the situation.

2. resolved 2025-05-15 15:21 UTC

   A fix has been implemented, and the issue is now resolved.

3. postmortem 2025-05-27 19:04 UTC

   ### **SUMMARY** On May 15, 2025, between 13:55 and 14:18 UTC, Atlassian customers using the Trello product experienced errors or slow loading times when attempting to view their cards and boards. The event was triggered by a database plan cache expiring and high resource usage...

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

Affected: Trello.com

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

1. investigating 2025-05-05 15:08 UTC

   We've noticed that Trello is slow or unavailable for some users. This will be present in both the web and mobile apps. Our engineering team is actively investigating this incident and working to bring Trello back up to speed as quickly as possible. We'll keep you posted with...

2. monitoring 2025-05-05 16:56 UTC

   We have identified and mitigated the issue causing Trello to be slow or unavailable for some users. We expect API traffic to return to normal within the next 30 minutes. We are now monitoring closely. We will update within the next 30 minutes.

3. resolved 2025-05-05 17:37 UTC

   On May 5th, 2025 we identified a degradation for Trello. Trello is now back online and no further impact has been observed.

4. postmortem 2025-05-16 00:09 UTC

   ### **SUMMARY** On May 5, 2025, between 2:08 p.m. and 4:29 p.m. UTC, some Atlassian customers using Trello were unable to view their boards or cards. The event was triggered by an unexpected error encountered by our infrastructure management tools, which resulted in an incorrect...

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

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

1. monitoring 2025-04-25 18:39 UTC

   Trello was slow or unavailable. Our engineering team is actively investigating this incident to determine root cause. Users affected by this incident may have noticeed that Trello was slow or completely unavailable in both the web and mobile apps. Trello operations have...

2. resolved 2025-04-25 19:12 UTC

   Between 18:18 UTC to 18:33 UTC, we experienced an outage for Trello. The issue has been resolved and the service is operating normally. Our teams are investigating and will publish the root cause as soon as available.

3. postmortem 2025-05-16 18:16 UTC

   ### **SUMMARY** On April 25, 2025, between 18:18 and 18:33 UTC, Atlassian customers using Trello may have experienced service interruptions. The event was triggered by temporarily reduced capacity following a rollback deployment, with insufficient nodes to handle the load....

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

Affected: Trello.com

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

1. investigating 2025-03-11 09:23 UTC

   We're currently investigating an issue that's causing degraded performance in Trello for some customers and our team are working to get Trello back up and running as quickly as possible.

2. monitoring 2025-03-11 09:50 UTC

   Our team have implemented a fix and we're seeing performance improve, we'll continue to monitor this to make sure everything is working as normal.

3. investigating 2025-03-11 10:43 UTC

   We're continuing to investigate issues causing degraded performance in Trello for some Trello customers. We'll post more updates on this shortly.

4. investigating 2025-03-11 11:33 UTC

   We're still looking into issues with degraded performance in Trello and our team are working to get Trello back up and running as quickly as possible. We'll post more updates on this shortly.

5. monitoring 2025-03-11 12:59 UTC

   Trello is back up and running and we're not seeing any more performance issues but we'll continue to monitor this. If you're still experiencing any performance issues, please reach out to us through our support channels for further assistance

6. resolved 2025-03-11 13:30 UTC

   Following a period of monitoring, we've confirmed that the issue with degraded performance in Trello has been resolved. For any further issues please contact our Support team.

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

Affected: Trello.com

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

1. investigating 2025-03-10 11:15 UTC

   We're currently investigating an issue causing degraded performance for Trello's realtime updates for some customers. Our team are actively working to bring Trello back up to speed as quickly as possible.

2. resolved 2025-03-10 11:50 UTC

   We've identified this issue and released a fix so realtime updates are back up and running in Trello. We appreciate your patience and understanding while we worked on this.

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

Affected: Trello.com

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

1. investigating 2025-03-07 12:12 UTC

   We are investigating an issue related to connections being dropped. Some Trello users are experiencing slower updates and disconnection messages. Our engineering team is actively working to bring Trello back up to speed as quickly as possible.

2. investigating 2025-03-07 14:38 UTC

   We're continuing to investigate this issue with connections to Trello being dropped. Our engineering are working to bring Trello back up to speed as quickly as possible.

3. identified 2025-03-07 17:18 UTC

   We’ve already identified the issue and are working on a possible fix in our infrastructure for all connection problems some users have been experiencing. We’ll share a new update soon!

4. resolved 2025-03-07 18:23 UTC

   The changes we applied to our infrastructure have resulted in very good results on our side, and we’re no longer noticing issues that would result in constant disconnections or degraded services for Trello. We appreciate your understanding while we worked on this.

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

Affected: Trello.com

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

1. investigating 2025-03-05 15:48 UTC

   We are investigating cases of degraded performance for SOME Trello Cloud customers. We will provide more details within the next hour.

2. investigating 2025-03-05 16:55 UTC

   We are still investigating realtime update errors that is impacting most Trello Cloud customers. We will provide more details within the next hour.

3. investigating 2025-03-05 18:19 UTC

   We are continuing our investigation on realtime updates that is impacting all Trello Cloud customers. We will provide more details within the next hour.

4. monitoring 2025-03-05 19:25 UTC

   Between to , we experienced realtime update functionality degraded performance for Trello. We have mitigated the problem and are investigating the root cause. We are now monitoring closely.

5. resolved 2025-03-05 19:44 UTC

   Between to , we experienced realtime update functionality degraded performance for Trello. We have mitigated the problem and are investigating the root cause. The issue has been resolved and the service is operating normally.

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

Affected: Trello.com

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

1. identified 2025-02-13 15:54 UTC

   We've identified an issue that's causing users to be re-directed to the Home page when using the Trello Desktop app. We'll provide a new update soon.

2. identified 2025-02-13 17:54 UTC

   We're still working on a fix for the Trello Desktop. We'll provide a new update soon.

3. identified 2025-02-13 22:17 UTC

   We're still working on a fix for the Trello Desktop. We'll provide a new update soon.

4. monitoring 2025-02-14 01:29 UTC

   Our engineering team has successfully released a fix for both the MacOS and Windows Desktop Apps. To benefit from this fix, users are required to update to the latest version of the app. If you continue to experience any issues, particularly with redirection, please reach out to...

5. resolved 2025-02-14 04:02 UTC

   Following a period of monitoring, we have confirmed that the issue affecting the MacOS and Windows Desktop Apps is resolved. Please update to the latest version for the latest fix. For any further issues please contact our Support team. Thank you for your patience.

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

Affected: Trello.com, API

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

1. investigating 2024-12-11 15:27 UTC

   We’re currently investigating reports that users can’t create new repeats while using the Card Repeater and that existing repeats aren’t being executed.

2. identified 2024-12-11 15:45 UTC

   We've identified the issue that's causing issues with the repeats, and we're working now on a fix.

3. monitoring 2024-12-11 16:24 UTC

   A fix has been implemented and we're currently monitoring it.

4. identified 2024-12-11 16:35 UTC

   Our recent change hasn’t fixed the existing issue with the Card Repeater Power-Up. We’ll keep investigating the problem, and a new update will be provided soon.

5. resolved 2024-12-11 17:59 UTC

   A fix was released for the Card Repeater Power-up, and the repeats and new ones are working as intended.

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

Affected: Trello.com, API

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

1. investigating 2024-10-14 18:43 UTC

   We are investigating issues with some large boards that are experiencing poor performance when loading them and opening cards, and we will provide updates here soon.

2. investigating 2024-10-14 19:23 UTC

   We are continuing to investigate issues with some large boards that are experiencing poor performance when loading them and opening cards, and will provide updates as we learn more.

3. investigating 2024-10-14 21:12 UTC

   We are continuing to investigate issues with some large boards that are experiencing poor performance when loading them and opening cards, and will provide updates as we learn more.

4. investigating 2024-10-15 14:56 UTC

   We are continuing to investigate issues with some large boards that are experiencing poor performance when loading them and opening cards, and will provide updates as we learn more.

5. investigating 2024-10-15 16:58 UTC

   We’re continuing to investigating issues with boards that are experiencing slow performance when loading them and opening cards for Workspace Guests, and we will provide updates here soon

6. identified 2024-10-15 21:08 UTC

   We've identified the issue that caused the issue for slow performance for boards when loading them and opening cards for Workspace Guests, and we're now working on a fix for the problem and will provide a new update here soon.

7. monitoring 2024-10-15 21:48 UTC

   On October 15th, we identified that some boards were performing slowly for Workspace Guests. We have taken action to mitigate this issue and we will continue to monitor for the next 30 minutes before marking the incident as resolved.

8. resolved 2024-10-15 22:25 UTC

   On October 15th, we identified that some boards were performing slowly for Workspace Guests. A fix has been released to all affected users, and the slow performance issue is fixed. No further impact has been observed.

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

Affected: Trello.com, API

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

1. investigating 2024-09-25 19:22 UTC

   We are investigating issues with Email-to-Board feature not working for some customers and will provide updates here soon.

2. investigating 2024-09-25 19:51 UTC

   We are continuing to investigate issues with Email-to-Board feature not working for some customers and will provide updates as we learn more.

3. identified 2024-09-25 19:58 UTC

   We've identified the issue that caused the issues with the Email-to-Board feature not working correctly, and we're now working on a fix for the problem and will provide a new update here soon.

4. monitoring 2024-09-25 20:53 UTC

   On Sept 25 we identified that our email-to-board feature was failing for some users. We have taken action to mitigate this issue and we will continue to monitor for the next 30 minutes before marking the incident as resolved.

5. resolved 2024-09-25 21:32 UTC

   On September 25th, we identified a temporary outage with the Email-to-Board feature. The affected feature is now back online, and no further impact has been observed.

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

Affected: Trello.com

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

1. investigating 2024-09-12 02:08 UTC

   Users attempting to sign up are encountering reCaptcha errors that are preventing a successful signup.

2. monitoring 2024-09-12 02:40 UTC

   We have identified the root cause and the issue appears to be resolved.

3. resolved 2024-09-12 03:28 UTC

   This issue has been resolved.

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

Affected: Trello.com

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

1. investigating 2024-07-25 19:31 UTC

   We are investigating reports of intermittent errors for some Trello customers when moving cards between boards or searching for cards. We will provide more details once we identify the root cause.

2. investigating 2024-07-25 19:31 UTC

   We are investigating reports of intermittent errors for some Trello customers when moving cards between boards or searching for cards. We will provide more details once we identify the root cause

3. identified 2024-07-25 20:00 UTC

   We’ve identified the issue causing problems with moving and searching for cards on Trello. We’re currently working on implementing a fix, and a new update will be shared soon.

4. resolved 2024-07-25 20:27 UTC

   We previously identified the issue with moving cards and searching for cards in Trello. The issue has been resolved and Trello is operating normally.

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

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

1. investigating 2024-07-10 00:49 UTC

   We are investigating reports of intermittent errors whilst sending Email Notifications for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, and Jira Product Discovery Cloud customers. We will provide more details once we identify the root cause.

2. identified 2024-07-10 01:06 UTC

   We continue to work on resolving the Email Notifications for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, and Jira Product Discovery. We have identified the root cause.

3. resolved 2024-07-10 08:54 UTC

   Between 12:00am 9th July to 08:00am 10th July, we experienced email deliverability issues for some recipient domains for Confluence, Jira Work Management, Jira Service Management, Jira, Trello, Atlassian Bitbucket, and Jira Product Discovery. The issue has been resolved and...

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

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

1. investigating 2024-07-03 20:51 UTC

   We are investigating an issue with that is impacting Atlassian, Atlassian Partners, Atlassian Support, Confluence, Jira Work Management, Jira Service Management, Jira, Opsgenie, Atlassian Developer, Atlassian (deprecated), Trello, Atlassian Bitbucket, Guard, Jira Align, Jira...

2. monitoring 2024-07-03 21:45 UTC

   We have mitigated the problem and continue looking into the root cause. The outage was between 8:08pm 03/07 UTC - 08:31pm 03/07 UTC We are now monitoring closely.

3. resolved 2024-07-04 00:42 UTC

   Between 03-07-2024 20:08 UTC to 03-07-2024 20:31 UTC, we experienced downtime for Trello. The issue has been resolved and the service is operating normally.

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

Affected: Trello.com

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

1. identified 2024-06-27 07:57 UTC

   Users of the Jira powerup for Trello may be experiencing errors when installing and using the powerup on their boards. The team is working to resolve this issue as quickly as possible.

2. resolved 2024-06-27 08:35 UTC

   The issues with the Jira powerup have been resolved!

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

Affected: Trello.com

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

1. investigating 2024-06-21 00:18 UTC

   We are investigating an intermittent issue with accessing Atlassian Cloud services that is impacting some Atlassian Cloud customers. We will provide more details once we identify the root cause.

2. monitoring 2024-06-21 01:31 UTC

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

3. resolved 2024-06-21 02:47 UTC

   Between 2024-06-20 22:04 UTC to 2024-06-20 22:28 UTC, we experienced intermittent issue for users to access the services for some Atlassian Cloud customers. The issue has been resolved and the service is operating normally.

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

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

1. identified 2024-06-03 23:11 UTC

   We are investigating an issue with error responses for some Cloud customers across multiple products. We have identified the root cause and expect recovery shortly.

2. resolved 2024-06-04 00:31 UTC

   Between 22:18 UTC to 22:56 UTC, we experienced errors for multiple Cloud products. The issue has been resolved and the service is operating normally.

3. postmortem 2024-06-11 00:57 UTC

   ### Summary On June 3rd, between 09:43pm and 10:58 pm UTC, Atlassian customers using multiple product\(s\) were unable to access their services. The event was triggered by a change to the infrastructure API Gateway, which is responsible for routing the traffic to the correct...

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

Affected: Trello.com

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

1. investigating 2024-05-23 17:56 UTC

   Our engineering team identified an incident affecting the Card Repeater Power-Up service which caused an issue while repeating cards and we're currently investigating.

2. resolved 2024-05-23 23:06 UTC

   Our engineering team has resolved this issue, and the Card Repeater Power-Up is working again. Cards that missed their scheduled repeat will run at their next scheduled time.

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

Affected: Trello.com

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

1. investigating 2024-04-09 17:24 UTC

   We are currently investigating this issue.

2. identified 2024-04-09 18:16 UTC

   We have identified the root cause and are working towards releasing a fix.

3. resolved 2024-04-09 20:02 UTC

   A fix has been deployed. Thank you for your patience.

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

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

1. identified 2024-04-03 09:52 UTC

   We are investigating an issue causing failures in accessing some features from the Admin Portal, which is impacting some of our Cloud customers. We have identified the root cause and anticipate recovery shortly.

2. resolved 2024-04-03 10:23 UTC

   Between 6:30 AM UTC to 9:50 AM UTC, we experienced failures in accessing some features from the Admin Portal. The issue has been resolved and the service is operating normally.

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

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

1. resolved 2024-03-26 03:17 UTC

   We have identified and resolved a problem with Forge hosted storage, where some paginated queries kept repeating the last page. The incident was detected by our internal monitoring and was resolved quickly after detection by reverting the deployment. Activating changes recently...

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

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

1. investigating 2024-02-29 01:27 UTC

   We are investigating an issue with new product purchasing that is impacting for all products. Customers adding new cloud products may have experienced a long waiting page or an error page after attempting to add a product. We have mitigated the root cause and are working to...

2. resolved 2024-02-29 02:53 UTC

   Between 28th Feb 2024 23:15 UTC to 29th Feb 2024 00:05 UTC, we experienced issue with new product purchasing for all products. All new sign up products have been successfully provision and confirmed issue has been resolved and the service is operating normally.

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

Affected: Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base

Failure mode: Network, DNS, routing or connectivity failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2024-02-14 21:57 UTC

   We are investigating reports of intermittent errors for all Cloud Customers across all Atlassian products. We will provide more details once we identify the root cause.

2. identified 2024-02-14 22:31 UTC

   We have identified the root cause of the increased errors and have mitigated the problem. We continue to work on resolving the issue and monitoring this closely.

3. monitoring 2024-02-14 22:55 UTC

   We have identified the root cause of the Service Disruptions affecting all Atlassian products and have mitigated the problem. We are now monitoring this closely.

4. resolved 2024-02-14 23:32 UTC

   We experienced increased errors on Confluence, Jira Work Management, Jira Service Management, Jira Software, Opsgenie, Trello, Atlassian Bitbucket, Atlassian Access, Jira Align, Jira Product Discovery, Atlas, Compass, and Atlassian Analytics. The issue has been resolved and the...

5. postmortem 2024-02-27 05:45 UTC

   ### **Summary** On February 14, 2024, between 20:05 UTC and 23:03 UTC, Atlassian customers on the following cloud products encountered a service disruption: Access, Atlas, Atlassian Analytics, Bitbucket, Compass, Confluence, Ecosystem apps, Jira Service Management, Jira...

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

Affected: Trello.com, API

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

1. investigating 2024-02-13 08:57 UTC

   We've noticed that Trello is responding slowly. This will be present in both the web and mobile apps. Our engineering team is actively investigating this incident and working to bring Trello back up to speed as quickly as possible. We'll keep you posted with further updates on...

2. investigating 2024-02-13 09:30 UTC

   Our team is still investigating the issue that's causing Trello to be slow or unavailable, and working to bring Trello back up to speed as quickly as possible. Thanks for your patience and understanding!

3. investigating 2024-02-13 10:12 UTC

   We're still investigating the root cause of this problem, and a new update will be shared soon! Thanks for your patience!

4. investigating 2024-02-13 11:03 UTC

   Our team is still looking into the issue causing Trello to be slow or unavailable. Thank you for your understanding, we're working to have Trello back up and running as quickly as possible.

5. monitoring 2024-02-13 11:40 UTC

   We've identified an issue that was causing slowness in Trello and put a fix in place. We're seeing things improving for all our customers and we'll keep monitoring this latest fix for now. Once again, we appreciate your understanding!

6. resolved 2024-02-13 11:46 UTC

   Trello is now available. Thank you for your patience.

7. postmortem 2024-02-23 18:01 UTC

   ### Summary On Feb. 13, 2024, between 8:00 AM and 11:34 AM UTC, Trello experienced severely degraded performance appearing as a full or partial outage to Atlassian customers. The event was triggered by a buildup of long-running queries against our database, leading to slowed API...

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

Affected: Trello.com

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

1. investigating 2023-12-06 20:45 UTC

   Some users may see intermittent issues viewing and loading attachments. We are investigating the cause - for now, refreshing your browser may fix the issue. We will update this page with more information as it is discovered.

2. monitoring 2023-12-06 21:36 UTC

   A fix has been implement and we are monitoring the results.

3. resolved 2023-12-07 19:20 UTC

   This incident has been resolved.

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

Failure mode: Network, DNS, routing or connectivity failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. identified 2023-12-04 16:33 UTC

   We are currently investigating an incident that result in connection time outs on service egress proxy. This affects Jira, JSM, Confluence, BitBucket, Trello, Ecosystem products. The features affected for these products are those that require a connection to service egress.

2. identified 2023-12-04 16:43 UTC

   Including Atlassian Developer

3. identified 2023-12-04 16:54 UTC

   We are currently investigating an incident that result in outbound connections from Atlassian cloud in us-east-1 intermittently timing out. This affects Jira, Trello, Confluence, Ecosystem products. The features affected for these products are those that require opening a...

4. monitoring 2023-12-04 16:59 UTC

   The issue was identified and a fix implemented. We are monitoring currently.

5. resolved 2023-12-04 17:15 UTC

   The systems are stable after the fix and monitoring for a specified duration

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

Affected: Trello.com, API

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

1. investigating 2023-11-30 14:21 UTC

   We're currently investigating an issue that's causing Trello to be slow or unavailable to our users. A new update will be shared soon.

2. investigating 2023-11-30 14:52 UTC

   We're still investigating the root cause of this problem, and a new update will be shared soon! Thanks for your patience!

3. investigating 2023-11-30 15:22 UTC

   Our team is still investigating the issue that's affecting Trello's availability, and we'll provide a new update soon. Thanks for your patience and understanding!

4. investigating 2023-11-30 15:56 UTC

   Our teams are still investigating the issue affecting Trello's availability, and a new update will be provided soon. We appreciate your understanding!

5. identified 2023-11-30 16:35 UTC

   Our engineering team has identified an issue with Trello's database, and we're now working on implementing a fix to restore Trello's availability to all users. We appreciate everyone's understanding!

6. monitoring 2023-11-30 17:14 UTC

   We've implemented a new fix to the issue affecting our database, and we're now seeing signs of recovery for all users on Trello. We'll keep monitoring this latest fix for now. Once again, we appreciate your understanding!

7. resolved 2023-11-30 17:37 UTC

   The fix we released was successful, and all the issues our users were experiencing with Trello have been resolved. Thank you for your patience and understanding!

8. postmortem 2023-12-08 16:03 UTC

   ### **SUMMARY** On Nov 30 2023, between 14:04 and 16:57 UTC, Atlassian customers using Trello experienced errors when accessing and interacting with the application. This incident impacted Trello users on the iOS and Android mobile apps as well as those using the Trello web app....

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

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

1. resolved 2023-11-29 03:00 UTC

   Forge Invocations had an 8 minute outage between 2023-11-29 03:05:13 UTC to 2023-11-29 03:13:27 UTC resulting in Smart Links failing. This service has recovered post this time period.

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

Affected: Trello.com

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

1. investigating 2023-11-16 22:37 UTC

   We are currently investigating an issue affecting some of Trello's services. We have identified that some users may experience trouble with the following service: - Automations commands not running - Card changes not saving

2. identified 2023-11-16 22:52 UTC

   Our Engineers have identified the issue and are working on a fix. We have found the following services to be affected: - Inability to create new Automation commands - Card changes not saving - Some file uploads failing

3. monitoring 2023-11-16 23:32 UTC

   Our Engineers have rolled out a fix and have seen services recovering. We're now monitoring it.

4. resolved 2023-11-16 23:58 UTC

   This incident has been resolved. If you're still seeing issues, please reach out at https://trello.com/contact/

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

Affected: Trello.com, API

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

1. identified 2023-11-10 14:43 UTC

   We've identified an issue on Trello that's affecting multiple users to connect to our servers. We'll provide a new update soon.

2. identified 2023-11-10 14:45 UTC

   We are continuing to work on a fix for this issue.

3. identified 2023-11-10 15:05 UTC

   We've identified the root cause of the issue, and we made some adjustments, which should bring Trello's functionalities back soon.

4. monitoring 2023-11-10 15:47 UTC

   The changes we released have fixed the connection issues our users were experiencing when connecting to Trello. We're now monitoring it.

5. resolved 2023-11-10 16:19 UTC

   We want to let you know that the changes we made on our side fixed all the connection issues our users were experiencing with Trello, and all services are functional right now. We appreciate your patience and understanding.

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