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

6h window · 6.0 hours observed · generated 2026-08-27 09:32:35 UTC

Selected providers compared across every measured metric
MetricPublicNodeMEV BlockerCloudflare1RPC
Rank1789
Score99.469.550.20.0
StatusExcellentDegradedDegradedPoor
Availability99.98%99.91%23.09%0.00%
p50 latency19.2 ms119.7 ms13.4 ms0.0 ms
p95 latency32.1 ms208.6 ms76.5 ms0.0 ms
p99 latency67.4 ms226.9 ms116.8 ms0.0 ms
Correctness99.99%100.00%100.00%not measured
Head lag0.49 blocks0.42 blocksno cohortno cohort
Rate limited01191,549
Unsupported002660
Samples9,0398,9618,9841,773

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

+29.9points

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

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

PublicNodevsCloudflare

+49.2points

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

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

PublicNodevs1RPC

+99.4points

  • Availability+40.0
  • Latency*+30.0
  • Correctness*+20.0
  • Head freshness*+9.4

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