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 · 2.8 days observed · generated 2026-08-27 16:07:55 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealMerkle
Rank1346
Score99.492.287.778.5
StatusExcellentExcellentGoodGood
Availability99.98%99.93%99.83%99.98%
p50 latency19.0 ms33.8 ms87.4 ms106.7 ms
p95 latency34.9 ms71.9 ms100.0 ms196.0 ms
p99 latency74.4 ms169.5 ms126.3 ms243.3 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.35 blocks0.48 blocks
Rate limited0645017,568
Unsupported000216
Samples110,158107,507107,47325,325

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.

PublicNodevsdRPC

+7.2points

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

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

PublicNodevsNodeReal

+11.7points

  • Latency+11.8
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsMerkle

+20.9points

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

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

Latency over time