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 10:35:38 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCCloudflare1RPC
Rank2389
Score98.987.750.00.0
StatusExcellentGoodDegradedPoor
Availability99.98%99.94%23.14%0.00%
p50 latency20.2 ms32.1 ms14.0 ms0.0 ms
p95 latency35.9 ms70.0 ms80.7 ms0.0 ms
p99 latency88.8 ms163.0 ms116.5 ms0.0 ms
Correctness99.99%99.99%100.00%not measured
Head lag0.49 blocks0.35 blocksno cohortno cohort
Rate limited043191,558
Unsupported002660
Samples9,1218,9129,0721,784

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

+11.2points

  • Latency+11.3
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+48.9points

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

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

PublicNodevs1RPC

+98.9points

  • Availability+40.0
  • Latency*+29.5
  • Correctness*+20.0
  • Head freshness*+9.4

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