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 · 3.2 days observed · generated 2026-08-28 00:21:25 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 9 |
| Score | 87.3 | 77.3 | 54.0 |
| Status | Good | Good | Degraded |
| Availability | 99.85% | 99.90% | 23.11% |
| p50 latency | 87.4 ms | 119.6 ms | 15.2 ms |
| p95 latency | 99.9 ms | 210.9 ms | 88.6 ms |
| p99 latency | 125.2 ms | 234.1 ms | 253.3 ms |
| Correctness | 99.99% | 99.99% | 100.00% |
| Head lag | 0.34 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 3 | 111 |
| Unsupported | 0 | 0 | 3,605 |
| Samples | 120,574 | 122,422 | 122,461 |
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
+10.0points
- Latency+9.9
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +10.0, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.3points
- Availability+29.7
- Head freshness*+9.6
- Latency−3.8
- Correctness−2.2
The parts add to +33.3, 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.