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

7d window · 2.5 days observed · generated 2026-08-27 09:43:37 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlyNodeRealCloudflare
Rank1249
Score99.495.388.055.3
StatusExcellentExcellentGoodDegraded
Availability99.97%99.96%99.81%23.10%
p50 latency18.4 ms19.8 ms87.4 ms15.0 ms
p95 latency33.6 ms58.8 ms100.1 ms86.8 ms
p99 latency70.3 ms813.4 ms125.7 ms252.0 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.35 blocksno cohort
Rate limited00096
Unsupported0002,908
Samples99,68698,92497,27498,754

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.

PublicNodevsTenderly

+4.1points

  • Latency+4.1
  • Head freshness+0.0
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsNodeReal

+11.4points

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

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