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

24h window · 24 hours observed · generated 2026-08-27 10:49:03 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank2367
Score99.290.577.876.8
StatusExcellentExcellentGoodGood
Availability99.97%99.91%100.00%99.92%
p50 latency18.9 ms34.2 ms107.1 ms120.2 ms
p95 latency36.0 ms72.1 ms193.4 ms210.6 ms
p99 latency79.6 ms175.5 ms237.9 ms232.4 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.38 blocks0.51 blocks0.40 blocks
Rate limited01666,1553
Unsupported00760
Samples38,90537,9558,84838,518

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

+8.7points

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

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

PublicNodevsMerkle

+21.4points

  • Latency+21.4
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+22.4points

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

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

Latency over time