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.4 days observed · generated 2026-08-27 07:25:44 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank2469
Score95.088.278.755.4
StatusExcellentGoodGoodDegraded
Availability99.97%99.80%99.98%23.10%
p50 latency19.8 ms87.4 ms106.5 ms15.0 ms
p95 latency61.1 ms100.1 ms195.5 ms87.3 ms
p99 latency825.3 ms125.9 ms244.4 ms252.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.35 blocks0.48 blocksno cohort
Rate limited0015,31777
Unsupported001852,801
Samples95,21293,60722,01295,027

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

+6.8points

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

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

TenderlyvsMerkle

+16.2points

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

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

TenderlyvsCloudflare

+39.6points

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

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