Phantom vs Safe
A tie, on what we measured. Both score 8.59/10. The difference between them is not something our probe can see, so we are not going to invent one.
Last collection 2026-08-25: probed 252 services, measured 233, over a 90-day window.
| Measured | Phantom | Safe |
|---|---|---|
| Status now | Not published | Not published |
| Score On what we could measure: 78% of the criteria weight for Phantom, 78% for Safe. | 8.59/10 | 8.59/10 |
| Age | 5.6 yr | 8.7 yr |
| Latency (our probe) | 170 ms | 39 ms |
| Median fix | — | — |
| Status feed | unknown | unknown |
Phantom
8.59 / 1078% measuredLive 5.6 yr (since founding (2021), public record). Most failures happen young, so time survived is real signal.
Median 170 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).
Safe
8.59 / 1078% measuredLive 8.7 yr (since founding (2018), public record). Most failures happen young, so time survived is real signal.
Median 39 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).
No affiliate links or ads anywhere on this site. How this is funded · Methodology · Full crypto wallets ranking