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

1h window · 60 minutes observed · generated 2026-08-27 12:04:34 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeReal1RPC
Rank2349
Score95.785.183.20.0
StatusExcellentGoodGoodPoor
Availability99.94%99.94%100.00%0.00%
p50 latency23.9 ms34.6 ms86.7 ms0.0 ms
p95 latency47.4 ms87.6 ms98.3 ms0.0 ms
p99 latency95.7 ms190.8 ms125.2 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.51 blocks0.39 blocks0.34 blocksno cohort
Rate limited050276
Unsupported0000
Samples1,6241,5771,575318

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

+10.6points

  • Latency+10.7
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsNodeReal

+12.5points

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

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

PublicNodevs1RPC

+95.7points

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

The parts add to +95.7, 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