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 18:38:29 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkle1RPCCloudflare
Rank1689
Score99.477.957.853.5
StatusExcellentGoodDegradedDegraded
Availability99.98%100.00%73.97%23.15%
p50 latency19.3 ms107.5 ms2024.4 ms15.1 ms
p95 latency33.8 ms193.7 ms6590.4 ms86.7 ms
p99 latency75.4 ms235.0 ms9196.2 ms246.7 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.48 blocks0.53 blocks0.95 blocksno cohort
Rate limited06,0446,57436
Unsupported07501,127
Samples38,2698,7677,89238,312

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.4
  • Head freshness+0.1
  • Availability0.0
  • Correctness0.0

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

Tenderlyvs1RPC

+41.6points

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

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

TenderlyvsCloudflare

+45.9points

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

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