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:53:39 UTC
| Metric | PublicNode | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 2 | 7 | 8 |
| Score | 95.5 | 69.5 | 48.2 |
| Status | Excellent | Degraded | Poor |
| Availability | 100.00% | 99.94% | 23.08% |
| p50 latency | 23.7 ms | 123.9 ms | 16.3 ms |
| p95 latency | 46.7 ms | 216.4 ms | 92.1 ms |
| p99 latency | 103.3 ms | 238.5 ms | 271.2 ms |
| Correctness | 100.00% | 99.98% | 100.00% |
| Head lag | 0.47 blocks | 0.39 blocks | no cohort |
| Rate limited | 0 | 0 | 15 |
| Unsupported | 0 | 0 | 282 |
| Samples | 9,629 | 9,535 | 9,538 |
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 PublicNode, the highest scorer of those selected.
PublicNodevsMEV Blocker
+26.0points
- Latency+26.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +26.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+47.3points
- Availability+29.7
- Latency+10.3
- Head freshness*+9.4
- Correctness−2.2
The parts add to +47.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.