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 11:48:20 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeRealCloudflare
Rank1249
Score99.499.186.453.1
StatusExcellentExcellentGoodDegraded
Availability99.97%99.97%100.00%23.14%
p50 latency19.4 ms19.1 ms87.2 ms15.4 ms
p95 latency35.1 ms36.4 ms100.1 ms87.8 ms
p99 latency105.3 ms81.7 ms128.2 ms187.0 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.49 blocks0.34 blocksno cohort
Rate limited00055
Unsupported0001,133
Samples38,52238,88937,92738,497

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

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

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

TenderlyvsNodeReal

+12.9points

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

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