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 23:30:12 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 88.7 | 82.3 | 70.8 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.97% | 100.00% |
| p50 latency | 33.5 ms | 87.1 ms | 107.7 ms |
| p95 latency | 67.8 ms | 99.0 ms | 190.5 ms |
| p99 latency | 189.6 ms | 117.8 ms | 236.0 ms |
| Correctness | 100.00% | 99.97% | 100.00% |
| Head lag | 0.36 blocks | 0.33 blocks | 0.52 blocks |
| Rate limited | 14 | 0 | 1,421 |
| Unsupported | 0 | 0 | 16 |
| Samples | 8,773 | 8,766 | 2,130 |
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
+6.5points
- Latency+6.5
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+17.9points
- Latency+17.7
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +17.9, exactly — the score is a weighted sum, so it comes apart.