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
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-27 17:02:11 UTC
| Metric | PublicNode | NodeReal | Merkle |
|---|---|---|---|
| Rank | 2 | 4 | 6 |
| Score | 95.0 | 82.9 | 70.9 |
| Status | Excellent | Good | Degraded |
| Availability | 100.00% | 100.00% | 100.00% |
| p50 latency | 25.5 ms | 87.6 ms | 109.8 ms |
| p95 latency | 50.1 ms | 99.6 ms | 191.2 ms |
| p99 latency | 113.6 ms | 130.8 ms | 235.5 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.48 blocks | 0.33 blocks | 0.52 blocks |
| Rate limited | 0 | 0 | 1,287 |
| Unsupported | 0 | 0 | 19 |
| Samples | 8,228 | 8,016 | 1,901 |
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
+12.2points
- Latency+12.3
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +12.2, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+24.1points
- Latency+24.1
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +24.1, exactly — the score is a weighted sum, so it comes apart.