Which nft marketplaces actually stay up
Best measured: Magic Eden — 10/10 on the 100% we could measure.
Runner-up: MagicEden Runes — 10/10.
Not rankable: 1 of 15 — too little published about them to measure.
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 | Magic Eden | 10100% | 5.6y | 141 ms | — | statuspage |
| 2 | MagicEden Runes | 1042% | — | 452 ms | — | statuspage |
| 3 | OpenSea | 8.76100% | 9.7y | 342 ms | 334 min | statuspage |
| 4 | Zora | 8.7658% | 6.7y | 785 ms | — | blocked |
| 5 | Foundation | 7.880% | 5.6y | 88 ms | — | none |
| 6 | Nifty Gateway | 7.880% | 8.7y | 184 ms | — | none |
| 7 | SuperRare | 7.7280% | 8.7y | 641 ms | — | unknown |
| 8 | Blur | 7.3780% | 4.6y | 82 ms | — | none |
| 9 | LooksRare | 7.3780% | 4.6y | 187 ms | — | none |
| 10 | Tensor | 7.3780% | 4.6y | 46 ms | — | none |
| 11 | X2Y2 | 6.4780% | 4.6y | 539 ms | — | none |
| 12 | Rarible | 6.380% | 6.7y | 1426 ms | — | none |
| 13 | Manifold | 6.1746% | — | 131 ms | — | none |
| 14 | Element | 3.5746% | — | 1079 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 plus latency and status transparency (our probe) — No on-chain TVL to weigh — track record and operational reliability carry it.
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 5.6 yr (since founding (2021), public record). Most failures happen young, so time survived is real signal.
Median 141 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.
No incidents at all in the 90 days its feed covers — we read the feed and it is empty.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
No documented launch or listing date to measure age from.
Measured 452 ms, but at a different surface from the rest of this category — not comparable, so shown as context, not scored.
Publishes a machine-readable incident archive (statuspage) — its whole record can be checked by anyone, including against us.
No incidents at all in the 90 days its feed covers — we read the feed and it is empty.
Over the 90 days the feed covers. Not scored — logging granularity varies between services.
Timed at a different surface from the rest of this category, so not a fair comparison — not scored.
OpenSea
Live 9.7 yr (since founding (2017), public record). Most failures happen young, so time survived is real signal.
Median 342 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 334 min from published report to resolution across 1 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.
Incident repair time: Median 334 min from published report to resolution across 1 logged incidents. Scored on repair speed, not on how many it logged.
Zora
Live 6.7 yr (since founding (2020), public record). Most failures happen young, so time survived is real signal.
Median 785 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
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: Median 785 ms to first byte from the live interface, our own probe, slowest sample discarded, single location. Compared only within this category.
Live 5.6 yr (since founding (2021), public record). Most failures happen young, so time survived is real signal.
Median 88 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 184 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 641 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).
Blur
Live 4.6 yr (since founding (2022), public record). Most failures happen young, so time survived is real signal.
Median 82 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 4.6 yr (since founding (2022), public record). Most failures happen young, so time survived is real signal.
Median 187 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.
Tensor
Live 4.6 yr (since founding (2022), public record). Most failures happen young, so time survived is real signal.
Median 46 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.
X2Y2
Live 4.6 yr (since founding (2022), public record). Most failures happen young, so time survived is real signal.
Median 539 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.
Rarible
Live 6.7 yr (since founding (2020), public record). Most failures happen young, so time survived is real signal.
Median 1426 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.
Manifold
No documented launch or listing date to measure age from.
Median 131 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.
Element
No documented launch or listing date to measure age from.
Median 1079 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 14, and could not measure 1.
| Service | Status feed | Why it isn’t ranked |
|---|---|---|
| OKX NFT | none | 1 of 4 criteria measurable, 22% of this category’s weight — under the 25% a place in the ranking needs. Left unranked on purpose: the less we measure, the fewer criteria there are to dock points on, so a thinly-measured service drifts upward for no reason but our ignorance. |
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