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 14:55:50 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCBlast APICloudflare
Rank2358
Score95.588.178.448.0
StatusExcellentGoodGoodPoor
Availability99.98%99.95%99.99%23.19%
p50 latency24.7 ms34.2 ms108.3 ms16.5 ms
p95 latency48.9 ms74.1 ms126.2 ms96.0 ms
p99 latency116.9 ms185.2 ms153.5 ms157.4 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.50 blocks0.36 blocks0.41 blocksno cohort
Rate limited0407112
Unsupported000279
Samples9,6929,4549,6079,615

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

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

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

PublicNodevsBlast API

+17.1points

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

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

PublicNodevsCloudflare

+47.6points

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

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