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
6h window · 6.0 hours observed · generated 2026-08-27 20:43:42 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 8 |
| Score | 83.0 | 70.7 | 46.9 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 23.14% |
| p50 latency | 87.2 ms | 110.1 ms | 17.6 ms |
| p95 latency | 99.1 ms | 192.2 ms | 101.9 ms |
| p99 latency | 123.3 ms | 236.0 ms | 277.2 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.61 blocks | no cohort |
| Rate limited | 0 | 1,486 | 0 |
| Unsupported | 0 | 18 | 274 |
| Samples | 9,123 | 2,204 | 9,269 |
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.3points
- Latency+12.0
- Head freshness+0.3
- Availability+0.0
- Correctness+0.0
The parts add to +12.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+36.2points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−0.9
The parts add to +36.2, 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.