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:18:42 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV Blocker1RPC
Rank2479
Score95.782.969.50.0
StatusExcellentGoodDegradedPoor
Availability99.98%100.00%99.91%0.00%
p50 latency24.5 ms87.7 ms123.7 ms0.0 ms
p95 latency48.3 ms99.4 ms214.6 ms0.0 ms
p99 latency122.2 ms126.6 ms236.4 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.49 blocks0.33 blocks0.39 blocksno cohort
Rate limited0001,482
Unsupported0000
Samples8,6828,4548,5841,699

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.

PublicNodevsNodeReal

+12.8points

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

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

PublicNodevsMEV Blocker

+26.2points

  • Latency+26.3
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevs1RPC

+95.7points

  • Availability+40.0
  • Latency*+26.3
  • 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