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 14:53:30 UTC

Selected providers compared across every measured metric
MetricPublicNodeBlast API1RPCCloudflare
Rank2589
Score98.583.857.853.2
StatusExcellentGoodDegradedDegraded
Availability99.97%99.99%73.97%23.16%
p50 latency19.7 ms105.8 ms2024.4 ms15.1 ms
p95 latency38.2 ms122.2 ms6590.4 ms87.3 ms
p99 latency88.8 ms148.6 ms9196.2 ms214.9 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.41 blocks0.95 blocksno cohort
Rate limited03446,63755
Unsupported0001,138
Samples39,03338,4717,96938,664

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

+14.7points

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

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

PublicNodevs1RPC

+40.8points

  • Latency+29.2
  • Availability+10.4
  • 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

+45.3points

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

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