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 07:57:53 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank1348
Score99.487.880.051.1
StatusExcellentGoodGoodDegraded
Availability99.99%99.96%100.00%23.11%
p50 latency18.0 ms31.3 ms87.4 ms13.0 ms
p95 latency29.5 ms63.8 ms104.4 ms70.3 ms
p99 latency59.6 ms157.1 ms140.0 ms130.6 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.37 blocks0.35 blocksno cohort
Rate limited03700
Unsupported000287
Samples9,7359,4979,5219,667

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

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

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

PublicNodevsNodeReal

+19.4points

  • Latency+19.5
  • Head freshness0.1
  • Availability0.0
  • Correctness+0.0

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

PublicNodevsCloudflare

+48.3points

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

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