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 16:25:05 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkle1RPC
Rank2369
Score95.189.170.90.0
StatusExcellentGoodDegradedPoor
Availability99.99%99.94%100.00%0.00%
p50 latency25.3 ms34.5 ms109.9 ms0.0 ms
p95 latency49.6 ms69.9 ms191.4 ms0.0 ms
p99 latency113.4 ms185.6 ms235.5 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.49 blocks0.36 blocks0.51 blocksno cohort
Rate limited0201,4021,513
Unsupported00190
Samples8,8618,6242,0391,739

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

+6.0points

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

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

PublicNodevsMerkle

+24.2points

  • Latency+24.2
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

PublicNodevs1RPC

+95.1points

  • Availability+40.0
  • Latency*+25.7
  • Correctness*+20.0
  • Head freshness*+9.4

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