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 16:04:34 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 8 |
| Score | 82.9 | 78.4 | 47.1 |
| Status | Good | Good | Poor |
| Availability | 100.00% | 99.99% | 23.15% |
| p50 latency | 87.4 ms | 108.8 ms | 17.1 ms |
| p95 latency | 99.5 ms | 127.4 ms | 100.6 ms |
| p99 latency | 133.7 ms | 153.4 ms | 250.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.33 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 46 | 0 |
| Unsupported | 0 | 0 | 244 |
| Samples | 8,072 | 8,207 | 8,235 |
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.
NodeRealvsBlast API
+4.5points
- Latency+4.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +4.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+35.8points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−1.3
The parts add to +35.8, 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.