Which trading tools actually stay up
Best measured: Cryptohopper — 8.63/10 on the 80% we could measure.
Runner-up: TradingView — 8.63/10.
Last collection 2026-08-25: probed 252 services, measured 233, over a 90-day window. Collected by our own script, not by hand — the numbers are reproducible, and reproducibly boring.
The ranking
| # | Service | Score | Age | Latency | Median fix | Status feed |
|---|---|---|---|---|---|---|
| 1 | Cryptohopper | 8.6380% | 9.7y | 151 ms | — | unknown |
| 2 | TradingView | 8.6380% | 15.7y | 45 ms | — | unknown |
| 3 | 3Commas | 7.880% | 9.7y | 93 ms | — | none |
| 4 | Bitsgap | 7.880% | 9.7y | 99 ms | — | none |
| 5 | TradeSanta | 7.880% | 8.7y | 126 ms | — | none |
| 6 | Coinrule | 7.880% | 8.7y | 122 ms | — | none |
| 7 | DexScreener | 7.880% | 5.6y | 143 ms | — | none |
| 8 | DEXTools | 7.880% | 6.7y | 123 ms | — | none |
| 9 | Gunbot | 7.880% | 10.7y | 85 ms | — | none |
| 10 | WunderTrading | 7.4780% | 7.7y | 201 ms | — | none |
| 11 | Kryll | 7.4780% | 8.7y | 222 ms | — | none |
| 12 | Pionex | 6.7454% | 7.7y | 335 ms | — | none |
| 13 | GMGN | 6.3348% | — | 89 ms | — | none |
| 14 | Photon | 6.3348% | — | 163 ms | — | none |
| 15 | Maestro | 6.3348% | — | 52 ms | — | none |
Every figure carries the date it was taken, on the service’s card below, linked to its open source. Score is out of what we could measure — the % next to it is coverage.
How we scored this
These weights belong to this category alone. Signature measurement here: Age, latency and status transparency (our probe) — Tools hold no funds on chain — judged on longevity and service uptime.
Time the service has been live and continuously operating, from DefiLlama's listing date or the documented launch. Survi…
Median time to first byte from a public endpoint, our own probe, slowest sample discarded, single location. Scored withi…
Whether a public, machine-readable status page exists (statuspage / incident.io / instatus). A service you can audit fro…
Median minutes from published report to published resolution across the incidents a service logged, from its own status …
Latency in this category is timed at the live interface for every service, so the comparison is like-for-like. We never compare latency across categories — a DEX interface and an exchange API are not the same thing, and pretending otherwise would just reward whoever we happened to probe more cheaply.
The brief also defines FEES and UX (0%, 0%). We don’t publish them: we can’t measure them ourselves, and an estimate dressed as a measurement is worse than a gap. Full methodology
The services
Live 9.7 yr (since founding (2017), public record). Most failures happen young, so time survived is real signal.
Median 151 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
No incident feed we can read, so no repair time to compute.
Status transparency: A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
Live 15.7 yr (since founding (2011), public record). Most failures happen young, so time survived is real signal.
Median 45 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
No incident feed we can read, so no repair time to compute.
Status transparency: A status page exists but publishes no feed we could parse — readable, not auditable. Part of that may be our blind spot (we read three platforms).
3Commas
Live 9.7 yr (since founding (2017), public record). Most failures happen young, so time survived is real signal.
Median 93 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Bitsgap
Live 9.7 yr (since founding (2017), public record). Most failures happen young, so time survived is real signal.
Median 99 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 126 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Coinrule
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 122 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Live 5.6 yr (since founding (2021), public record). Most failures happen young, so time survived is real signal.
Median 143 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
DEXTools
Live 6.7 yr (since founding (2020), public record). Most failures happen young, so time survived is real signal.
Median 123 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Gunbot
Live 10.7 yr (since founding (2016), public record). Most failures happen young, so time survived is real signal.
Median 85 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Live 7.7 yr (since founding (2019), public record). Most failures happen young, so time survived is real signal.
Median 201 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Kryll
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 222 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Pionex
Live 7.7 yr (since founding (2019), public record). Most failures happen young, so time survived is real signal.
Measured 335 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
GMGN
No documented launch or listing date to measure age from.
Median 89 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Photon
No documented launch or listing date to measure age from.
Median 163 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Maestro
No documented launch or listing date to measure age from.
Median 52 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
No public status page found. Nothing about its reliability can be verified from outside — including by us.
No incident feed we can read, so no repair time to compute.
Status transparency: No public status page found. Nothing about its reliability can be verified from outside — including by us.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Who we left out, and why
We looked at 15, ranked 15.
Head to head
Questions
Why isn’t the biggest name at the top?+
Because we rank on whether a service works and can be checked, not on how big it is. Size is not a criterion here — a large service that publishes no status feed cannot demonstrate its reliability to anyone, and it scores accordingly.
What does "62% measured" mean under a score?+
It is the share of our criteria weight we actually measured for that service. The rest is n/a — we did not measure it, so its weight was redistributed across what we did measure rather than counted as zero. A high score at low coverage is a narrower claim than the same score at high coverage, and we would rather show you that than hide it.
Where do the incident numbers come from?+
From each provider's own status page, which several publish as a machine-readable feed. We compute repair time from their published report and resolution timestamps, and link the source on every figure so you can check it. It is their record — we just do the arithmetic and refuse to round it in their favour.
No affiliate links or paid placements in this section. How this is funded · Methodology