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
Side by side
1h window · 60 minutes observed · generated 2026-08-27 20:43:56 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 82.7 | 70.8 | 46.8 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 22.90% |
| p50 latency | 87.1 ms | 107.4 ms | 17.7 ms |
| p95 latency | 98.5 ms | 190.5 ms | 99.7 ms |
| p99 latency | 119.9 ms | 195.8 ms | 264.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.68 blocks | no cohort |
| Rate limited | 0 | 269 | 0 |
| Unsupported | 0 | 2 | 47 |
| Samples | 1,590 | 407 | 1,615 |
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
+12.0points
- Latency+11.6
- Head freshness+0.4
- Availability+0.0
- Correctness+0.0
The parts add to +12.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+36.0points
- Availability+29.8
- Head freshness*+9.6
- Correctness−2.2
- Latency−1.2
The parts add to +36.0, 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.