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.8 days observed · generated 2026-08-27 16:03:24 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCMEV BlockerCloudflare
Rank1379
Score99.492.277.654.6
StatusExcellentExcellentGoodDegraded
Availability99.98%99.93%99.89%23.11%
p50 latency19.0 ms33.8 ms119.0 ms15.2 ms
p95 latency34.9 ms71.8 ms210.0 ms88.0 ms
p99 latency74.4 ms169.4 ms233.8 ms251.3 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.40 blocksno cohort
Rate limited0645396
Unsupported0003,211
Samples110,039107,386108,993109,021

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

+7.2points

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

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

PublicNodevsMEV Blocker

+21.8points

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

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

PublicNodevsCloudflare

+44.8points

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

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