Skip to content

Outage tracker / Trello

Is Trello down?

I'm having a problem

Partially downchecked moments ago

Our probes cannot reach Trello from 2 of the 10 regions we check; the other 8 answered.

As of Sep 13, 2026, 4:15 PM UTC, Trello answered RealUptime's probes in 8 of the 10 regions that returned a reading. Our Australia and South America probes could not reach it.

Functional endpoints verified

We have an outage open for Trello, 2h 27m so far.

Last outage: 4h on Sep 12, 2026 (web surface, from South America, intermittent).

our independent probeslive · checked Sep 13, 2026, 4:15 PM UTC
US-East126 msOperational
US-West274 msOperational
Europe261 msOperational
Asia-Pacific403 msOperational
US-Central295 msOperational
Canada417 msOperational
UK176 msOperational
Southeast Asia1232 msOperational
Australia537 msDown
South America178 msDown
their status pagetheir claim, not our reading

Trello reports: All systems operational (“All Systems Operational”)

from Trello's own status page, checked Sep 13, 2026, 4:02 PM UTC
Our probes are seeing errors from Trello right now. Trello's own status page currently reports All Systems Operational. We are not able to explain the difference. It's possible the issue is limited to the specific request path we check, or that their status page has not updated yet.

Trello's own component breakdown, as they publish it

  • Trello.comOperational
  • APIOperational
  • Atlassian Support - Support PortalOperational
  • Atlassian Support TicketingOperational
  • Atlassian Support Knowledge BaseOperational

These are Trello's components, named and scored by Trello. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Trello's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Trello response time, by region

US-East
284msp95 · latest
1s500ms0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 655ms2026-08-21 UTC: p95 428ms2026-08-22 UTC: p95 407ms2026-08-23 UTC: p95 492ms2026-08-24 UTC: p95 537ms2026-08-25 UTC: p95 648ms2026-08-26 UTC: p95 492ms2026-08-27 UTC: p95 428ms2026-08-28 UTC: p95 377ms2026-08-29 UTC: p95 531ms2026-08-30 UTC: p95 437ms2026-08-31 UTC: p95 569ms2026-09-01 UTC: p95 666ms2026-09-02 UTC: p95 453ms2026-09-03 UTC: p95 659ms2026-09-04 UTC: p95 827ms2026-09-05 UTC: p95 416ms2026-09-06 UTC: p95 390ms2026-09-07 UTC: p95 299ms2026-09-08 UTC: p95 355ms2026-09-09 UTC: p95 244ms2026-09-10 UTC: p95 295ms2026-09-11 UTC: p95 320ms2026-09-12 UTC: p95 305ms2026-09-13 UTC: p95 284ms
Aug 15Aug 29Sep 13
US-West
372msp95 · latest
2s1s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 545ms2026-08-21 UTC: p95 392ms2026-08-22 UTC: p95 260ms2026-08-23 UTC: p95 265ms2026-08-24 UTC: p95 342ms2026-08-25 UTC: p95 428ms2026-08-26 UTC: p95 504ms2026-08-27 UTC: p95 1.1s2026-08-28 UTC: p95 495ms2026-08-29 UTC: p95 668ms2026-08-30 UTC: p95 408ms2026-08-31 UTC: p95 355ms2026-09-01 UTC: p95 451ms2026-09-02 UTC: p95 578ms2026-09-03 UTC: p95 604ms2026-09-04 UTC: p95 709ms2026-09-05 UTC: p95 630ms2026-09-06 UTC: p95 587ms2026-09-07 UTC: p95 547ms2026-09-08 UTC: p95 563ms2026-09-09 UTC: p95 446ms2026-09-10 UTC: p95 326ms2026-09-11 UTC: p95 462ms2026-09-12 UTC: p95 491ms2026-09-13 UTC: p95 372ms
Aug 15Aug 29Sep 13
Europe
441msp95 · latest
1s500ms0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 669ms2026-08-21 UTC: p95 309ms2026-08-22 UTC: p95 349ms2026-08-23 UTC: p95 399ms2026-08-24 UTC: p95 534ms2026-08-25 UTC: p95 579ms2026-08-26 UTC: p95 472ms2026-08-27 UTC: p95 451ms2026-08-28 UTC: p95 605ms2026-08-29 UTC: p95 494ms2026-08-30 UTC: p95 491ms2026-08-31 UTC: p95 443ms2026-09-01 UTC: p95 383ms2026-09-02 UTC: p95 475ms2026-09-03 UTC: p95 437ms2026-09-04 UTC: p95 691ms2026-09-05 UTC: p95 467ms2026-09-06 UTC: p95 422ms2026-09-07 UTC: p95 480ms2026-09-08 UTC: p95 455ms2026-09-09 UTC: p95 540ms2026-09-10 UTC: p95 550ms2026-09-11 UTC: p95 426ms2026-09-12 UTC: p95 586ms2026-09-13 UTC: p95 441ms
Aug 15Aug 29Sep 13
Asia-Pacific
557msp95 · latest
2s1s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-08-20 UTC: p95 918ms2026-08-21 UTC: p95 692ms2026-08-22 UTC: p95 593ms2026-08-23 UTC: p95 865ms2026-08-24 UTC: p95 1.0s2026-08-25 UTC: p95 873ms2026-08-26 UTC: p95 897ms2026-08-27 UTC: p95 986ms2026-08-28 UTC: p95 995ms2026-08-29 UTC: p95 808ms2026-08-30 UTC: p95 950ms2026-08-31 UTC: p95 1.1s2026-09-01 UTC: p95 950ms2026-09-02 UTC: p95 924ms2026-09-03 UTC: p95 1.4s2026-09-04 UTC: p95 722ms2026-09-05 UTC: p95 714ms2026-09-06 UTC: p95 707ms2026-09-07 UTC: p95 654ms2026-09-08 UTC: p95 849ms2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 802ms2026-09-11 UTC: p95 757ms2026-09-12 UTC: p95 706ms2026-09-13 UTC: p95 557ms
Aug 15Aug 29Sep 13
US-Central
423msp95 · latest
1s500ms0ms
US-Central response time (p95) over the last 30 daysDaily 95th-percentile response time for US-Central, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 596ms2026-09-04 UTC: p95 617ms2026-09-05 UTC: p95 535ms2026-09-06 UTC: p95 593ms2026-09-07 UTC: p95 552ms2026-09-08 UTC: p95 496ms2026-09-09 UTC: p95 412ms2026-09-10 UTC: p95 436ms2026-09-11 UTC: p95 502ms2026-09-12 UTC: p95 518ms2026-09-13 UTC: p95 423ms
Aug 15Aug 29Sep 13
Canada
502msp95 · latest
1s500ms0ms
Canada response time (p95) over the last 30 daysDaily 95th-percentile response time for Canada, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 404ms2026-09-04 UTC: p95 518ms2026-09-05 UTC: p95 422ms2026-09-06 UTC: p95 425ms2026-09-07 UTC: p95 408ms2026-09-08 UTC: p95 392ms2026-09-09 UTC: p95 381ms2026-09-10 UTC: p95 542ms2026-09-11 UTC: p95 324ms2026-09-12 UTC: p95 536ms2026-09-13 UTC: p95 502ms
Aug 15Aug 29Sep 13
UK
226msp95 · latest
1s500ms0ms
UK response time (p95) over the last 30 daysDaily 95th-percentile response time for UK, scaled to a maximum of 1s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 394ms2026-09-04 UTC: p95 631ms2026-09-05 UTC: p95 373ms2026-09-06 UTC: p95 410ms2026-09-07 UTC: p95 204ms2026-09-08 UTC: p95 233ms2026-09-09 UTC: p95 242ms2026-09-10 UTC: p95 369ms2026-09-11 UTC: p95 294ms2026-09-12 UTC: p95 218ms2026-09-13 UTC: p95 226ms
Aug 15Aug 29Sep 13
Southeast Asia
1.1sp95 · latest
2s1s0ms
Southeast Asia response time (p95) over the last 30 daysDaily 95th-percentile response time for Southeast Asia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 1.1s2026-09-04 UTC: p95 1.2s2026-09-05 UTC: p95 1.3s2026-09-06 UTC: p95 1.2s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.3s2026-09-09 UTC: p95 1.1s2026-09-10 UTC: p95 1.3s2026-09-11 UTC: p95 1.2s2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.1s
Aug 15Aug 29Sep 13
Australia
1.8sp95 · latest
2s1s0ms
Australia response time (p95) over the last 30 daysDaily 95th-percentile response time for Australia, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 783ms2026-09-04 UTC: p95 643ms2026-09-05 UTC: p95 910ms2026-09-06 UTC: p95 1.1s2026-09-07 UTC: p95 1.2s2026-09-08 UTC: p95 1.1s2026-09-09 UTC: p95 1.2s2026-09-10 UTC: p95 1.0s2026-09-11 UTC: p95 674ms2026-09-12 UTC: p95 1.1s2026-09-13 UTC: p95 1.8s
Aug 15Aug 29Sep 13
South America
523msp95 · latest
2s1s0ms
South America response time (p95) over the last 30 daysDaily 95th-percentile response time for South America, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-09-03 UTC: p95 938ms2026-09-04 UTC: p95 1.1s2026-09-05 UTC: p95 1.2s2026-09-06 UTC: p95 939ms2026-09-07 UTC: p95 518ms2026-09-08 UTC: p95 668ms2026-09-09 UTC: p95 835ms2026-09-10 UTC: p95 761ms2026-09-11 UTC: p95 748ms2026-09-12 UTC: p95 632ms2026-09-13 UTC: p95 523ms
Aug 15Aug 29Sep 13

Is it Trello, or is it you?

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Trello -- it cannot diagnose Trello's own systems.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

Open incident

Sep 13, 2026, 1:49 PM UTCOngoing
multiple regions
open for 2h 27m so farAustralia: failing from Sep 13, 2026, 2:42 PM UTC, still failingSouth America: failing from Sep 13, 2026, 1:49 PM UTC, still failing

What we measured, and what people reported

Our Australia and South America probes cannot reach Trello, without a matching rise in user reports.

  • North America
    OperationalUS-East, US-West, US-Central, Canada
    • US-East
      Operationallatency: 126msstatus code: 400checked: Sep 13, 2026, 3:54 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Trello normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Operationallatency: 274msstatus code: 400checked: Sep 13, 2026, 3:46 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Trello normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Operationallatency: 295msstatus code: 400checked: Sep 13, 2026, 4:15 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Trello normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
    • Canada
      Operationallatency: 417msstatus code: 400checked: Sep 13, 2026, 3:19 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Trello normally. We do not have enough reports from Canada to say anything about what people there are seeing.
  • South America
    Downlatency: 178msstatus code: 405checked: Sep 13, 2026, 3:49 PM UTC
    0 people in the last 5 minutesNot enough reports to sayOur South America probes cannot reach Trello. We do not have enough reports from South America to say whether people there are seeing it too.
  • Europe
    OperationalEurope, UK
    • Europe
      Operationallatency: 261msstatus code: 400checked: Sep 13, 2026, 3:59 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Trello normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Operationallatency: 176msstatus code: 400checked: Sep 13, 2026, 3:50 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Trello normally. We do not have enough reports from UK to say anything about what people there are seeing.
  • Asia Pacific
    DownAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Operationallatency: 403msstatus code: 400checked: Sep 13, 2026, 3:44 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Trello normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Operationallatency: 1232msstatus code: 400checked: Sep 13, 2026, 4:05 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Trello normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
    • Australia
      Downlatency: 537msstatus code: 405checked: Sep 13, 2026, 3:42 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Australia probes cannot reach Trello. We do not have enough reports from Australia to say whether people there are seeing it too.

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Trello, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Trello yet, which is not evidence that nothing is wrong.

Recent outages

Partial outage, 4hmeasured by our probes · South America2026-09-12
Partial outage, 37mmeasured by our probes · Australia2026-09-10
Partial outage, 1hmeasured by our probes · South America2026-09-10
Partial outage, 54mmeasured by our probes · Southeast Asia2026-09-09
Partial outage, 1h 54mmeasured by our probes · South America2026-09-08
Partial outage, 54mmeasured by our probes · South America2026-09-08
Partial outage, 3h 56mmeasured by our probes · South America2026-09-06
Partial outage, 1h 44mmeasured by our probes · Australia2026-09-06

measured entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Trello since August 20, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Trello covering any window you pick, with our measurements and Trello's own claim at the time, side by side.

Full availability history for Trello: 90-day availability by region, month-by-month uptime, and every incident on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Tell me when this goes down

Get told when we measure this

We will tell you when our probes stop reaching Trello, and again when they can reach it again. That is our own measurement from ten regions, not Trello's status page. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when a measured outage opens, one when it closes, and a one-click unsubscribe in every one. We do not send anything else to this address.

Put this badge in your README

Trello uptime measured by RealUptimeLive, from this page's own readings.
[![Trello uptime measured by RealUptime](https://realuptime.io/outages/trello/badge.svg?days=30)](https://realuptime.io/outages/trello)
<a href="https://realuptime.io/outages/trello"><img src="https://realuptime.io/outages/trello/badge.svg?days=30" alt="Trello uptime measured by RealUptime"></a>

The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.

What Trello's SLA implies, from our measurement

Below your target

We measured 2h 26m of downtime for Trello over the 592h 15m since we started watching it on 2026-08-20, which is 99.5875% uptime by our reading. A 99.9% target allows 35 minutes over that period.

That is 1h 51m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.

Separately, we measured 24h 22m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.

This is computed from our own probe measurements, not from Trello's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.

What we check

primaryfunctional
https://api.trello.com/1/members/me
secondary
https://trello.status.atlassian.com/
RealUptime is not affiliated with Trello; the name identifies what we measured, and nothing here speaks for Trello's own team. We send a single web request to Trello from 10 regions on our own schedule and time the response. We do not see inside Trello's systems, do not use an account or real transaction, and are not the same signal Trello's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Trello is a real functional API call (marked “functional” above), not just a landing page, so a clean read there is a stronger signal than reachability alone, though it still does not cover every feature of the service. Read the full methodology.