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 13:05:57 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank2468
Score96.582.770.149.4
StatusExcellentGoodDegradedPoor
Availability99.98%100.00%100.00%23.17%
p50 latency23.4 ms87.8 ms108.0 ms15.7 ms
p95 latency45.3 ms99.6 ms200.3 ms88.9 ms
p99 latency116.3 ms123.9 ms231.3 ms128.5 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.49 blocksno cohort
Rate limited001,32419
Unsupported0016239
Samples8,3378,1201,9638,268

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.

PublicNodevsNodeReal

+13.8points

  • Latency+14.0
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMerkle

+26.4points

  • Latency+26.4
  • Availability0.0
  • Head freshness0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+47.2points

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

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