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 08:51:37 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV Blocker1RPC
Rank1379
Score99.488.369.50.0
StatusExcellentGoodDegradedPoor
Availability99.99%99.95%99.90%0.00%
p50 latency18.5 ms31.4 ms119.3 ms0.0 ms
p95 latency30.7 ms63.1 ms207.9 ms0.0 ms
p99 latency64.2 ms158.3 ms227.2 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.49 blocks0.37 blocks0.42 blocksno cohort
Rate limited03511,637
Unsupported0000
Samples9,5629,3259,4741,872

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

+11.1points

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

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

PublicNodevsMEV Blocker

+30.0points

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

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