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

1h window · 60 minutes observed · generated 2026-08-26 23:12:04 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV Blocker1RPC
Rank2679
Score98.971.069.50.0
StatusExcellentDegradedDegradedPoor
Availability100.00%100.00%100.00%0.00%
p50 latency16.3 ms105.6 ms117.0 ms0.0 ms
p95 latency36.1 ms181.5 ms208.6 ms0.0 ms
p99 latency96.3 ms213.0 ms238.6 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.46 blocks0.40 blocksno cohort
Rate limited02551277
Unsupported0200
Samples1,5993551,594319

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.

PublicNodevsMerkle

+27.9points

  • Latency+27.9
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsMEV Blocker

+29.4points

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

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

PublicNodevs1RPC

+98.9points

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

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