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:41:40 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMerkleCloudflare
Rank1368
Score99.488.370.248.8
StatusExcellentGoodDegradedPoor
Availability99.95%99.94%100.00%23.17%
p50 latency20.1 ms33.7 ms108.8 ms15.9 ms
p95 latency34.9 ms73.1 ms200.3 ms92.0 ms
p99 latency96.9 ms173.5 ms230.9 ms133.3 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.35 blocks0.48 blocksno cohort
Rate limited0421,45019
Unsupported0018269
Samples9,2299,0822,1699,232

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

  • Latency+11.3
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+29.2points

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

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

TenderlyvsCloudflare

+50.6points

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

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