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 14:40:39 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank1368
Score99.488.070.548.2
StatusExcellentGoodDegradedPoor
Availability99.95%99.94%100.00%23.18%
p50 latency20.1 ms34.1 ms108.1 ms16.4 ms
p95 latency34.4 ms75.1 ms197.2 ms95.4 ms
p99 latency78.0 ms183.5 ms231.3 ms141.5 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.36 blocks0.44 blocksno cohort
Rate limited0401,44412
Unsupported0016267
Samples9,2099,0512,1439,205

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

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

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

TenderlyvsMerkle

+28.9points

  • Latency+29.0
  • Head freshness0.0
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+51.2points

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

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