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
6h window · 6.0 hours observed · generated 2026-08-27 02:15:34 UTC
| Metric | PublicNode | dRPC | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 3 | 6 | 8 |
| Score | 98.7 | 90.3 | 77.8 | 58.7 |
| Status | Excellent | Excellent | Good | Degraded |
| Availability | 99.99% | 99.87% | 100.00% | 76.33% |
| p50 latency | 17.1 ms | 33.5 ms | 105.8 ms | 2024.4 ms |
| p95 latency | 35.4 ms | 70.3 ms | 193.2 ms | 6590.4 ms |
| p99 latency | 93.2 ms | 172.9 ms | 229.0 ms | 9196.2 ms |
| Correctness | 100.00% | 99.98% | 100.00% | 96.63% |
| Head lag | 0.49 blocks | 0.38 blocks | 0.45 blocks | 0.95 blocks |
| Rate limited | 0 | 32 | 1,338 | 1,434 |
| Unsupported | 0 | 0 | 19 | 0 |
| Samples | 8,596 | 8,384 | 1,897 | 2,003 |
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.4points
- Latency+8.5
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +8.4, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.0points
- Latency+21.0
- Head freshness−0.0
- Availability−0.0
- Correctness+0.0
The parts add to +21.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+40.0points
- Latency+29.3
- Availability+9.5
- Correctness+0.7
- Head freshness+0.5
The parts add to +40.0, exactly — the score is a weighted sum, so it comes apart.