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-28 21:12:30 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 89.4 | 86.1 | 77.4 |
| Status | Good | Good | Good |
| Availability | 99.98% | 99.91% | 100.00% |
| p50 latency | 33.7 ms | 87.4 ms | 107.3 ms |
| p95 latency | 76.6 ms | 100.3 ms | 200.9 ms |
| p99 latency | 188.6 ms | 136.0 ms | 263.5 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.35 blocks | 0.50 blocks |
| Rate limited | 96 | 0 | 6,053 |
| Unsupported | 0 | 0 | 73 |
| Samples | 36,986 | 36,958 | 8,735 |
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
+3.3points
- Latency+3.3
- Availability+0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +3.3, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+11.9points
- Latency+11.8
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +11.9, exactly — the score is a weighted sum, so it comes apart.