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 08:24:35 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealBlast APICloudflare
Rank1458
Score99.479.978.050.9
StatusExcellentGoodGoodDegraded
Availability99.99%100.00%99.99%23.14%
p50 latency18.2 ms87.7 ms104.2 ms13.0 ms
p95 latency30.1 ms105.5 ms118.8 ms71.5 ms
p99 latency59.6 ms140.5 ms145.5 ms119.9 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.41 blocksno cohort
Rate limited00907
Unsupported000262
Samples8,8298,6298,7478,760

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

+19.5points

  • Latency+19.6
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsBlast API

+21.4points

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

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

PublicNodevsCloudflare

+48.5points

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

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