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

7d window · 42 hours observed · generated 2026-08-26 14:54:06 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV BlockerCloudflare
Rank1679
Score99.478.477.655.8
StatusExcellentGoodGoodDegraded
Availability99.98%99.97%99.87%23.09%
p50 latency18.3 ms106.4 ms118.0 ms15.1 ms
p95 latency32.0 ms196.9 ms208.6 ms88.1 ms
p99 latency67.9 ms245.5 ms233.1 ms256.3 ms
Correctness99.98%100.00%99.98%100.00%
Head lag0.49 blocks0.47 blocks0.40 blocksno cohort
Rate limited011,094041
Unsupported013702,012
Samples68,93915,99168,30968,307

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

+21.0points

  • Latency+21.0
  • Head freshness0.0
  • Correctness0.0
  • Availability+0.0

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

PublicNodevsMEV Blocker

+21.8points

  • Latency+21.9
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+43.6points

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

The parts add to +43.6, 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