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
24h window · 24 hours observed · generated 2026-08-26 14:57:44 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 94.0 | 78.9 |
| Status | Excellent | Excellent | Good |
| Availability | 99.97% | 99.96% | 99.95% |
| p50 latency | 19.2 ms | 34.3 ms | 106.6 ms |
| p95 latency | 32.3 ms | 69.7 ms | 197.8 ms |
| p99 latency | 71.5 ms | 170.7 ms | 245.4 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.36 blocks | 0.47 blocks |
| Rate limited | 0 | 112 | 6,294 |
| Unsupported | 0 | 0 | 85 |
| Samples | 39,119 | 38,215 | 9,085 |
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.4points
- Latency+5.5
- Head freshness−0.2
- Availability+0.0
- Correctness−0.0
The parts add to +5.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.5points
- Latency+20.5
- Head freshness−0.0
- Availability+0.0
- Correctness−0.0
The parts add to +20.5, exactly — the score is a weighted sum, so it comes apart.