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
- PublicNode
- Tenderly
- dRPC
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 03:27:36 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 1 | 3 | 6 |
| Score | 99.4 | 91.2 | 77.7 |
| Status | Excellent | Excellent | Good |
| Availability | 99.96% | 99.98% | 100.00% |
| p50 latency | 18.6 ms | 32.5 ms | 105.8 ms |
| p95 latency | 30.4 ms | 62.5 ms | 193.6 ms |
| p99 latency | 56.0 ms | 163.5 ms | 281.6 ms |
| Correctness | 99.97% | 99.98% | 100.00% |
| Head lag | 0.48 blocks | 0.38 blocks | 0.48 blocks |
| Rate limited | 0 | 7 | 1,442 |
| Unsupported | 0 | 0 | 20 |
| Samples | 8,936 | 8,700 | 2,089 |
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.2points
- Latency+8.3
- Head freshness−0.1
- Availability−0.0
- Correctness−0.0
The parts add to +8.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.7points
- Latency+21.7
- Availability−0.0
- Correctness−0.0
- Head freshness+0.0
The parts add to +21.7, exactly — the score is a weighted sum, so it comes apart.