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.7 days observed · generated 2026-08-27 13:39:50 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 92.3 | 78.5 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.93% | 99.98% |
| p50 latency | 18.7 ms | 33.8 ms | 106.6 ms |
| p95 latency | 34.3 ms | 71.9 ms | 196.3 ms |
| p99 latency | 73.2 ms | 168.2 ms | 243.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.48 blocks |
| Rate limited | 0 | 641 | 16,917 |
| Unsupported | 0 | 0 | 205 |
| Samples | 106,126 | 103,576 | 24,393 |
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
+7.1points
- Latency+7.2
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +7.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.