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.9 days observed · generated 2026-08-27 19:10:44 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank2369
Score96.992.078.454.2
StatusExcellentExcellentGoodDegraded
Availability99.96%99.94%99.98%23.11%
p50 latency19.8 ms33.9 ms107.0 ms15.3 ms
p95 latency49.4 ms71.9 ms195.7 ms89.3 ms
p99 latency729.4 ms170.5 ms242.7 ms253.0 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.50 blocks0.36 blocks0.48 blocksno cohort
Rate limited066118,33596
Unsupported002243,360
Samples114,261112,37626,482114,073

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

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

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

TenderlyvsMerkle

+18.5points

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

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

TenderlyvsCloudflare

+42.7points

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

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