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
1h window · 60 minutes observed · generated 2026-08-28 01:23:24 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.3 | 91.2 | 77.6 |
| Status | Excellent | Excellent | Good |
| Availability | 99.94% | 99.87% | 100.00% |
| p50 latency | 18.8 ms | 32.9 ms | 105.0 ms |
| p95 latency | 29.1 ms | 60.7 ms | 187.6 ms |
| p99 latency | 53.6 ms | 186.6 ms | 260.1 ms |
| Correctness | 99.94% | 99.87% | 100.00% |
| Head lag | 0.51 blocks | 0.39 blocks | 0.62 blocks |
| Rate limited | 0 | 2 | 250 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,616 | 1,566 | 369 |
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
+8.1points
- Latency+8.2
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.7points
- Latency+21.7
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.