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 08:29:51 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1249
Score99.499.486.452.6
StatusExcellentExcellentGoodDegraded
Availability99.97%99.98%100.00%23.14%
p50 latency19.4 ms18.4 ms87.2 ms15.7 ms
p95 latency35.3 ms35.4 ms100.3 ms90.8 ms
p99 latency125.7 ms74.2 ms128.7 ms241.3 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.48 blocks0.34 blocksno cohort
Rate limited00043
Unsupported0001,122
Samples38,02638,36937,45437,998

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

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

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

TenderlyvsNodeReal

+13.0points

  • Latency+13.2
  • Head freshness0.2
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.8points

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

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