Skip to main content

Is Trello Down?

No — Trello is up

Reachable from all 8 checked regions

Average response time: 231ms

Last checked · checks run every 6 hours

Official status page: https://trello.status.atlassian.com

Trello uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
249ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 12 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

12-day clean streak
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: 100.00% uptime, 37 checks
Aug 13: 100.00% uptime, 45 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 36 checks
Aug 18: 100.00% uptime, 32 checks
Aug 19: 100.00% uptime, 32 checks
Aug 20: 100.00% uptime, 32 checks
Aug 21: 100.00% uptime, 32 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: no data
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
245ms
DNS 0ms TCP 1ms TLS 4ms TTFB 245ms
arn
224ms
DNS 0ms TCP 0ms TLS 2ms TTFB 224ms
bom
389ms
DNS 0ms TCP 1ms TLS 4ms TTFB 388ms
cdg
198ms
DNS 0ms TCP 1ms TLS 3ms TTFB 198ms
dfw
175ms
DNS 0ms TCP 1ms TLS 3ms TTFB 174ms
ewr
122ms
DNS 0ms TCP 1ms TLS 4ms TTFB 121ms
sjc
192ms
DNS 0ms TCP 1ms TLS 4ms TTFB 191ms
syd
339ms
DNS 0ms TCP 1ms TLS 4ms TTFB 339ms
yyz
156ms
DNS 0ms TCP 8ms TLS 11ms TTFB 155ms

What Trello does

Trello is Atlassian's kanban board tool, organising work into cards on lists that teams move across a board. It is often the lightest-weight system a team depends on, which makes an outage disproportionately disruptive: standups, handovers and queue triage stop even though nothing else is broken. Atlassian reports Trello.com and the Trello API as separate components.

What an outage looks like

Boards fail to load, or load with lists visible but cards missing. Card changes appear locally and then revert, because the write never reached the server. Drag-and-drop stops persisting between refreshes. Power-Ups and automations that call the Trello API break independently of the web app, so integrations can fail while boards themselves open normally.

What to do about it

Check trello.status.atlassian.com, which lists Trello.com and the API separately from Atlassian Support. Avoid re-entering cards that appeared to fail, since duplicates are common once writes drain. Trello shares the Atlassian status platform with other Atlassian products, and each has its own page and components, so read the Trello lines rather than a general Atlassian banner.

Is it down for everyone, or just you?

If this page says Trello is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

Trello outage FAQ

Is Trello down or is my board just not loading?
Check trello.status.atlassian.com first. Trello.com and the API are reported separately, so a green board line points at something local: a browser extension, a cached session, or a network filter. Opening the same board in a private window is the fastest way to separate a client problem from a platform one.
Will I lose card changes made during an outage?
Changes that appeared to save but reverted after a refresh did not reach the server, and are lost. Trello's web app updates the view optimistically, so a card can look moved for several seconds before snapping back. After an incident, refresh the board and compare it against what you expected before re-doing work, because some writes do land.
Does a Trello outage mean Jira and Confluence are down too?
Not necessarily. Trello runs on the Atlassian status platform alongside other Atlassian products, but each product has its own status page and components. Trello can fail while Jira is healthy. If your team depends on both, check each product's page rather than assuming one incident covers everything Atlassian operates.
Why did my Power-Up stop working when the board still opens?
Power-Ups and automations call the Trello API, which is reported as a separate component from Trello.com. An API incident breaks integrations while the web app continues to serve boards. Check the API line on the status page before debugging the Power-Up itself or reinstalling it, because the integration is probably intact.

How we measure this

  • We request Trello's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Trello publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Trello goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required