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

Selected providers compared across every measured metric
MetricPublicNodedRPC1RPCCloudflare
Rank1389
Score99.491.058.552.3
StatusExcellentExcellentDegradedDegraded
Availability99.98%99.92%75.73%23.13%
p50 latency18.2 ms34.0 ms2024.4 ms16.1 ms
p95 latency35.1 ms69.8 ms6590.4 ms93.4 ms
p99 latency73.7 ms172.6 ms9196.2 ms246.4 ms
Correctness100.00%99.99%96.63%100.00%
Head lag0.49 blocks0.38 blocks0.95 blocksno cohort
Rate limited01346,66236
Unsupported0001,146
Samples39,16338,2227,99038,803

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

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

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

PublicNodevs1RPC

+40.9points

  • Latency+30.0
  • Availability+9.7
  • Correctness+0.7
  • Head freshness+0.5

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

PublicNodevsCloudflare

+47.1points

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

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