Current Status: Possible Partial Outage. While the Official Atlassian Status Page currently shows Trello as “Operational” with no active incidents for December 12, 2025, third-party monitors like Downdetector are receiving reports from users experiencing issues today.
This suggests a partial outage or a lag in the official status update. You are likely not alone in this issue.
Immediate Troubleshooting Steps
Since the outage isn’t total, it might be fixable on your end if it’s a caching issue. Try these steps in order:
Check Downdetector: Visit Downdetector Trello Page to see if report spikes match your timeline.
Try “Incognito” or “Private” Mode: Open a new private window in your browser (Ctrl+Shift+N or Cmd+Shift+N) and try logging in. If it works, you need to clear your browser cache.
Switch Platforms: If you are on the Web, try the Mobile App (or vice versa). Often one works while the other is down.
Check for “504 Gateway Timeout”: If you see this error, it is definitely a server-side failure at Trello. Stop refreshing constantly; wait 15 minutes and try again.
Also Read : Tesco Flu Jab Booking | Book an Appointment
Check Trello status page for current incidents
The official Trello status page currently shows no active or newly posted incidents, and all core components are listed as operational as of the latest available update. However, third‑party aggregators that mirror this page also report Trello as “Up” with no ongoing outages, which matches what the official page exposes through its public feed.
Where to look
You can verify this directly on Trello’s own public status portal, which is where Atlassian publishes real‑time incident and maintenance information for Trello. That page also links to an incident history view, where any recent problems (like degraded performance or connectivity issues) would appear with timestamps and resolutions.
If Trello feels down
If Trello still isn’t working for you while the status page shows all systems operational, outage aggregators note that this can happen during partial or regional issues that are not yet reflected as a full incident. In that case, it helps to:
Check a crowd‑sourced outage site to see if other users are reporting problems.
Try another network, browser, or device to rule out a local connectivity or cache issue
Be the first to comment