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 14:05:47 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodedRPCCloudflare
Rank1239
Score99.498.790.653.2
StatusExcellentExcellentExcellentDegraded
Availability99.98%99.97%99.92%23.15%
p50 latency19.2 ms19.5 ms33.9 ms15.0 ms
p95 latency34.1 ms37.7 ms71.8 ms86.7 ms
p99 latency77.1 ms88.2 ms171.9 ms217.1 ms
Correctness100.00%100.00%99.99%100.00%
Head lag0.49 blocks0.49 blocks0.37 blocksno cohort
Rate limited0014755
Unsupported0001,098
Samples37,37537,73636,80837,369

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

  • Latency+0.7
  • Availability+0.0
  • Head freshness0.0
  • Correctness+0.0

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

TenderlyvsdRPC

+8.8points

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

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

TenderlyvsCloudflare

+46.2points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency+9.3
  • 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