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 12:27:09 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank1468
Score99.482.570.049.9
StatusExcellentGoodDegradedPoor
Availability99.93%100.00%100.00%23.20%
p50 latency19.6 ms87.8 ms106.8 ms15.3 ms
p95 latency35.1 ms99.8 ms202.1 ms85.5 ms
p99 latency126.9 ms123.1 ms231.3 ms119.2 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.47 blocks0.34 blocks0.50 blocksno cohort
Rate limited001,42819
Unsupported0017257
Samples8,8358,6782,0928,836

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

+16.9points

  • Latency+17.1
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+29.4points

  • Latency+29.4
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+49.5points

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

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