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

24h window · 24 hours observed · generated 2026-08-27 09:58:14 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast API1RPCCloudflare
Rank2589
Score99.383.858.252.9
StatusExcellentGoodDegradedDegraded
Availability99.97%99.99%74.93%23.12%
p50 latency18.7 ms105.4 ms2024.4 ms15.6 ms
p95 latency35.7 ms122.5 ms6590.4 ms88.9 ms
p99 latency76.9 ms146.7 ms9196.2 ms238.9 ms
Correctness100.00%99.99%96.63%100.00%
Head lag0.49 blocks0.42 blocks0.95 blocksno cohort
Rate limited03666,66155
Unsupported0001,140
Samples39,14638,6067,98838,765

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.

PublicNodevsBlast API

+15.5points

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

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

PublicNodevs1RPC

+41.1points

  • Latency+29.9
  • Availability+10.0
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+46.4points

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

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