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.5 days observed · generated 2026-08-27 08:26:47 UTC

Selected providers compared across every measured metric
MetricPublicNodeMEV Blocker1RPCCloudflare
Rank1789
Score99.477.862.555.3
StatusExcellentGoodDegradedDegraded
Availability99.97%99.89%85.27%23.11%
p50 latency18.3 ms118.5 ms225.7 ms15.0 ms
p95 latency33.5 ms209.2 ms4391.3 ms86.9 ms
p99 latency69.7 ms232.8 ms7602.5 ms252.3 ms
Correctness99.99%99.99%97.48%100.00%
Head lag0.49 blocks0.40 blocks0.91 blocksno cohort
Rate limited0316,61984
Unsupported0002,850
Samples97,59496,68420,44696,672

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

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

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

PublicNodevs1RPC

+36.9points

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

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

PublicNodevsCloudflare

+44.1points

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

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