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

24h window · 24 hours observed · generated 2026-08-27 19:03:45 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV BlockerCloudflare
Rank2679
Score97.977.976.953.6
StatusExcellentGoodGoodDegraded
Availability99.99%100.00%99.93%23.16%
p50 latency20.8 ms107.5 ms121.1 ms15.0 ms
p95 latency40.8 ms194.7 ms212.5 ms85.7 ms
p99 latency100.3 ms235.5 ms235.0 ms248.1 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.53 blocks0.40 blocksno cohort
Rate limited05,888336
Unsupported07201,099
Samples37,6908,55437,28037,388

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

+20.0points

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

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

PublicNodevsMEV Blocker

+21.0points

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

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

PublicNodevsCloudflare

+44.3points

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

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

Latency over time