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:25:17 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodedRPCCloudflare
Rank1239
Score99.499.090.353.1
StatusExcellentExcellentExcellentDegraded
Availability99.97%99.97%99.91%23.15%
p50 latency19.4 ms19.2 ms34.2 ms15.2 ms
p95 latency34.8 ms36.7 ms73.0 ms87.5 ms
p99 latency95.5 ms82.4 ms172.7 ms181.6 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.49 blocks0.49 blocks0.38 blocksno cohort
Rate limited0016355
Unsupported0001,113
Samples37,90938,26037,32637,884

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.

TenderlyvsdRPC

+9.1points

  • Latency+9.2
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+46.3points

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

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