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-28 00:41:24 UTC
| Metric | PublicNode | NodeReal | Merkle | 1RPC |
|---|---|---|---|---|
| Rank | 2 | 4 | 6 | 8 |
| Score | 97.9 | 86.4 | 78.0 | 59.4 |
| Status | Excellent | Good | Good | Degraded |
| Availability | 100.00% | 99.97% | 100.00% | 77.78% |
| p50 latency | 20.8 ms | 87.1 ms | 106.6 ms | 1326.0 ms |
| p95 latency | 38.9 ms | 98.9 ms | 190.5 ms | 7406.7 ms |
| p99 latency | 91.8 ms | 116.5 ms | 278.7 ms | 9776.0 ms |
| Correctness | 100.00% | 99.97% | 100.00% | 96.96% |
| Head lag | 0.48 blocks | 0.35 blocks | 0.52 blocks | 0.94 blocks |
| Rate limited | 0 | 0 | 1,515 | 1,556 |
| Unsupported | 0 | 0 | 17 | 0 |
| Samples | 9,309 | 9,049 | 2,219 | 2,141 |
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
+11.5points
- Latency+11.7
- Head freshness−0.2
- Availability+0.0
- Correctness+0.0
The parts add to +11.5, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsMerkle
+19.9points
- Latency+19.9
- Head freshness+0.0
- Availability+0.0
- Correctness+0.0
The parts add to +19.9, exactly — the score is a weighted sum, so it comes apart.
PublicNodevs1RPC
+38.5points
- Latency+28.5
- Availability+8.9
- Correctness+0.6
- Head freshness+0.5
The parts add to +38.5, exactly — the score is a weighted sum, so it comes apart.