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 10:50:00 UTC

Selected providers compared across every measured metric
MetricPublicNodeMerkleMEV Blocker1RPC
Rank2679
Score98.870.169.50.0
StatusExcellentDegradedDegradedPoor
Availability99.98%100.00%99.94%0.00%
p50 latency20.3 ms106.3 ms120.6 ms0.0 ms
p95 latency36.1 ms196.0 ms209.6 ms0.0 ms
p99 latency91.7 ms228.8 ms228.5 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.49 blocks0.57 blocks0.41 blocksno cohort
Rate limited01,48811,629
Unsupported01800
Samples9,5142,2039,4241,865

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

+28.8points

  • Latency+28.7
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+29.4points

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

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

PublicNodevs1RPC

+98.8points

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

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