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-28 15:51:25 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 7 |
| Score | 84.0 | 82.1 | 69.4 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.99% | 100.00% |
| p50 latency | 35.5 ms | 87.4 ms | 109.5 ms |
| p95 latency | 88.7 ms | 99.4 ms | 209.6 ms |
| p99 latency | 176.6 ms | 123.7 ms | 332.7 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.36 blocks | 0.35 blocks | 0.51 blocks |
| Rate limited | 36 | 0 | 1,513 |
| Unsupported | 0 | 0 | 15 |
| Samples | 9,323 | 9,328 | 2,161 |
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
+1.9points
- Latency+1.9
- Head freshness−0.0
- Correctness+0.0
- Availability−0.0
The parts add to +1.9, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+14.6points
- Latency+14.5
- Head freshness+0.2
- Availability−0.0
- Correctness+0.0
The parts add to +14.6, exactly — the score is a weighted sum, so it comes apart.