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 13:43:39 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank1369
Score99.490.577.853.0
StatusExcellentExcellentGoodDegraded
Availability99.97%99.92%100.00%23.14%
p50 latency19.3 ms34.1 ms107.2 ms15.2 ms
p95 latency34.4 ms72.1 ms194.0 ms88.1 ms
p99 latency83.7 ms171.6 ms235.0 ms222.7 ms
Correctness100.00%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.50 blocksno cohort
Rate limited01586,07255
Unsupported00721,128
Samples38,39737,8108,78838,382

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

+8.9points

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

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

TenderlyvsMerkle

+21.6points

  • Latency+21.6
  • Head freshness+0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsCloudflare

+46.4points

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

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