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.0 days observed · generated 2026-08-26 21:02:03 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 93.6 | 78.4 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.93% | 99.97% |
| p50 latency | 18.5 ms | 34.1 ms | 106.7 ms |
| p95 latency | 33.4 ms | 72.8 ms | 196.0 ms |
| p99 latency | 69.3 ms | 168.2 ms | 243.2 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.46 blocks |
| Rate limited | 0 | 532 | 12,666 |
| Unsupported | 0 | 0 | 153 |
| Samples | 78,962 | 77,076 | 18,262 |
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+6.0
- 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
+21.0points
- Latency+21.0
- Head freshness−0.0
- Correctness−0.0
- Availability−0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.