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

6h window · 6.0 hours observed · generated 2026-08-27 03:57:54 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank1469
Score99.486.677.756.2
StatusExcellentGoodGoodDegraded
Availability100.00%99.99%100.00%23.21%
p50 latency18.9 ms86.8 ms105.0 ms12.6 ms
p95 latency32.6 ms98.7 ms205.0 ms68.6 ms
p99 latency69.6 ms117.4 ms263.5 ms247.4 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.48 blocks0.33 blocks0.44 blocksno cohort
Rate limited001,5296
Unsupported0022282
Samples9,6369,5272,1569,669

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

  • Latency+13.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+21.7points

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

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

TenderlyvsCloudflare

+43.2points

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

The parts add to +43.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