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 00:47:05 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkle1RPCCloudflare
Rank1689
Score99.477.958.553.8
StatusExcellentGoodDegradedDegraded
Availability99.99%100.00%75.73%23.17%
p50 latency19.0 ms107.6 ms2024.4 ms15.1 ms
p95 latency35.0 ms196.0 ms6590.4 ms84.6 ms
p99 latency69.3 ms230.7 ms9196.2 ms259.8 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.50 blocks0.50 blocks0.95 blocksno cohort
Rate limited01,4451,57317
Unsupported0160275
Samples9,3402,0772,1669,369

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.

TenderlyvsMerkle

+21.5points

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

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

Tenderlyvs1RPC

+40.9points

  • Latency+30.0
  • Availability+9.7
  • Correctness+0.7
  • Head freshness+0.5

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

TenderlyvsCloudflare

+45.6points

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

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