Providers
Compare RPC providers on measured data
The top 4 on the chosen chain are compared by default. Pick your own — up to 4 — and the selection moves into the URL, so a comparison can be sent to someone else and they will see exactly what you saw.
Providers on Ethereum
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 10:18:46 UTC
| Metric | NodeReal | Merkle | 1RPC |
|---|---|---|---|
| Rank | 3 | 6 | 9 |
| Score | 78.8 | 69.7 | 0.0 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 0.00% |
| p50 latency | 87.4 ms | 106.0 ms | 0.0 ms |
| p95 latency | 116.1 ms | 200.6 ms | 0.0 ms |
| p99 latency | 162.2 ms | 250.3 ms | 0.0 ms |
| Correctness | 100.00% | 100.00% | not measured |
| Head lag | 0.34 blocks | 0.55 blocks | no cohort |
| Rate limited | 0 | 1,409 | 1,487 |
| Unsupported | 0 | 19 | 0 |
| Samples | 8,459 | 2,019 | 1,703 |
9 providers scored against each other.
Where the gap comes from
Two scores side by side say one is higher. This says why: the score is a weighted sum, so it comes apart, and each component’s share of the difference adds back to the difference exactly. Compared against NodeReal, the highest scorer of those selected.
NodeRealvsMerkle
+9.1points
- Latency+8.8
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +9.1, exactly — the score is a weighted sum, so it comes apart.
NodeRealvs1RPC
+78.8points
- Availability+40.0
- Correctness*+20.0
- Head freshness*+9.6
- Latency*+9.2
The parts add to +78.8, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.