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 10:51:29 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMerkleCloudflare
Rank1269
Score99.499.277.852.9
StatusExcellentExcellentGoodDegraded
Availability99.97%99.97%100.00%23.13%
p50 latency19.4 ms18.9 ms107.0 ms15.5 ms
p95 latency35.2 ms36.0 ms193.4 ms88.8 ms
p99 latency114.6 ms80.0 ms237.9 ms229.9 ms
Correctness99.99%100.00%100.00%100.00%
Head lag0.49 blocks0.49 blocks0.51 blocksno cohort
Rate limited006,17455
Unsupported00771,133
Samples38,60038,9678,87138,589

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.

TenderlyvsPublicNode

+0.2points

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

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

TenderlyvsMerkle

+21.6points

  • Latency+21.6
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.5points

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

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