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
30d window · 2.2 days observed · generated 2026-08-27 02:29:13 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 93.6 | 79.1 |
| 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 | 195.7 ms |
| p99 latency | 70.3 ms | 169.3 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 | 565 | 14,068 |
| Unsupported | 0 | 0 | 172 |
| Samples | 87,874 | 85,774 | 20,234 |
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.8points
- Latency+5.9
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.3points
- Latency+20.3
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +20.3, exactly — the score is a weighted sum, so it comes apart.