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 01:19:27 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 91.2 | 86.6 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.91% | 100.00% | 100.00% |
| p50 latency | 34.1 ms | 87.3 ms | 107.1 ms |
| p95 latency | 69.2 ms | 100.0 ms | 195.2 ms |
| p99 latency | 170.7 ms | 124.6 ms | 239.8 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.38 blocks | 0.34 blocks | 0.47 blocks |
| Rate limited | 124 | 0 | 6,082 |
| Unsupported | 0 | 0 | 79 |
| Samples | 37,191 | 37,157 | 8,730 |
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.2points
- Latency+13.1
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.