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

7d window · 2.3 days observed · generated 2026-08-27 02:57:28 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank2469
Score94.088.979.155.9
StatusExcellentGoodGoodDegraded
Availability99.96%99.79%99.98%23.10%
p50 latency19.9 ms87.3 ms106.6 ms15.2 ms
p95 latency69.4 ms99.9 ms196.0 ms88.9 ms
p99 latency868.9 ms123.5 ms243.1 ms254.4 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.51 blocks0.35 blocks0.46 blocksno cohort
Rate limited0014,18777
Unsupported001742,585
Samples87,97786,46820,39987,782

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

+5.1points

  • Latency+5.3
  • Head freshness0.2
  • Availability+0.1
  • Correctness0.0

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

TenderlyvsMerkle

+15.0points

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

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

TenderlyvsCloudflare

+38.1points

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

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