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 08:57:12 UTC
| Metric | PublicNode | MEV Blocker | Cloudflare |
|---|---|---|---|
| Rank | 1 | 7 | 8 |
| Score | 99.4 | 69.5 | 50.9 |
| Status | Excellent | Degraded | Degraded |
| Availability | 99.99% | 99.91% | 23.14% |
| p50 latency | 18.5 ms | 119.4 ms | 13.1 ms |
| p95 latency | 30.9 ms | 207.9 ms | 72.6 ms |
| p99 latency | 64.5 ms | 227.0 ms | 119.9 ms |
| Correctness | 100.00% | 100.00% | 100.00% |
| Head lag | 0.49 blocks | 0.42 blocks | no cohort |
| Rate limited | 0 | 1 | 7 |
| Unsupported | 0 | 0 | 287 |
| Samples | 9,714 | 9,616 | 9,647 |
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
+30.0points
- Latency+30.0
- Head freshness−0.1
- Availability+0.0
- Correctness+0.0
The parts add to +30.0, exactly — the score is a weighted sum, so it comes apart.
PublicNodevsCloudflare
+48.5points
- Availability+29.7
- Latency+11.6
- Head freshness*+9.4
- Correctness−2.2
The parts add to +48.5, 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.