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 13:38:25 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast API1RPCCloudflare
Rank2589
Score98.883.857.853.0
StatusExcellentGoodDegradedDegraded
Availability99.97%99.99%73.97%23.14%
p50 latency19.4 ms105.7 ms2024.4 ms15.1 ms
p95 latency37.3 ms122.5 ms6590.4 ms88.1 ms
p99 latency86.7 ms149.0 ms9196.2 ms217.9 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.41 blocks0.95 blocksno cohort
Rate limited03316,56955
Unsupported0001,124
Samples38,61838,0687,88838,246

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

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

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

PublicNodevs1RPC

+41.0points

  • Latency+29.4
  • Availability+10.4
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+45.8points

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

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