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

30d window · 2.8 days observed · generated 2026-08-27 15:42:52 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank2369
Score96.492.278.554.6
StatusExcellentExcellentGoodDegraded
Availability99.96%99.93%99.98%23.11%
p50 latency19.8 ms33.8 ms106.7 ms15.2 ms
p95 latency52.2 ms71.8 ms196.0 ms88.0 ms
p99 latency762.2 ms169.3 ms243.5 ms250.8 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.36 blocks0.48 blocksno cohort
Rate limited064517,47396
Unsupported002133,193
Samples108,640106,84325,168108,465

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.

TenderlyvsdRPC

+4.2points

  • Latency+4.3
  • Head freshness0.2
  • Availability+0.0
  • Correctness0.0

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

TenderlyvsMerkle

+17.9points

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

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

TenderlyvsCloudflare

+41.7points

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

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