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
- Tenderly
- PublicNode
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 17:13:46 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 98.6 | 89.0 | 77.4 |
| Status | Excellent | Good | Good |
| Availability | 99.98% | 99.98% | 100.00% |
| p50 latency | 21.0 ms | 33.5 ms | 107.2 ms |
| p95 latency | 36.1 ms | 78.4 ms | 196.3 ms |
| p99 latency | 76.0 ms | 193.0 ms | 265.9 ms |
| Correctness | 99.98% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.52 blocks |
| Rate limited | 0 | 97 | 6,068 |
| Unsupported | 0 | 0 | 72 |
| Samples | 37,991 | 37,015 | 8,808 |
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
+9.6points
- Latency+9.7
- Head freshness−0.1
- Correctness−0.0
- Availability+0.0
The parts add to +9.6, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.2points
- Latency+21.2
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.2, exactly — the score is a weighted sum, so it comes apart.