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 22:00:33 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 82.8 | 69.5 | 47.8 |
| Status | Good | Degraded | Poor |
| Availability | 99.97% | 99.94% | 23.09% |
| p50 latency | 87.1 ms | 124.4 ms | 16.8 ms |
| p95 latency | 98.8 ms | 216.5 ms | 95.6 ms |
| p99 latency | 117.7 ms | 239.0 ms | 273.3 ms |
| Correctness | 99.97% | 99.98% | 100.00% |
| Head lag | 0.33 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 240 |
| Samples | 7,982 | 8,106 | 8,105 |
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.
NodeRealvsMEV Blocker
+13.3points
- Latency+13.2
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +13.3, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+35.0points
- Availability+29.7
- Head freshness*+9.6
- Correctness−2.2
- Latency−2.1
The parts add to +35.0, 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.