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
30d window · 2.3 days observed · generated 2026-08-27 04:01:20 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 88.7 | 85.8 | 55.8 |
| Status | Good | Good | Degraded |
| Availability | 99.79% | 99.98% | 23.11% |
| p50 latency | 87.3 ms | 104.5 ms | 15.1 ms |
| p95 latency | 99.8 ms | 122.1 ms | 88.4 ms |
| p99 latency | 123.3 ms | 144.2 ms | 254.1 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 987 | 77 |
| Unsupported | 0 | 0 | 2,635 |
| Samples | 88,170 | 89,145 | 89,507 |
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.9points
- Latency+2.9
- Head freshness+0.1
- Availability−0.1
- Correctness+0.0
The parts add to +2.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+32.9points
- Availability+29.6
- Head freshness*+9.6
- Latency−4.1
- Correctness−2.2
The parts add to +32.9, 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.