Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Trello Outage History

Every past Trello outage tracked by IsDown, with detection times, duration, and resolution details.

There were 186 Trello outages since July 2017. The 17 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor May 15, 2026

May 2026: Trello - degraded performance (investigating)

Detected May 15, 2026 11:14 AM EDT · Resolved May 15, 2026 2:08 PM EDT · Duration about 3 hours

Trello experienced degraded performance affecting core features including commenting on cards, deleting comments, adding attachments, and search functionality, with recent card changes not appearing in search results. The incident impacted Trello.com, the API, and Atlassian Support services for 2.9 hours. The team identified and resolved the issues with cards and comments, then restored full search functionality after addressing indexing delays.

Major May 14, 2026

May 2026: Users experiencing issues accessing multiple Atlassian products

Detected May 14, 2026 1:24 AM EDT · Resolved May 14, 2026 2:48 AM EDT · Duration about 1 hour

Users experienced login and access issues across multiple Atlassian products including Trello, API services, and support systems during a major incident lasting 1.4 hours. The outage affected the ability to access Atlassian products and submit support requests. The team identified the root cause, implemented a mitigation, and fully restored all services.

Minor May 7, 2026

May 2026: Multiple Atlassian services are experiencing issues

Detected May 7, 2026 9:31 PM EDT · Resolved May 8, 2026 6:28 AM EDT · Duration about 9 hours

Multiple Atlassian services including Trello.com, API, and support systems experienced a 9-hour outage caused by an infrastructure issue with their public cloud provider. The incident affected asynchronous event processing, causing degraded notifications, automation triggers, and data syncs globally, with initial recovery beginning in regions outside Eastern USA. The underlying infrastructure issue was mitigated and services were restored after clearing the backlog of queued events.