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
7d window · 2.9 days observed · generated 2026-08-27 17:52:07 UTC
| Metric | NodeReal | Merkle | Cloudflare |
|---|---|---|---|
| Rank | 4 | 6 | 9 |
| Score | 87.6 | 78.4 | 54.3 |
| Status | Good | Good | Degraded |
| Availability | 99.83% | 99.98% | 23.11% |
| p50 latency | 87.4 ms | 106.9 ms | 15.3 ms |
| p95 latency | 100.0 ms | 195.7 ms | 89.0 ms |
| p99 latency | 126.0 ms | 243.1 ms | 252.1 ms |
| Correctness | 99.99% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.48 blocks | no cohort |
| Rate limited | 0 | 18,018 | 96 |
| Unsupported | 0 | 220 | 3,297 |
| Samples | 110,241 | 25,988 | 111,953 |
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
+9.2points
- Latency+9.1
- Head freshness+0.2
- Availability−0.1
- Correctness−0.0
The parts add to +9.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.3points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.8
- Correctness−2.2
The parts add to +33.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.