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 21:10:42 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 91.5 | 78.0 |
| Status | Excellent | Excellent | Good |
| Availability | 99.98% | 99.94% | 100.00% |
| p50 latency | 18.8 ms | 34.1 ms | 106.8 ms |
| p95 latency | 34.3 ms | 67.9 ms | 195.8 ms |
| p99 latency | 71.3 ms | 165.4 ms | 241.2 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.46 blocks |
| Rate limited | 0 | 112 | 6,073 |
| Unsupported | 0 | 0 | 78 |
| Samples | 37,847 | 36,965 | 8,780 |
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.9points
- Latency+8.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.4points
- Latency+21.4
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.4, exactly — the score is a weighted sum, so it comes apart.