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
- NodeReal
- dRPC
- Blast API
- Merkle
- MEV Blocker
- Cloudflare
- 1RPC
Side by side
6h window · 6.0 hours observed · generated 2026-08-28 11:55:31 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 3 | 6 | 8 |
| Score | 80.0 | 69.5 | 48.7 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 23.18% |
| p50 latency | 87.6 ms | 107.0 ms | 12.9 ms |
| p95 latency | 108.9 ms | 202.7 ms | 84.6 ms |
| p99 latency | 160.4 ms | 250.3 ms | 134.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.56 blocks | no cohort |
| Rate limited | 0 | 1,576 | 6 |
| Unsupported | 0 | 19 | 284 |
| Samples | 9,448 | 2,253 | 9,590 |
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 NodeReal, the highest scorer of those selected.
NodeRealvsMerkle
+10.4points
- Latency+10.2
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +10.4, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+31.3points
- Availability+29.7
- Head freshness*+9.6
- Latency−5.7
- Correctness−2.2
The parts add to +31.3, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.