Trello Outage History
14 incidents recorded over the last 365 days, 14 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Trello Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 17, 2026 | Trello - degraded performance# 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… | 223h 1m | Resolved |
| May 15, 2026 | Trello - degraded performance (resolved)Search is now fully up to date for all users, and all issues with previous degraded functionality have been resolved. | 2h 50m | Resolved |
| May 14, 2026 | Users experiencing issues accessing multiple Atlassian products### 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… | 1h 23m | Resolved |
| May 8, 2026 | Multiple Atlassian services are experiencing issuesAll 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… | 8h 55m | Resolved |
| Feb 21, 2026 | Trello Slow or down for usersImpact 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… | 0 min | Resolved |
| Feb 19, 2026 | Degraded performance of TrelloOn 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. | 15 min | Resolved |
| Feb 9, 2026 | Trello performance is degraded### **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… | 15 min | Resolved |
| Dec 27, 2025 | Outbound Email, Mobile Push Notifications, and Support Ticket Delivery Impacting All Cloud Products### 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… | 37 min | Resolved |
| Dec 12, 2025 | 500 Errors being experienced by Trello users### 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… | 1h 1m | Resolved |
| Nov 21, 2025 | Multiple Atlassian services experiencing degraded performance### 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… | 1h 54m | Resolved |
| Nov 14, 2025 | Trello automations delayedOn November 14, 2025 Trello users may have experienced delays on the execution of Trello automations. The issue has now been resolved, and the service is operating normally for all affected customers. Note: All… | 2h 47m | Resolved |
| Oct 20, 2025 | Atlassian Cloud Services impacted### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance… | 21h 28m | Resolved |
| Sep 11, 2025 | Degraded performance of TrelloOn Thursday, September 11, 2025 1:00PM UTC, Trello users may have experienced performance degradation. The issues has now been resolved, and the service is operating normally for all affected customers. | 22 min | Resolved |
| Aug 27, 2025 | Trello Connectivity ProblemsThis incident has been resolved. | 1h 32m | Resolved |
How to Read This Trello Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Trello acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Trello outage in this window ran 9d 7h, against a mean recovery of 19h 1m. If you depend on Trello in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.