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.2 days observed · generated 2026-08-27 02:26:13 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV Blocker1RPC
Rank1378
Score99.493.678.262.6
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.88%85.50%
p50 latency18.3 ms34.0 ms118.5 ms225.7 ms
p95 latency33.7 ms72.6 ms209.5 ms4391.3 ms
p99 latency70.4 ms169.2 ms233.3 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.49 blocks0.36 blocks0.40 blocks0.91 blocks
Rate limited0565214,945
Unsupported0000
Samples87,79285,68886,97518,528

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

+5.8points

  • Latency+5.9
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.2points

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

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

PublicNodevs1RPC

+36.8points

  • Latency+30.0
  • Availability+5.8
  • Correctness+0.5
  • Head freshness+0.5

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

Latency over time