We started checking Trello on August 20, 2026, which is 65 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Trello's own status page declared. Below it, any public chatter we saw about Trello and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Trello's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Unverified user reportsNo reports about Trello in the last 24 hours, which is not evidence that nothing is wrong.
Trello's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Trello's own declaration, shown as they made it.
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Trello's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Trello - degraded performanceMinor incident
May 17, 2026, 2:11 PM UTC to May 26, 2026, 9:12 PM UTC (9d 7h)postmortem published
their latest update (Jun 26, 2026, 7:42 PM 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 …
Trello - degraded performance (resolved)Minor incident
May 15, 2026, 3:14 PM UTC to May 15, 2026, 6:04 PM UTC (2h 51m)resolved
their latest update (May 15, 2026, 6:04 PM UTC): Search is now fully up to date for all users, and all issues with previous degraded functionality have been resolved.
Users experiencing issues accessing multiple Atlassian productsMajor outage
May 14, 2026, 5:24 AM UTC to May 14, 2026, 6:48 AM UTC (1h 24m)postmortem published
their latest update (May 19, 2026, 7:10 PM 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 …
Multiple Atlassian services are experiencing issuesMinor incident
May 8, 2026, 1:31 AM UTC to May 8, 2026, 10:26 AM UTC (8h 55m)postmortem published
their latest update (May 20, 2026, 6:46 AM 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 pe…
Trello Slow or down for usersPartial outage
Feb 21, 2026, 3:32 PM UTC to Feb 21, 2026, 3:32 PM UTC (0 min)resolved
their latest update (Feb 21, 2026, 3:32 PM 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 se…
Degraded performance of TrelloMinor incident
Feb 19, 2026, 3:06 PM UTC to Feb 19, 2026, 3:22 PM UTC (16 min)resolved
their latest update (Feb 19, 2026, 3:22 PM 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.
Trello performance is degradedAll systems operational
Feb 9, 2026, 8:20 AM UTC to Feb 9, 2026, 8:36 AM UTC (16 min)postmortem published
their latest update (Feb 18, 2026, 8:33 AM 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 …
Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud ProductsMajor outage
Dec 27, 2025, 4:42 AM UTC to Dec 27, 2025, 5:20 AM UTC (38 min)postmortem published
their latest update (Jan 30, 2026, 4:09 AM 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…
500 Errors being experienced by Trello usersMajor outage
Dec 12, 2025, 6:40 AM UTC to Dec 12, 2025, 7:41 AM UTC (1h 2m)postmortem published
their latest update (Jan 6, 2026, 5:06 PM 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 miti…
Multiple Atlassian services experiencing degraded performancePartial outage
Nov 21, 2025, 2:55 PM UTC to Nov 21, 2025, 4:49 PM UTC (1h 54m)postmortem published
their latest update (Dec 8, 2025, 5:12 AM 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.
…
Showing the 10 most recent of 50 incidents Trello has declared in the history we hold.
These entries are Trello's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Trello's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.