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 05:24:58 UTC
| Metric | PublicNode | dRPC | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 3 | 7 | 8 |
| Score | 99.4 | 91.2 | 76.9 | 60.2 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.94% | 99.98% | 99.92% | 79.89% |
| p50 latency | 18.7 ms | 32.0 ms | 120.2 ms | 1317.0 ms |
| p95 latency | 29.8 ms | 62.2 ms | 212.6 ms | 7406.7 ms |
| p99 latency | 55.4 ms | 177.2 ms | 228.4 ms | 9776.0 ms |
| Correctness | 99.95% | 99.98% | 99.99% | 96.95% |
| Head lag | 0.49 blocks | 0.37 blocks | 0.39 blocks | 0.94 blocks |
| Rate limited | 0 | 9 | 0 | 1,469 |
| Unsupported | 0 | 0 | 0 | 0 |
| Samples | 8,843 | 8,634 | 8,779 | 2,029 |
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.4
- 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.
PublicNodevsMEV Blocker
+22.5points
- Latency+22.6
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +22.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+39.1points
- Latency+30.0
- Availability+8.0
- Correctness+0.6
- Head freshness+0.5
The parts add to +39.1, exactly — the score is a weighted sum, so it comes apart.