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 17:42:56 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APICloudflare
Rank2359
Score98.291.283.953.5
StatusExcellentExcellentGoodDegraded
Availability99.97%99.94%99.99%23.15%
p50 latency20.4 ms33.8 ms106.1 ms15.0 ms
p95 latency40.1 ms70.0 ms122.7 ms87.0 ms
p99 latency95.9 ms170.8 ms149.9 ms242.0 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.42 blocksno cohort
Rate limited013632336
Unsupported0001,130
Samples38,74937,78238,25638,445

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

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

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

PublicNodevsBlast API

+14.2points

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

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

PublicNodevsCloudflare

+44.7points

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

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