Skip to content

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 12:54:03 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV BlockerCloudflare
Rank2678
Score97.169.969.549.6
StatusExcellentDegradedDegradedPoor
Availability99.98%100.00%99.93%23.17%
p50 latency22.6 ms107.3 ms122.8 ms15.4 ms
p95 latency42.8 ms202.1 ms212.4 ms86.8 ms
p99 latency108.3 ms231.3 ms234.3 ms124.6 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.51 blocks0.40 blocksno cohort
Rate limited01,561119
Unsupported0190279
Samples9,6392,2999,5399,574

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.

PublicNodevsMerkle

+27.2points

  • Latency+27.2
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

The parts add to +27.2, exactly — the score is a weighted sum, so it comes apart.

PublicNodevsMEV Blocker

+27.6points

  • Latency+27.7
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

The parts add to +27.6, exactly — the score is a weighted sum, so it comes apart.

PublicNodevsCloudflare

+47.5points

  • Availability+29.7
  • Latency+10.7
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +47.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.

Latency over time