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 05:50:50 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast API1RPCCloudflare
Rank1589
Score99.484.058.755.8
StatusExcellentGoodDegradedDegraded
Availability99.99%99.99%76.13%23.17%
p50 latency17.5 ms103.1 ms2024.4 ms12.8 ms
p95 latency32.0 ms115.5 ms6590.4 ms68.0 ms
p99 latency60.3 ms142.6 ms9196.2 ms160.7 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.48 blocks0.42 blocks0.95 blocksno cohort
Rate limited0781,6046
Unsupported000277
Samples9,5539,4642,2019,478

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.4points

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

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

PublicNodevs1RPC

+40.8points

  • Latency+30.0
  • Availability+9.5
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+43.6points

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

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