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 13:43:31 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 88.3 | 82.8 | 70.2 |
| Status | Good | Good | Degraded |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 33.7 ms | 87.8 ms | 108.8 ms |
| p95 latency | 72.9 ms | 99.6 ms | 200.3 ms |
| p99 latency | 173.8 ms | 123.5 ms | 230.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.34 blocks | 0.49 blocks |
| Rate limited | 42 | 0 | 1,456 |
| Unsupported | 0 | 0 | 18 |
| Samples | 9,131 | 9,118 | 2,179 |
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.5points
- Latency+5.6
- Availability−0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +5.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+18.1points
- Latency+18.0
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +18.1, exactly — the score is a weighted sum, so it comes apart.