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

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealMerkle
Rank2346
Score97.990.986.677.9
StatusExcellentExcellentGoodGood
Availability99.99%99.93%100.00%100.00%
p50 latency20.8 ms33.6 ms87.4 ms107.6 ms
p95 latency40.7 ms70.9 ms100.0 ms194.3 ms
p99 latency100.2 ms175.8 ms129.8 ms235.5 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.34 blocks0.53 blocks
Rate limited013305,925
Unsupported00072
Samples37,85536,91836,9228,609

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

  • Latency+7.1
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsNodeReal

+11.3points

  • Latency+11.5
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMerkle

+20.0points

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

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

Latency over time