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
24h window · 24 hours observed · generated 2026-08-26 14:55:05 UTC
| Metric | NodeReal | Blast API | Cloudflare |
|---|---|---|---|
| Rank | 4 | 5 | 9 |
| Score | 88.8 | 86.0 | 55.6 |
| Status | Good | Good | Degraded |
| Availability | 99.99% | 99.97% | 23.09% |
| p50 latency | 87.6 ms | 104.3 ms | 15.8 ms |
| p95 latency | 100.0 ms | 121.6 ms | 89.9 ms |
| p99 latency | 124.4 ms | 142.0 ms | 253.6 ms |
| Correctness | 99.99% | 99.97% | 100.00% |
| Head lag | 0.35 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 309 | 9 |
| Unsupported | 0 | 0 | 1,144 |
| Samples | 38,130 | 38,718 | 38,764 |
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.8
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +2.9, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.2points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.8
- Correctness−2.2
The parts add to +33.2, 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.