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 13:05:57 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank1368
Score99.487.870.149.4
StatusExcellentGoodDegradedPoor
Availability99.94%99.94%100.00%23.17%
p50 latency20.0 ms33.5 ms108.0 ms15.7 ms
p95 latency35.0 ms74.5 ms200.3 ms88.9 ms
p99 latency103.3 ms177.9 ms231.3 ms128.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.35 blocks0.49 blocksno cohort
Rate limited0401,32419
Unsupported0016239
Samples8,2738,1321,9638,268

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

+11.6points

  • Latency+11.7
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+29.3points

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

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

TenderlyvsCloudflare

+50.0points

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

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