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-27 18:37:58 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 9 |
| Score | 86.7 | 76.9 | 53.5 |
| Status | Good | Good | Degraded |
| Availability | 100.00% | 99.93% | 23.15% |
| p50 latency | 87.4 ms | 121.3 ms | 15.1 ms |
| p95 latency | 100.0 ms | 212.5 ms | 86.8 ms |
| p99 latency | 129.8 ms | 235.2 ms | 246.7 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.34 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 3 | 36 |
| Unsupported | 0 | 0 | 1,126 |
| Samples | 37,661 | 38,202 | 38,300 |
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
+9.8points
- Latency+9.7
- Head freshness+0.1
- Availability+0.0
- Correctness−0.0
The parts add to +9.8, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.1points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.9
- Correctness−2.2
The parts add to +33.1, 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.