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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 23:01:13 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 6 |
| Score | 96.0 | 88.6 | 71.0 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 99.99% | 100.00% |
| p50 latency | 23.2 ms | 33.7 ms | 107.8 ms |
| p95 latency | 44.6 ms | 68.6 ms | 187.6 ms |
| p99 latency | 101.9 ms | 189.3 ms | 236.0 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.47 blocks | 0.36 blocks | 0.52 blocks |
| Rate limited | 0 | 13 | 1,289 |
| Unsupported | 0 | 0 | 12 |
| Samples | 8,208 | 8,000 | 1,937 |
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.3points
- Latency+7.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +7.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+25.0points
- Latency+24.9
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +25.0, exactly — the score is a weighted sum, so it comes apart.