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

1h window · 60 minutes observed · generated 2026-08-27 12:27:41 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkleCloudflare
Rank1468
Score99.483.370.447.9
StatusExcellentGoodDegradedPoor
Availability100.00%100.00%100.00%23.28%
p50 latency20.9 ms87.3 ms112.4 ms17.1 ms
p95 latency34.4 ms98.8 ms204.6 ms97.9 ms
p99 latency66.4 ms120.8 ms217.6 ms140.9 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.49 blocks0.32 blocks0.23 blocksno cohort
Rate limited002540
Unsupported00247
Samples1,6181,5783681,611

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

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

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

TenderlyvsMerkle

+29.0points

  • Latency+29.3
  • Head freshness0.3
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsCloudflare

+51.5points

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

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