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 17:20:58 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV Blocker1RPC
Rank2379
Score95.089.569.50.0
StatusExcellentGoodDegradedPoor
Availability100.00%99.95%99.90%0.00%
p50 latency25.5 ms34.5 ms125.2 ms0.0 ms
p95 latency50.0 ms68.4 ms217.5 ms0.0 ms
p99 latency113.6 ms177.7 ms244.0 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.49 blocks0.36 blocks0.40 blocksno cohort
Rate limited02101,495
Unsupported0000
Samples8,7358,5178,6331,715

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

+5.5points

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

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

PublicNodevsMEV Blocker

+25.6points

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

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

PublicNodevs1RPC

+95.0points

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

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