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
- MEV Blocker
- Merkle
- Cloudflare
- 1RPC
Side by side
1h window · 60 minutes observed · generated 2026-08-28 14:44:41 UTC
| Metric | PublicNode | dRPC | Merkle |
|---|---|---|---|
| Rank | 2 | 3 | 7 |
| Score | 98.2 | 85.6 | 69.4 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 22.8 ms | 37.3 ms | 109.2 ms |
| p95 latency | 37.9 ms | 82.5 ms | 226.0 ms |
| p99 latency | 83.8 ms | 174.7 ms | 332.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.56 blocks | 0.37 blocks | 0.53 blocks |
| Rate limited | 0 | 7 | 258 |
| Unsupported | 0 | 0 | 3 |
| Samples | 1,619 | 1,578 | 383 |
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
+12.5points
- Latency+12.8
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+28.8points
- Latency+28.9
- Head freshness−0.0
- Availability+0.0
- Correctness+0.0
The parts add to +28.8, exactly — the score is a weighted sum, so it comes apart.