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.9 days observed · generated 2026-08-27 17:49:57 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMerkleMEV Blocker
Rank1367
Score99.492.178.477.5
StatusExcellentExcellentGoodGood
Availability99.98%99.93%99.98%99.89%
p50 latency19.2 ms33.9 ms106.9 ms119.2 ms
p95 latency35.4 ms71.7 ms195.7 ms210.2 ms
p99 latency75.3 ms169.2 ms243.1 ms233.9 ms
Correctness99.99%99.99%100.00%99.99%
Head lag0.49 blocks0.36 blocks0.48 blocks0.40 blocks
Rate limited065218,0063
Unsupported002200
Samples112,938110,23025,975111,858

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

+7.3points

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

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

PublicNodevsMerkle

+21.0points

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

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

PublicNodevsMEV Blocker

+21.9points

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

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

Latency over time