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 09:46:09 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMerkleCloudflare
Rank1468
Score99.480.570.150.3
StatusExcellentGoodDegradedDegraded
Availability99.98%100.00%100.00%23.09%
p50 latency19.4 ms87.7 ms105.0 ms13.5 ms
p95 latency32.8 ms104.6 ms194.3 ms77.1 ms
p99 latency68.6 ms140.0 ms228.8 ms116.5 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.60 blocksno cohort
Rate limited001,45819
Unsupported0018278
Samples9,4109,1972,1379,348

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

+18.9points

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

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

PublicNodevsMerkle

+29.3points

  • Latency+29.2
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+49.1points

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

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