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-28 01:05:58 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 86.3 | 83.8 | 54.8 |
| Status | Good | Good | Degraded |
| Availability | 99.96% | 99.99% | 23.01% |
| p50 latency | 87.1 ms | 104.8 ms | 13.8 ms |
| p95 latency | 98.8 ms | 120.8 ms | 74.8 ms |
| p99 latency | 114.9 ms | 149.1 ms | 251.2 ms |
| Correctness | 99.96% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 30 | 15 |
| Unsupported | 0 | 0 | 243 |
| Samples | 8,111 | 8,255 | 8,256 |
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
+2.5points
- Latency+2.4
- Head freshness+0.1
- Availability−0.0
- Correctness−0.0
The parts add to +2.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+31.5points
- Availability+29.8
- Head freshness*+9.6
- Latency−5.6
- Correctness−2.2
The parts add to +31.5, 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.