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
1h window · 60 minutes observed · generated 2026-08-27 20:25:07 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 8 |
| Score | 83.0 | 69.5 | 47.2 |
| Status | Good | Degraded | Poor |
| Availability | 100.00% | 100.00% | 22.91% |
| p50 latency | 87.0 ms | 125.1 ms | 17.9 ms |
| p95 latency | 98.8 ms | 216.2 ms | 99.0 ms |
| p99 latency | 121.6 ms | 235.2 ms | 264.6 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.35 blocks | 0.41 blocks | no cohort |
| Rate limited | 0 | 0 | 0 |
| Unsupported | 0 | 0 | 46 |
| Samples | 1,557 | 1,603 | 1,593 |
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.5points
- Latency+13.4
- Head freshness+0.1
- Availability+0.0
- Correctness+0.0
The parts add to +13.5, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+35.7points
- Availability+29.8
- Head freshness*+9.6
- Correctness−2.2
- Latency−1.4
The parts add to +35.7, 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.