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 15:04:09 UTC
| Metric | PublicNode | dRPC | Blast API | Merkle |
|---|---|---|---|---|
| Rank | 2 | 3 | 5 | 6 |
| Score | 95.3 | 88.8 | 78.4 | 70.9 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.99% | 99.95% | 99.99% | 100.00% |
| p50 latency | 25.0 ms | 34.3 ms | 108.5 ms | 109.8 ms |
| p95 latency | 49.6 ms | 71.4 ms | 126.6 ms | 191.2 ms |
| p99 latency | 112.7 ms | 178.5 ms | 152.9 ms | 277.4 ms |
| Correctness | 100.00% | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.41 blocks | 0.44 blocks |
| Rate limited | 0 | 29 | 45 | 1,297 |
| Unsupported | 0 | 0 | 0 | 12 |
| Samples | 8,289 | 8,075 | 8,208 | 1,908 |
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.5points
- Latency+6.6
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +6.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsBlast API
+16.9points
- Latency+16.9
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +16.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+24.3points
- Latency+24.4
- Head freshness−0.1
- Availability−0.0
- Correctness+0.0
The parts add to +24.3, exactly — the score is a weighted sum, so it comes apart.