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 01:50:40 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkle1RPCCloudflare
Rank2689
Score99.078.058.552.4
StatusExcellentGoodDegradedDegraded
Availability99.98%100.00%75.73%23.12%
p50 latency19.8 ms107.0 ms2024.4 ms16.2 ms
p95 latency36.8 ms195.4 ms6590.4 ms93.5 ms
p99 latency218.6 ms239.8 ms9196.2 ms247.1 ms
Correctness99.99%100.00%96.63%100.00%
Head lag0.49 blocks0.46 blocks0.95 blocksno cohort
Rate limited06,2036,62745
Unsupported08101,137
Samples38,6208,9097,94938,555

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.1points

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

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

Tenderlyvs1RPC

+40.5points

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

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

TenderlyvsCloudflare

+46.7points

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

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