Which instant exchangers actually stay up
Best measured: ChangeNOW — 9.8/10 on the 100% we could measure.
Runner-up: Changelly — 7.8/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 | ChangeNOW | 9.8100% | 9.7y | 92 ms | 58 min | statuspage |
| 2 | Changelly | 7.880% | 11.7y | 166 ms | — | none |
| 3 | StealthEX | 7.880% | 8.7y | 109 ms | — | none |
| 4 | FixedFloat | 7.880% | 8.7y | 171 ms | — | none |
| 5 | Exolix | 7.880% | 8.7y | 101 ms | — | none |
| 6 | SideShift | 7.7280% | 8.7y | 543 ms | — | unknown |
| 7 | Swapzone | 7.580% | 7.7y | 347 ms | — | none |
| 8 | LetsExchange | 7.580% | 6.7y | 301 ms | — | none |
| 9 | ChangeHero | 7.580% | 8.7y | 204 ms | — | none |
| 10 | SimpleSwap | 6.980% | 8.7y | 486 ms | — | none |
| 11 | Trocador | 6.6958% | 5.6y | — | — | blocked |
| 12 | Quickex | 6.1746% | — | 102 ms | — | none |
| 13 | Swapin | 6.1746% | — | 161 ms | — | none |
| 14 | Godex | 5.480% | 9.7y | — | — | none |
| 15 | Alligat0r | 4.6146% | — | 611 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) — No on-chain value to weigh, so this rests on track record and whether the service is reliable and transparent.
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 92 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
Median 58 min from published report to resolution across 49 logged incidents. Scored on repair speed, not on how many it logged.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
Live 11.7 yr (since founding (2015), public record). Most failures happen young, so time survived is real signal.
Median 166 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 109 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 171 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.
Exolix
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 101 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 543 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).
Swapzone
Live 7.7 yr (since founding (2019), public record). Most failures happen young, so time survived is real signal.
Median 347 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 6.7 yr (since founding (2020), public record). Most failures happen young, so time survived is real signal.
Median 301 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 204 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.
SimpleSwap
Live 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 486 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.
Trocador
Live 5.6 yr (since founding (2021), public record). Most failures happen young, so time survived is real signal.
Our probe could not reach it (our own probe failed: HTTP 503). Measured from one location, so it may be a block on us — but it is what we saw.
Their status host turned our probe away — the page exists and we could not read it, so n/a rather than a mark against them.
No incident feed we can read, so no repair time to compute.
Latency: Our probe could not reach it (our own probe failed: HTTP 503). Measured from one location, so it may be a block on us — but it is what we saw.
Quickex
No documented launch or listing date to measure age from.
Median 102 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.
Swapin
No documented launch or listing date to measure age from.
Median 161 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.
Godex
Live 9.7 yr (since founding (2017), public record). Most failures happen young, so time survived is real signal.
Our probe could not reach it (our own probe failed: 20). Measured from one location, so it may be a block on us — but it is what we saw.
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.
Latency: Our probe could not reach it (our own probe failed: 20). Measured from one location, so it may be a block on us — but it is what we saw.
Anyone who needs to know when it breaks: no status feed, so you find out it is down by discovering it yourself.
Alligat0r
No documented launch or listing date to measure age from.
Median 611 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