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 01:54:23 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank2469
Score99.086.678.052.4
StatusExcellentGoodGoodDegraded
Availability99.98%100.00%100.00%23.11%
p50 latency19.8 ms87.3 ms107.0 ms16.1 ms
p95 latency36.8 ms100.0 ms195.2 ms93.3 ms
p99 latency217.6 ms124.4 ms239.8 ms247.0 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.34 blocks0.46 blocksno cohort
Rate limited006,21945
Unsupported00821,140
Samples38,72538,0898,94138,655

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.

TenderlyvsNodeReal

+12.5points

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

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

TenderlyvsMerkle

+21.0points

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

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

TenderlyvsCloudflare

+46.7points

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

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