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

30d window · 2.8 days observed · generated 2026-08-27 16:00:34 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APICloudflare
Rank1459
Score99.487.784.954.6
StatusExcellentGoodGoodDegraded
Availability99.98%99.83%99.98%23.11%
p50 latency19.0 ms87.4 ms105.0 ms15.2 ms
p95 latency34.9 ms100.0 ms122.4 ms87.9 ms
p99 latency74.3 ms126.3 ms146.9 ms251.2 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.35 blocks0.42 blocksno cohort
Rate limited001,17296
Unsupported0003,208
Samples109,964107,278108,546108,944

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

+11.7points

  • Latency+11.9
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsBlast API

+14.5points

  • Latency+14.6
  • Head freshness0.1
  • Availability0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+44.8points

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

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