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-27 00:47:11 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 91.0 | 86.4 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 33.7 ms | 87.3 ms | 105.0 ms |
| p95 latency | 66.5 ms | 98.2 ms | 199.7 ms |
| p99 latency | 164.1 ms | 123.9 ms | 219.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.75 blocks |
| Rate limited | 5 | 0 | 256 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,578 | 1,565 | 365 |
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
+4.6points
- Latency+4.7
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +4.6, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.6points
- Latency+13.2
- Head freshness+0.4
- Availability+0.0
- Correctness+0.0
The parts add to +13.6, exactly — the score is a weighted sum, so it comes apart.