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

7d window · 2.8 days observed · generated 2026-08-27 16:28:32 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealMEV Blocker1RPC
Rank1478
Score99.487.777.662.4
StatusExcellentGoodGoodDegraded
Availability99.98%99.83%99.89%84.99%
p50 latency19.0 ms87.4 ms119.0 ms225.7 ms
p95 latency35.0 ms100.0 ms210.1 ms4391.3 ms
p99 latency74.6 ms126.3 ms233.9 ms7602.5 ms
Correctness99.99%99.99%99.99%97.48%
Head lag0.49 blocks0.35 blocks0.40 blocks0.91 blocks
Rate limited00318,871
Unsupported0000
Samples110,724108,022109,67223,027

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.

PublicNodevsNodeReal

+11.7points

  • Latency+11.8
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.8points

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

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

PublicNodevs1RPC

+37.0points

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

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

Latency over time