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
24h window · 24 hours observed · generated 2026-08-27 04:44:30 UTC
| Metric | PublicNode | Tenderly | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 1 | 2 | 6 | 8 |
| Score | 99.4 | 99.2 | 77.9 | 58.5 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.98% | 99.98% | 100.00% | 75.73% |
| p50 latency | 18.2 ms | 19.6 ms | 107.1 ms | 2024.4 ms |
| p95 latency | 35.2 ms | 36.2 ms | 194.8 ms | 6590.4 ms |
| p99 latency | 73.8 ms | 172.6 ms | 247.0 ms | 9196.2 ms |
| Correctness | 100.00% | 99.99% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.47 blocks | 0.95 blocks |
| Rate limited | 0 | 0 | 6,135 | 6,592 |
| Unsupported | 0 | 0 | 81 | 0 |
| Samples | 38,763 | 38,445 | 8,805 | 7,909 |
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.
PublicNodevsTenderly
+0.2points
- Latency+0.2
- Head freshness+0.0
- Correctness+0.0
- Availability−0.0
The parts add to +0.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.5points
- Latency+21.5
- Head freshness−0.0
- Availability−0.0
- Correctness−0.0
The parts add to +21.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.9points
- Latency+30.0
- Availability+9.7
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.9, exactly — the score is a weighted sum, so it comes apart.