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 00:46:44 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank2369
Score99.091.378.052.4
StatusExcellentExcellentGoodDegraded
Availability99.98%99.92%100.00%23.11%
p50 latency19.8 ms34.1 ms106.9 ms16.1 ms
p95 latency36.9 ms68.6 ms195.9 ms93.3 ms
p99 latency232.8 ms169.0 ms239.8 ms247.3 ms
Correctness99.99%99.99%100.00%100.00%
Head lag0.49 blocks0.37 blocks0.47 blocksno cohort
Rate limited01286,20545
Unsupported00801,137
Samples38,51937,9068,93038,460

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

+7.7points

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

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

TenderlyvsMerkle

+21.0points

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

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

TenderlyvsCloudflare

+46.6points

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

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