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 07:14:28 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealCloudflare1RPC
Rank1489
Score99.479.851.20.0
StatusExcellentGoodDegradedPoor
Availability99.99%100.00%23.12%0.00%
p50 latency17.8 ms87.4 ms12.9 ms0.0 ms
p95 latency29.2 ms105.4 ms69.4 ms0.0 ms
p99 latency56.5 ms143.0 ms130.6 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.35 blocksno cohortno cohort
Rate limited0001,461
Unsupported002520
Samples8,5568,3668,4971,676

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.

PublicNodevsNodeReal

+19.6points

  • Latency+19.7
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+48.2points

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

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