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 09:46:09 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV Blocker1RPC
Rank1479
Score99.480.569.50.0
StatusExcellentGoodDegradedPoor
Availability99.98%100.00%99.91%0.00%
p50 latency19.4 ms87.7 ms119.8 ms0.0 ms
p95 latency32.8 ms104.6 ms208.7 ms0.0 ms
p99 latency68.6 ms140.0 ms226.2 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.49 blocks0.36 blocks0.42 blocksno cohort
Rate limited0011,618
Unsupported0000
Samples9,4109,1979,3231,853

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

+18.9points

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

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

PublicNodevsMEV Blocker

+29.9points

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

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

PublicNodevs1RPC

+99.4points

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

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