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 03:34:34 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank2367
Score99.290.777.877.2
StatusExcellentExcellentGoodGood
Availability99.99%99.94%100.00%99.94%
p50 latency17.2 ms33.1 ms104.9 ms117.8 ms
p95 latency33.9 ms69.1 ms199.7 ms208.9 ms
p99 latency82.7 ms168.5 ms263.5 ms228.8 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.38 blocks0.43 blocks0.39 blocks
Rate limited0291,4442
Unsupported00200
Samples9,1018,8862,0229,016

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.6
  • 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.4points

  • Latency+21.5
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsMEV Blocker

+21.9points

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

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

Latency over time