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.1 days observed · generated 2026-08-26 22:00:25 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV BlockerCloudflare
Rank1279
Score99.493.677.755.5
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.88%23.10%
p50 latency18.4 ms34.1 ms118.6 ms15.5 ms
p95 latency33.6 ms73.0 ms209.5 ms91.2 ms
p99 latency69.8 ms169.1 ms233.4 ms254.5 ms
Correctness99.99%99.99%99.98%100.00%
Head lag0.49 blocks0.36 blocks0.40 blocksno cohort
Rate limited0542071
Unsupported0002,351
Samples80,55778,62679,80579,753

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

+5.8points

  • Latency+5.9
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsMEV Blocker

+21.7points

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

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

PublicNodevsCloudflare

+43.9points

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

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