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-26 17:04:11 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank1349
Score99.492.087.153.2
StatusExcellentExcellentGoodDegraded
Availability99.98%99.95%100.00%23.10%
p50 latency19.1 ms34.1 ms87.5 ms15.9 ms
p95 latency32.5 ms68.4 ms100.1 ms91.9 ms
p99 latency71.3 ms166.4 ms123.9 ms248.3 ms
Correctness99.98%99.99%100.00%100.00%
Head lag0.49 blocks0.36 blocks0.35 blocksno cohort
Rate limited011109
Unsupported0001,104
Samples37,68136,79936,76837,376

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.

PublicNodevsNodeReal

+12.3points

  • Latency+12.5
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+46.2points

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

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