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.3 days observed · generated 2026-08-27 04:25:45 UTC

Selected providers compared across every measured metric
MetricPublicNodeMEV Blocker1RPCCloudflare
Rank1789
Score99.478.062.655.7
StatusExcellentGoodDegradedDegraded
Availability99.97%99.89%85.50%23.11%
p50 latency18.2 ms118.5 ms225.7 ms15.1 ms
p95 latency33.6 ms209.3 ms4391.3 ms88.3 ms
p99 latency70.2 ms233.0 ms7602.5 ms253.9 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.40 blocks0.91 blocksno cohort
Rate limited0215,50277
Unsupported0002,655
Samples91,04090,18419,16490,166

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

+21.4points

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

The parts add to +21.4, 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.

PublicNodevsCloudflare

+43.7points

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

The parts add to +43.7, 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