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 18:32:32 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV Blocker1RPC
Rank2378
Score98.191.176.957.8
StatusExcellentExcellentGoodDegraded
Availability99.99%99.94%99.93%73.97%
p50 latency20.7 ms33.8 ms121.2 ms2024.4 ms
p95 latency40.5 ms70.7 ms212.5 ms6590.4 ms
p99 latency97.6 ms174.1 ms235.2 ms9196.2 ms
Correctness100.00%99.99%100.00%96.63%
Head lag0.49 blocks0.37 blocks0.40 blocks0.95 blocks
Rate limited013736,546
Unsupported0000
Samples38,46937,51738,0557,859

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

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

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

PublicNodevsMEV Blocker

+21.2points

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

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

PublicNodevs1RPC

+40.3points

  • Latency+28.7
  • Availability+10.4
  • Correctness+0.7
  • Head freshness+0.5

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

Latency over time