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.9 days observed · generated 2026-08-27 19:23:59 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderlydRPCCloudflare
Rank1239
Score99.496.992.054.2
StatusExcellentExcellentExcellentDegraded
Availability99.98%99.97%99.94%23.11%
p50 latency19.3 ms19.8 ms33.9 ms15.3 ms
p95 latency35.7 ms49.2 ms71.8 ms89.3 ms
p99 latency76.4 ms727.6 ms170.5 ms252.9 ms
Correctness99.99%99.99%99.99%100.00%
Head lag0.49 blocks0.50 blocks0.36 blocksno cohort
Rate limited0066196
Unsupported0003,371
Samples115,504114,615112,730114,433

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

+2.5points

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

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

PublicNodevsdRPC

+7.4points

  • Latency+7.5
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.0

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

PublicNodevsCloudflare

+45.2points

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

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