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

7d window · 2.5 days observed · generated 2026-08-27 09:12:04 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APICloudflare
Rank1459
Score99.488.085.355.3
StatusExcellentGoodGoodDegraded
Availability99.97%99.81%99.98%23.10%
p50 latency18.3 ms87.4 ms104.5 ms15.0 ms
p95 latency33.5 ms100.1 ms122.0 ms86.9 ms
p99 latency70.1 ms125.8 ms145.0 ms252.3 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.35 blocks0.42 blocksno cohort
Rate limited001,09784
Unsupported0002,885
Samples98,82696,43697,52097,906

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

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

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

PublicNodevsBlast API

+14.1points

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

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

PublicNodevsCloudflare

+44.1points

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

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