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
1h window · 60 minutes observed · generated 2026-08-28 01:08:55 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 1 | 4 | 6 |
| Score | 99.4 | 86.1 | 77.5 |
| Status | Excellent | Good | Good |
| Availability | 99.94% | 100.00% | 100.00% |
| p50 latency | 17.9 ms | 87.4 ms | 106.4 ms |
| p95 latency | 29.1 ms | 98.1 ms | 201.7 ms |
| p99 latency | 55.0 ms | 109.8 ms | 316.7 ms |
| Correctness | 99.94% | 100.00% | 100.00% |
| Head lag | 0.50 blocks | 0.33 blocks | 0.60 blocks |
| Rate limited | 0 | 0 | 254 |
| Unsupported | 0 | 0 | 2 |
| Samples | 1,636 | 1,578 | 370 |
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.
PublicNodevsNodeReal
+13.2points
- Latency+13.5
- Head freshness−0.2
- Availability−0.0
- Correctness−0.0
The parts add to +13.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+21.8points
- Latency+21.7
- 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.