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:07:58 UTC
| Metric | PublicNode | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 1 | 7 | 9 |
| Score | 99.4 | 77.4 | 55.3 |
| Status | Excellent | Good | Degraded |
| Availability | 99.97% | 99.87% | 23.09% |
| p50 latency | 18.5 ms | 118.5 ms | 15.5 ms |
| p95 latency | 33.2 ms | 209.4 ms | 91.4 ms |
| p99 latency | 68.9 ms | 233.5 ms | 254.0 ms |
| Correctness | 99.98% | 99.98% | 100.00% |
| Head lag | 0.49 blocks | 0.40 blocks | no cohort |
| Rate limited | 0 | 0 | 60 |
| Unsupported | 0 | 0 | 2,262 |
| Samples | 77,478 | 76,780 | 76,715 |
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
+22.0points
- Latency+22.1
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +22.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+44.1points
- Availability+29.7
- Head freshness*+9.4
- Latency+7.2
- Correctness−2.2
The parts add to +44.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.