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-26 13:56:33 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV BlockerCloudflare
Rank1679
Score99.478.577.655.3
StatusExcellentGoodGoodDegraded
Availability99.97%99.95%99.85%23.08%
p50 latency19.1 ms106.4 ms118.7 ms15.7 ms
p95 latency32.3 ms197.1 ms210.0 ms90.2 ms
p99 latency71.5 ms243.1 ms236.1 ms256.2 ms
Correctness99.97%100.00%99.98%100.00%
Head lag0.49 blocks0.46 blocks0.39 blocksno cohort
Rate limited06,26409
Unsupported08401,147
Samples39,0999,04138,71938,813

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.9points

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

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

PublicNodevsMEV Blocker

+21.8points

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

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

PublicNodevsCloudflare

+44.1points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency+7.2
  • Correctness2.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.

Latency over time