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

30d window · 47 hours observed · generated 2026-08-26 19:44:16 UTC

Selected providers compared across every measured metric
MetricPublicNodedRPCNodeRealCloudflare
Rank1239
Score99.493.688.655.3
StatusExcellentExcellentGoodDegraded
Availability99.97%99.94%99.76%23.09%
p50 latency18.5 ms34.0 ms87.4 ms15.4 ms
p95 latency33.1 ms72.5 ms100.0 ms91.3 ms
p99 latency68.9 ms167.8 ms123.8 ms254.2 ms
Correctness99.98%99.99%99.99%100.00%
Head lag0.49 blocks0.36 blocks0.35 blocksno cohort
Rate limited0526060
Unsupported0002,243
Samples76,82875,00974,96376,078

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

+5.8points

  • Latency+6.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsNodeReal

+10.8points

  • Latency+10.9
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

PublicNodevsCloudflare

+44.1points

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

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