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 09:46:06 UTC

Selected providers compared across every measured metric
MetricTenderlydRPC1RPCCloudflare
Rank1389
Score99.490.658.252.9
StatusExcellentExcellentDegradedDegraded
Availability99.97%99.91%74.93%23.12%
p50 latency19.3 ms34.2 ms2024.4 ms15.6 ms
p95 latency35.3 ms71.5 ms6590.4 ms89.3 ms
p99 latency125.3 ms176.4 ms9196.2 ms239.5 ms
Correctness99.99%99.99%96.63%100.00%
Head lag0.49 blocks0.38 blocks0.95 blocksno cohort
Rate limited01576,60855
Unsupported0001,132
Samples38,46437,8747,92738,440

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.

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.

Tenderlyvs1RPC

+41.2points

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

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

TenderlyvsCloudflare

+46.5points

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

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