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
7d window · 2.3 days observed · generated 2026-08-27 03:22:00 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 93.5 | 79.0 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.93% | 99.98% |
| p50 latency | 18.3 ms | 34.0 ms | 106.6 ms |
| p95 latency | 33.7 ms | 72.6 ms | 196.0 ms |
| p99 latency | 70.5 ms | 169.2 ms | 243.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.46 blocks |
| Rate limited | 0 | 569 | 14,273 |
| Unsupported | 0 | 0 | 177 |
| Samples | 89,304 | 87,173 | 20,532 |
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.9points
- Latency+6.1
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +5.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.4points
- Latency+20.4
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.4, exactly — the score is a weighted sum, so it comes apart.