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
30d window · 3.1 days observed · generated 2026-08-27 23:30:00 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 91.8 | 87.3 | 78.3 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 99.84% | 99.98% |
| p50 latency | 33.8 ms | 87.4 ms | 106.9 ms |
| p95 latency | 71.5 ms | 99.9 ms | 194.9 ms |
| p99 latency | 170.7 ms | 125.4 ms | 241.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.34 blocks | 0.49 blocks |
| Rate limited | 670 | 0 | 19,462 |
| Unsupported | 0 | 0 | 237 |
| Samples | 119,269 | 119,212 | 28,157 |
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.5points
- Latency+4.5
- Availability+0.0
- Head freshness−0.0
- Correctness+0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.5points
- Latency+13.4
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.