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
24h window · 24 hours observed · generated 2026-08-27 00:47:29 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 91.3 | 86.6 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.92% | 100.00% | 100.00% |
| p50 latency | 34.1 ms | 87.3 ms | 106.9 ms |
| p95 latency | 68.6 ms | 100.0 ms | 195.9 ms |
| p99 latency | 168.9 ms | 124.6 ms | 239.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.37 blocks | 0.35 blocks | 0.47 blocks |
| Rate limited | 128 | 0 | 6,208 |
| Unsupported | 0 | 0 | 80 |
| Samples | 37,924 | 37,904 | 8,933 |
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.7points
- Latency+4.8
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +4.7, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.3points
- Latency+13.2
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.