Trello outage, November 2025: Multiple Atlassian services experiencing degraded performance

Trello reported and resolved an incident: Multiple Atlassian services experiencing degraded performance. It lasted 1.9 hours.

Resolved

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

What happened

Started
Resolved
Duration
1.9 hours
Impact
major
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 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. The event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into a known good state. This was followed by a global migration of edge proxy fleet hosts back to AMD64 CPU architecture the following day. ### **IMPACT** During the impact window, US East customers intermittently could not view or update data in Trello. The same underlying issue also impacted our Identity services and integrations with GitHub and Slack, meaning some customers had trouble signing in to Atlassian products or creating new integrations. At the incident’s peak, the incident impacted up to: * 52% of new Trello network connections. * 9% of new GitHub and Slack integrations. * 8% of new Identity network connections. ### **ROOT CAUSE** The issue was caused by a change to CPU architecture fr

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

    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

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

  3. monitoring

    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

    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

    ### 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. The event was triggered by a bug encountered in the software running our edge proxy fleet, which proxies customer traffic to Atlassian cloud services. The changes included the migration of our edge proxy fleet to hosts running an ARM CPU architecture, rather than the AMD64 CPU architecture they had previously been running, which impacted US East customers. The incident was detected within 1 minute by our automated monitoring systems, and mitigated by a scale up of of fleet size, which put Atlassian systems into a known good state. This was followed by a global migration of edge proxy fleet hosts back to AMD64 CPU architecture the following day. ### **IMPACT** During the impact window, US East customers intermittently could not view or update data in Trello. The same underlying issue also impacted our Identity services and integrations with GitHub and Slack, meaning some customers had trouble signing in to Atlassian products or creating new integrations. At the incident’s peak, the incident impacted up to: * 52% of new Trello network connections. * 9% of new GitHub and Slack integrations. * 8% of new Identity network connections. ### **ROOT CAUSE** The issue was caused by a change to CPU architecture fr

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

  • Retry anything that failed during the 1.9 hours.
  • 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