Trello outage, February 2026: Trello performance is degraded

Trello reported and resolved an incident: Trello performance is degraded. It lasted 16 minutes.

Resolved

From Trello's official status page, in their words.

What happened

Started
Resolved
Duration
16 minutes
Impact
none
Affected
Trello.com, API, Atlassian Support - Support Portal, Atlassian Support Ticketing, Atlassian Support Knowledge Base
  1. Investigating
  2. Identifiednot posted
  3. Monitoring
  4. Resolved

Why it happened

Trello has not given a cause in its updates. We never guess one.

How it was resolved

### **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 hosts, and 2\) temporarily limiting traffic from free customers. This intervention put Trello systems in a known good state with a total time to resolution of ~53 minutes. ### **IMPACT** The overall impact occurred on Feb 9, 2026 between 07:12 AM UTC and 08:05 AM UTC for Trello customers and caused service disruption for all customers, making Trello inaccessible during that time. Access was restored for paid users approximately 43 minutes after the onset, with full service restoration for free users 10 minutes later. ### **ROOT CAUSE** The issue was cause by increased memory requirements during the transition from the weekend to EU business hours, combined with Auto Scaling group scaling rules based on CPU utilization. Memory allocation on our instances outpaced the CPU usage, which caused processes to hit Out-Of-Memory \(OOM\) errors and crash before reaching CPU usage thresholds that would trigger the auto scaling policies. As a result, Trello went down and users received HTTP 502 erro

Trello's closing update

This incident on the Trello status page

Timeline

Oldest first, from the first notice to the resolution. From Trello's official status page, in their words.

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

  2. resolved

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

  3. 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 hosts, and 2\) temporarily limiting traffic from free customers. This intervention put Trello systems in a known good state with a total time to resolution of ~53 minutes. ### **IMPACT** The overall impact occurred on Feb 9, 2026 between 07:12 AM UTC and 08:05 AM UTC for Trello customers and caused service disruption for all customers, making Trello inaccessible during that time. Access was restored for paid users approximately 43 minutes after the onset, with full service restoration for free users 10 minutes later. ### **ROOT CAUSE** The issue was cause by increased memory requirements during the transition from the weekend to EU business hours, combined with Auto Scaling group scaling rules based on CPU utilization. Memory allocation on our instances outpaced the CPU usage, which caused processes to hit Out-Of-Memory \(OOM\) errors and crash before reaching CPU usage thresholds that would trigger the auto scaling policies. As a result, Trello went down and users received HTTP 502 erro

What this means for a business (and what to check now)

  • Retry anything that failed during the 16 minutes.
  • Enter any payments, bookings or jobs you took another way.
  • If a deadline fell inside the window, keep this page as your record of the outage.

The full guide: what to do when a service you rely on is down

Other Trello incidents

Hear about the next Trello incident as it starts

Free email alerts when the official status changes, with what to do while it is down.

Watch Trello