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

30d window · 2.4 days observed · generated 2026-08-27 05:41:54 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank1367
Score99.493.078.877.9
StatusExcellentExcellentGoodGood
Availability99.97%99.93%99.98%99.89%
p50 latency18.2 ms33.9 ms106.5 ms118.4 ms
p95 latency33.5 ms72.0 ms195.9 ms209.2 ms
p99 latency69.9 ms168.2 ms243.2 ms232.8 ms
Correctness99.99%99.99%100.00%99.99%
Head lag0.49 blocks0.36 blocks0.47 blocks0.40 blocks
Rate limited058314,8612
Unsupported001810
Samples93,11790,88321,36292,234

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

+6.4points

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

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

PublicNodevsMerkle

+20.6points

  • Latency+20.6
  • Head freshness0.0
  • Correctness0.0
  • Availability0.0

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

PublicNodevsMEV Blocker

+21.5points

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

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

Latency over time