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 · 3.6 days observed · generated 2026-08-28 11:40:59 UTC
| Metric | NodeReal | Cloudflare |
|---|---|---|
| Rank | 4 | 9 |
| Score | 86.8 | 53.8 |
| Status | Good | Degraded |
| Availability | 99.84% | 23.11% |
| p50 latency | 87.4 ms | 14.8 ms |
| p95 latency | 100.1 ms | 87.1 ms |
| p99 latency | 128.8 ms | 249.7 ms |
| Correctness | 99.99% | 100.00% |
| Head lag | 0.34 blocks | no cohort |
| Rate limited | 0 | 117 |
| Unsupported | 0 | 4,144 |
| Samples | 138,612 | 140,820 |
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.
NodeRealvsCloudflare
+33.1points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.9
- Correctness−2.2
The parts add to +33.1, 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.