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
30d window · 2.8 days observed · generated 2026-08-27 16:06:19 UTC
| Metric | PublicNode | Tenderly | dRPC | Merkle |
|---|---|---|---|---|
| Rank | 1 | 2 | 3 | 6 |
| Score | 99.4 | 96.4 | 92.2 | 78.5 |
| Status | Excellent | Excellent | Excellent | Good |
| Availability | 99.98% | 99.96% | 99.93% | 99.98% |
| p50 latency | 19.0 ms | 19.8 ms | 33.8 ms | 106.7 ms |
| p95 latency | 34.9 ms | 51.8 ms | 71.8 ms | 196.0 ms |
| p99 latency | 74.4 ms | 759.0 ms | 169.5 ms | 243.3 ms |
| Correctness | 99.99% | 99.99% | 99.99% | 100.00% |
| Head lag | 0.49 blocks | 0.50 blocks | 0.36 blocks | 0.48 blocks |
| Rate limited | 0 | 0 | 645 | 17,567 |
| Unsupported | 0 | 0 | 0 | 215 |
| Samples | 110,118 | 109,276 | 107,462 | 25,321 |
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
+3.0points
- Latency+3.0
- Head freshness+0.0
- Availability+0.0
- Correctness−0.0
The parts add to +3.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsdRPC
+7.2points
- Latency+7.4
- Head freshness−0.1
- Availability+0.0
- Correctness−0.0
The parts add to +7.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+20.9points
- Latency+21.0
- 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.