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
6h window · 6.0 hours observed · generated 2026-08-28 05:35:31 UTC
| Metric | PublicNode | Tenderly | Merkle |
|---|---|---|---|
| Rank | 1 | 2 | 6 |
| Score | 99.4 | 99.2 | 77.5 |
| Status | Excellent | Excellent | Good |
| Availability | 99.95% | 100.00% | 100.00% |
| p50 latency | 18.8 ms | 17.9 ms | 104.3 ms |
| p95 latency | 29.8 ms | 30.7 ms | 196.3 ms |
| p99 latency | 55.4 ms | 51.9 ms | 274.4 ms |
| Correctness | 99.96% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.47 blocks | 0.55 blocks |
| Rate limited | 0 | 0 | 1,435 |
| Unsupported | 0 | 0 | 18 |
| Samples | 9,136 | 9,063 | 2,079 |
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.1points
- Latency+0.2
- Availability−0.0
- Head freshness−0.0
- Correctness−0.0
The parts add to +0.1, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+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.