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 17:33:37 UTC

Selected providers compared across every measured metric
MetricPublicNodeNodeRealCloudflare1RPC
Rank2489
Score94.982.945.90.0
StatusExcellentGoodPoorPoor
Availability100.00%100.00%23.12%0.00%
p50 latency25.5 ms87.5 ms17.7 ms0.0 ms
p95 latency50.6 ms99.5 ms106.9 ms0.0 ms
p99 latency113.2 ms127.8 ms262.0 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.33 blocksno cohortno cohort
Rate limited0001,560
Unsupported002680
Samples9,0808,8549,0251,789

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.

PublicNodevsNodeReal

+12.0points

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

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

PublicNodevsCloudflare

+49.1points

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

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

PublicNodevs1RPC

+94.9points

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

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