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
1h window · 60 minutes observed · generated 2026-08-28 00:44:16 UTC
| Metric | dRPC | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 3 | 4 | 6 | 8 |
| Score | 91.5 | 86.0 | 77.7 | 60.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% | 79.94% |
| p50 latency | 31.7 ms | 87.4 ms | 102.7 ms | 1326.0 ms |
| p95 latency | 60.2 ms | 98.3 ms | 202.2 ms | 7406.7 ms |
| p99 latency | 143.0 ms | 109.2 ms | 316.7 ms | 9776.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 96.96% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.40 blocks | 0.94 blocks |
| Rate limited | 1 | 0 | 255 | 240 |
| Unsupported | 0 | 0 | 2 | 0 |
| Samples | 1,570 | 1,565 | 359 | 626 |
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 dRPC, the highest scorer of those selected.
dRPCvsNodeReal
+5.6points
- Latency+5.6
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +5.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.8points
- Latency+13.8
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +13.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvs1RPC
+31.3points
- Latency+22.0
- Availability+8.0
- Head freshness+0.7
- Correctness+0.6
The parts add to +31.3, exactly — the score is a weighted sum, so it comes apart.