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.7 days observed · generated 2026-08-27 14:27:15 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APICloudflare
Rank1359
Score99.492.385.054.8
StatusExcellentExcellentGoodDegraded
Availability99.97%99.93%99.98%23.11%
p50 latency18.8 ms33.8 ms104.9 ms15.1 ms
p95 latency34.5 ms71.9 ms122.3 ms87.5 ms
p99 latency73.3 ms168.5 ms146.3 ms250.7 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.42 blocksno cohort
Rate limited06411,15496
Unsupported0003,133
Samples107,421104,842106,030106,423

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.

PublicNodevsdRPC

+7.1points

  • Latency+7.3
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsBlast API

+14.4points

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

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

PublicNodevsCloudflare

+44.6points

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

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