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-27 12:31:46 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNode1RPCCloudflare
Rank1289
Score99.499.058.053.1
StatusExcellentExcellentDegradedDegraded
Availability99.97%99.97%74.55%23.15%
p50 latency19.4 ms19.2 ms2024.4 ms15.3 ms
p95 latency34.8 ms36.7 ms6590.4 ms87.4 ms
p99 latency94.8 ms82.7 ms9196.2 ms187.7 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.49 blocks0.95 blocksno cohort
Rate limited006,52955
Unsupported0001,118
Samples38,08638,4297,83938,061

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 Tenderly, the highest scorer of those selected.

TenderlyvsPublicNode

+0.4points

  • Latency+0.4
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

Tenderlyvs1RPC

+41.4points

  • Latency+30.0
  • Availability+10.2
  • Correctness+0.7
  • Head freshness+0.5

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

TenderlyvsCloudflare

+46.2points

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

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