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
1h window · 60 minutes observed · generated 2026-08-27 20:23:55 UTC
| Metric | PublicNode | dRPC | NodeReal | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 4 | 6 |
| Score | 93.3 | 86.5 | 82.9 | 71.3 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.94% | 100.00% | 100.00% |
| p50 latency | 25.4 ms | 35.5 ms | 87.0 ms | 108.9 ms |
| p95 latency | 55.7 ms | 81.0 ms | 98.8 ms | 181.6 ms |
| p99 latency | 127.1 ms | 195.8 ms | 121.6 ms | 194.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.34 blocks | 0.34 blocks | 0.65 blocks |
| Rate limited | 0 | 7 | 0 | 278 |
| Unsupported | 0 | 0 | 0 | 2 |
| Samples | 1,639 | 1,586 | 1,579 | 400 |
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
+6.8points
- Latency+6.9
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +6.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsNodeReal
+10.4points
- Latency+10.6
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.9points
- Latency+21.8
- Head freshness+0.2
- Availability+0.0
- Correctness+0.0
The parts add to +21.9, exactly — the score is a weighted sum, so it comes apart.