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 02:29:36 UTC

Selected providers compared across every measured metric
MetricPublicNodeMEV Blocker1RPCCloudflare
Rank1789
Score99.477.058.552.3
StatusExcellentGoodDegradedDegraded
Availability99.98%99.89%75.73%23.12%
p50 latency18.4 ms119.3 ms2024.4 ms16.2 ms
p95 latency35.2 ms210.7 ms6590.4 ms93.5 ms
p99 latency74.0 ms234.1 ms9196.2 ms247.0 ms
Correctness100.00%99.99%96.63%100.00%
Head lag0.49 blocks0.39 blocks0.95 blocksno cohort
Rate limited026,52145
Unsupported0001,122
Samples38,35838,0067,82838,003

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.

PublicNodevsMEV Blocker

+22.4points

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

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

PublicNodevs1RPC

+40.9points

  • Latency+30.0
  • Availability+9.7
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+47.1points

  • Availability+29.7
  • Latency+10.2
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +47.1, exactly — the score is a weighted sum, so it comes apart. Components marked * were measured for only one of the two; the other’s weight is spread across what it does have, which is why the two sides can carry different weights for the same row.

Latency over time