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 09:13:21 UTC
| Metric | dRPC | NodeReal | Merkle |
|---|---|---|---|
| Rank | 3 | 4 | 6 |
| Score | 91.3 | 86.5 | 78.0 |
| Status | Excellent | Good | Good |
| Availability | 99.97% | 99.90% | 100.00% |
| p50 latency | 33.1 ms | 87.4 ms | 107.6 ms |
| p95 latency | 68.6 ms | 100.1 ms | 193.4 ms |
| p99 latency | 189.6 ms | 136.5 ms | 259.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.37 blocks | 0.34 blocks | 0.52 blocks |
| Rate limited | 77 | 0 | 6,046 |
| Unsupported | 0 | 0 | 74 |
| Samples | 37,022 | 36,983 | 8,867 |
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.8points
- Latency+4.8
- Head freshness−0.0
- Availability+0.0
- Correctness−0.0
The parts add to +4.8, exactly — the score is a weighted sum, so it comes apart.
dRPCvsMerkle
+13.3points
- Latency+13.1
- Head freshness+0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.