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 14:35:29 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealMerkle
Rank2346
Score95.588.282.970.5
StatusExcellentGoodGoodDegraded
Availability99.98%99.94%100.00%100.00%
p50 latency24.6 ms34.0 ms87.7 ms108.1 ms
p95 latency48.9 ms74.0 ms99.4 ms197.2 ms
p99 latency122.7 ms176.2 ms126.3 ms231.3 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.33 blocks0.44 blocks
Rate limited04001,427
Unsupported00016
Samples9,1408,9148,8982,121

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

  • Latency+7.5
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsNodeReal

+12.6points

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

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

PublicNodevsMerkle

+25.1points

  • Latency+25.1
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

Latency over time