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
7d window · 48 hours observed · generated 2026-08-26 20:13:54 UTC
| Metric | NodeReal | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 4 | 7 | 9 |
| Score | 88.7 | 77.4 | 55.3 |
| Status | Good | Good | Degraded |
| Availability | 99.76% | 99.87% | 23.09% |
| p50 latency | 87.4 ms | 118.5 ms | 15.5 ms |
| p95 latency | 100.0 ms | 209.4 ms | 91.4 ms |
| p99 latency | 123.7 ms | 233.5 ms | 253.9 ms |
| Correctness | 99.99% | 99.98% | 100.00% |
| Head lag | 0.35 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 0 | 60 |
| Unsupported | 0 | 0 | 2,267 |
| Samples | 75,743 | 76,938 | 76,876 |
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
+11.2points
- Latency+11.2
- Head freshness+0.1
- Availability−0.0
- Correctness+0.0
The parts add to +11.2, exactly — the score is a weighted sum, so it comes apart.
NodeRealvsCloudflare
+33.4points
- Availability+29.6
- Head freshness*+9.6
- Latency−3.6
- Correctness−2.2
The parts add to +33.4, 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.