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 17:33:37 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 94.9 | 89.6 | 70.9 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.95% | 100.00% |
| p50 latency | 25.5 ms | 34.6 ms | 110.5 ms |
| p95 latency | 50.6 ms | 68.4 ms | 191.2 ms |
| p99 latency | 113.2 ms | 177.3 ms | 235.0 ms |
| Correctness | 100.00% | 99.99% | 100.00% |
| Head lag | 0.48 blocks | 0.36 blocks | 0.53 blocks |
| Rate limited | 0 | 23 | 1,413 |
| Unsupported | 0 | 0 | 19 |
| Samples | 9,080 | 8,856 | 2,090 |
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
+5.3points
- Latency+5.4
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +5.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+24.0points
- Latency+24.0
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +24.0, exactly — the score is a weighted sum, so it comes apart.