Trello change history

Trello.com, API and Atlassian support services experienced a critical login/access outage starting 2026-05-14 05:24 UTC, resolved at 2026-05-14 06:48 UTC (1 h 23 min). Atlassian attributed the disruption to a race condition in its internal deployment orchestration platform during a routine rollback of a core identity service in us-east; all impacted services recovered.

Trello reported a major incident involving intermittently dropping websocket connections, disrupting users’ active sessions. It started and was marked resolved at 2026-02-21 15:32 UTC, with a recorded duration of 0 min; the updates did not state a cause or completed fix.

Trello reported a critical incident affecting outbound email, mobile push notifications and support ticket delivery, starting 2025-12-27 04:42 UTC and resolved at 2025-12-27 05:20 UTC (computed duration: 37 min). The postmortem instead places onset at 02:48 UTC, citing expired monitoring TLS certificates that disrupted metrics traffic; core Jira and Confluence remained available.

Trello reported a critical disruption starting 2025-12-12 06:40 UTC and lasting 1 h 1 min, with 500 errors and service disruptions affecting web and mobile users. The postmortem attributed errors and slow loading to a dependency library upgrade causing high resource usage; rolling back the library restored service.

Trello reported a major degradation from 2025-11-21 14:55 UTC to 2025-11-21 16:49 UTC, lasting 1 h 54 min. Customers intermittently could not view or update boards and may have had authentication and new GitHub/Slack integration issues. The postmortem attributed the event to an edge proxy software bug; service was restored for all affected customers.

Trello.com experienced major-impact performance degradation, with the incident recorded from 2025-09-11 13:56 UTC to 2025-09-11 14:18 UTC (22 min). Trello confirmed normal service was restored for affected customers; its final update noted users may have experienced degradation as early as September 11, 2025 1:00PM UTC.

Trello.com experienced a major connectivity outage starting 2025-08-27 19:39 UTC; users could see a "You are disconnected from Trello" message. Recovery was reported at 21:01 UTC, and the incident was resolved at 2025-08-27 21:12 UTC, lasting 1 h 32 min. No cause or fix was stated.

Trello’s Email to Board failed for some users in a major-impact outage from 2025-07-15 03:43 UTC to 2025-07-15 05:45 UTC, lasting 2 h 2 min. Trello reverted a faulty internal configuration to restore functionality; users can resubmit failed emails to create cards.

Trello reported a major outage affecting all customers, with inaccessibility, errors or slow-loading cards and boards. The incident started at 2025-05-15 14:27 UTC and resolved at 2025-05-15 15:21 UTC (53 min). Trello attributed it to database plan cache expiry and high resource usage from subsequent query planning; a fix was implemented.

Trello reported a major degradation affecting API, Trello.com, and web/mobile apps; some users could not view boards or cards. It started at 2025-05-05 15:08 UTC and resolved at 2025-05-05 17:37 UTC (2 h 28 min). An infrastructure management tooling error deployed incorrect database DNS configuration; Trello mitigated the issue and reported no further impact.

Trello reported a critical outage affecting web and mobile apps, starting at 2025-04-25 18:39 UTC and resolved at 2025-04-25 19:12 UTC (computed duration: 32 min). Its postmortem separately identifies service interruptions between 18:18 and 18:33 UTC, caused by reduced capacity after a rollback deployment; scaling up mitigated the issue.

Trello’s Card Repeater Power-Up had a major outage: users couldn’t create new repeats, and existing repeats weren’t executing. It lasted 2 h 32 min, from 2024-12-11 15:27 UTC to 2024-12-11 17:59 UTC, affecting API and Trello.com. An initial fix failed; a subsequent fix restored existing repeats and creation of new ones.

Trello.com signup was blocked by reCaptcha errors in a vendor-rated critical outage from 2024-09-12 02:08 UTC to 2024-09-12 03:28 UTC, lasting 1 h 20 min. Trello reported identifying the root cause and confirmed resolution, but did not describe the cause or fix.

Some Trello.com customers experienced intermittent errors moving cards between boards or searching for cards. Trello rated the outage major; it started at 2024-07-25 19:31 UTC and was resolved at 2024-07-25 20:27 UTC, lasting 56 min. Trello confirmed normal operation but did not specify the cause or fix.

Trello.com experienced a major incident with intermittent content-access errors affecting some Atlassian Cloud customers, starting 2024-06-21 00:18 UTC and lasting 2 h 29 min, until resolution at 2024-06-21 02:47 UTC. The vendor said it identified the root cause, mitigated the problem, and restored normal service.

Trello reported a critical outage affecting API, Trello.com, and web and mobile apps, with slow or unavailable service starting 2024-02-13 09:30 UTC and resolving 2024-02-13 11:46 UTC (computed duration: 2 h 15 min). The postmortem cited long-running database queries slowing API responses; a fix was deployed and service restored.

Trello reported a critical outage affecting API and Trello.com, with errors across web, iOS and Android apps, starting 2023-11-30 14:21 UTC and lasting 3 h 16 min until resolution at 2023-11-30 17:37 UTC. The postmortem attributed it to a code change that overloaded a critical database component; Trello confirmed its database fix restored service.

Trello.com had a major degradation affecting some users: Automation commands failed to run or could not be created, card changes did not save, and some file uploads failed. It started at 2023-11-16 22:37 UTC and was resolved at 2023-11-16 23:58 UTC, lasting 1 h 20 min. Engineers rolled out a fix and observed recovery.

Trello reported a critical outage affecting API and Trello.com, preventing multiple users from connecting to its servers. It started at 2023-11-10 14:43 UTC and was resolved at 2023-11-10 16:19 UTC, lasting 1 h 35 min. Trello said its changes fixed the connection issues and all services were functional.