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

24h window · 24 hours observed · generated 2026-08-26 15:58:09 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderly1RPCCloudflare
Rank1289
Score99.494.864.754.7
StatusExcellentExcellentDegradedDegraded
Availability99.98%99.95%90.50%23.08%
p50 latency19.2 ms20.3 ms259.6 ms15.9 ms
p95 latency32.4 ms61.3 ms2579.7 ms90.8 ms
p99 latency70.8 ms853.1 ms4625.5 ms251.4 ms
Correctness99.98%99.98%98.18%100.00%
Head lag0.49 blocks0.50 blocks0.94 blocksno cohort
Rate limited006,6709
Unsupported0001,146
Samples39,13538,8937,97038,839

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

  • Latency+4.6
  • Head freshness+0.0
  • Availability+0.0
  • Correctness+0.0

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

PublicNodevs1RPC

+34.7points

  • Latency+30.0
  • Availability+3.8
  • Head freshness+0.5
  • Correctness+0.4

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

PublicNodevsCloudflare

+44.7points

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

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