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 12:17:12 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank2349
Score99.090.386.453.1
StatusExcellentExcellentGoodDegraded
Availability99.97%99.91%100.00%23.15%
p50 latency19.2 ms34.2 ms87.3 ms15.2 ms
p95 latency36.7 ms73.2 ms100.1 ms87.4 ms
p99 latency82.3 ms173.1 ms128.5 ms185.6 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.38 blocks0.34 blocksno cohort
Rate limited0161055
Unsupported0001,108
Samples38,03137,10837,08837,668

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

+8.7points

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

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

PublicNodevsNodeReal

+12.6points

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

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

PublicNodevsCloudflare

+45.9points

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

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