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:50:59 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeReal1RPC
Rank2349
Score95.588.183.00.0
StatusExcellentGoodGoodPoor
Availability99.98%99.95%100.00%0.00%
p50 latency24.7 ms34.2 ms87.7 ms0.0 ms
p95 latency49.0 ms74.5 ms99.4 ms0.0 ms
p99 latency117.2 ms185.4 ms126.5 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.50 blocks0.36 blocks0.33 blocksno cohort
Rate limited04001,635
Unsupported0000
Samples9,5649,3239,3101,875

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

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

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

PublicNodevs1RPC

+95.5points

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

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