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-27 00:28:10 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 98.9 | 90.6 | 77.9 |
| Status | Excellent | Excellent | Good |
| Availability | 100.00% | 99.86% | 100.00% |
| p50 latency | 17.6 ms | 34.7 ms | 107.7 ms |
| p95 latency | 37.8 ms | 72.9 ms | 196.0 ms |
| p99 latency | 91.9 ms | 179.7 ms | 230.7 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.49 blocks | 0.39 blocks | 0.49 blocks |
| Rate limited | 0 | 28 | 1,355 |
| Unsupported | 0 | 0 | 14 |
| Samples | 8,937 | 8,696 | 1,938 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsdRPC
+8.3points
- Latency+8.4
- Head freshness−0.1
- Availability+0.1
- Correctness+0.0
The parts add to +8.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.0points
- Latency+21.0
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.