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 06:54:04 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank1367
Score99.490.977.976.9
StatusExcellentExcellentGoodGood
Availability99.97%99.91%100.00%99.90%
p50 latency18.2 ms34.1 ms107.1 ms119.8 ms
p95 latency35.1 ms69.5 ms193.4 ms210.0 ms
p99 latency73.4 ms171.8 ms240.0 ms233.4 ms
Correctness100.00%99.99%100.00%99.99%
Head lag0.49 blocks0.38 blocks0.49 blocks0.40 blocks
Rate limited01406,1612
Unsupported00730
Samples39,02238,1008,81638,645

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.5points

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

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

PublicNodevsMerkle

+21.5points

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

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

PublicNodevsMEV Blocker

+22.5points

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

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

Latency over time