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-27 00:47:05 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 90.6 | 86.7 | 77.9 |
| Status | Excellent | Good | Good |
| Availability | 99.87% | 100.00% | 100.00% |
| p50 latency | 34.7 ms | 87.1 ms | 107.6 ms |
| p95 latency | 72.3 ms | 99.4 ms | 196.0 ms |
| p99 latency | 179.5 ms | 124.5 ms | 230.7 ms |
| Correctness | 99.98% | 100.00% | 100.00% |
| Head lag | 0.39 blocks | 0.34 blocks | 0.50 blocks |
| Rate limited | 31 | 0 | 1,445 |
| Unsupported | 0 | 0 | 16 |
| Samples | 9,205 | 9,201 | 2,077 |
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
+3.9points
- Latency+4.1
- Head freshness−0.1
- Availability−0.1
- Correctness−0.0
The parts add to +3.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+12.8points
- Latency+12.7
- Head freshness+0.1
- Availability−0.1
- Correctness−0.0
The parts add to +12.8, exactly — the score is a weighted sum, so it comes apart.