What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with Trello now? Check the current statusAffected services
Updates (3)
- Feb 18, 2026, 08:33 AMTrello 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 automatically scale for the traffic. The incident was detected within 5 minutes by automated monitoring systems, engaging Trello teams for resolution. Two parallel mitigation efforts were undertaken to restore access: 1\) manual scaling to address concerns with high utilization of hosts, and 2\) temporarily limiting traffic from free customers. This intervention put Trello systems
Trello ↗ - Feb 9, 2026, 08:36 AMTrello performance is degraded
Trello users experienced performance degradation. The issue has now been resolved, and the service is operating normally for all affected customers.
Trello ↗ - Feb 9, 2026, 08:20 AMTrello performance is degraded
Trello performance was degraded and the performance degradation of Trello has been resolved. All the services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
Trello ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow Trello's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.