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
- dRPC
- Tenderly
- NodeReal
- Blast API
- Merkle
- MEV Blocker
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-26 13:56:33 UTC
| Metric | PublicNode | Merkle | MEV Blocker | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 6 | 7 | 8 |
| Score | 99.4 | 78.5 | 77.6 | 64.7 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 99.97% | 99.95% | 99.85% | 90.50% |
| p50 latency | 19.1 ms | 106.4 ms | 118.7 ms | 259.6 ms |
| p95 latency | 32.3 ms | 197.1 ms | 210.0 ms | 2579.7 ms |
| p99 latency | 71.5 ms | 243.1 ms | 236.1 ms | 4625.5 ms |
| Correctness | 99.97% | 100.00% | 99.98% | 98.18% |
| Head lag | 0.49 blocks | 0.46 blocks | 0.39 blocks | 0.94 blocks |
| Rate limited | 0 | 6,264 | 0 | 6,667 |
| Unsupported | 0 | 84 | 0 | 0 |
| Samples | 39,099 | 9,041 | 38,719 | 7,965 |
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.
PublicNodevsMerkle
+20.9points
- Latency+20.9
- Head freshness−0.0
- Availability+0.0
- Correctness−0.0
The parts add to +20.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMEV Blocker
+21.8points
- Latency+21.8
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +21.8, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+34.7points
- Latency+30.0
- Availability+3.8
- Head freshness+0.5
- Correctness+0.4
The parts add to +34.7, exactly — the score is a weighted sum, so it comes apart.