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
- 1RPC
- Cloudflare
Side by side
24h window · 24 hours observed · generated 2026-08-28 18:45:19 UTC
| Metric | PublicNode | Merkle | 1RPC |
|---|---|---|---|
| Rank | 2 | 6 | 8 |
| Score | 98.7 | 77.4 | 58.7 |
| Status | Excellent | Good | Degraded |
| Availability | 99.98% | 100.00% | 75.93% |
| p50 latency | 20.8 ms | 107.0 ms | 1326.0 ms |
| p95 latency | 35.6 ms | 196.1 ms | 7406.7 ms |
| p99 latency | 75.2 ms | 263.5 ms | 9776.0 ms |
| Correctness | 99.98% | 100.00% | 96.96% |
| Head lag | 0.49 blocks | 0.52 blocks | 0.94 blocks |
| Rate limited | 0 | 6,235 | 6,598 |
| Unsupported | 0 | 73 | 0 |
| Samples | 38,845 | 8,994 | 7,920 |
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
+21.3points
- Latency+21.3
- Head freshness+0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.3, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.1points
- Latency+29.3
- Availability+9.6
- Correctness+0.6
- Head freshness+0.5
The parts add to +40.1, exactly — the score is a weighted sum, so it comes apart.