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 22:08:44 UTC

Selected providers compared across every measured metric
MetricPublicNodeTenderly1RPCCloudflare
Rank1289
Score99.498.864.452.3
StatusExcellentExcellentDegradedDegraded
Availability99.98%99.97%89.75%23.09%
p50 latency18.7 ms19.8 ms259.6 ms16.1 ms
p95 latency34.6 ms37.5 ms2579.7 ms94.2 ms
p99 latency72.0 ms266.9 ms4625.5 ms247.4 ms
Correctness99.99%99.99%98.18%100.00%
Head lag0.49 blocks0.49 blocks0.94 blocksno cohort
Rate limited006,43239
Unsupported0001,107
Samples37,80037,5287,70737,410

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

+0.6points

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

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

PublicNodevs1RPC

+35.0points

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

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

PublicNodevsCloudflare

+47.1points

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

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