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:56:35 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank1468
Score99.482.970.848.0
StatusExcellentGoodDegradedPoor
Availability99.95%100.00%100.00%23.18%
p50 latency20.1 ms87.7 ms108.2 ms16.5 ms
p95 latency34.5 ms99.4 ms191.4 ms95.9 ms
p99 latency77.6 ms126.6 ms231.3 ms157.4 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.33 blocks0.46 blocksno cohort
Rate limited001,49812
Unsupported0018279
Samples9,6419,4612,2359,636

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.

TenderlyvsNodeReal

+16.5points

  • Latency+16.7
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+28.6points

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

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

TenderlyvsCloudflare

+51.4points

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

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