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:04:34 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkle1RPC
Rank1469
Score99.483.269.90.0
StatusExcellentGoodDegradedPoor
Availability100.00%100.00%100.00%0.00%
p50 latency20.9 ms86.7 ms112.4 ms0.0 ms
p95 latency33.8 ms98.3 ms209.2 ms0.0 ms
p99 latency55.3 ms125.2 ms407.4 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.47 blocks0.34 blocks0.38 blocksno cohort
Rate limited00248276
Unsupported0010
Samples1,6081,575349318

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

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

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

TenderlyvsMerkle

+29.5points

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

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

Tenderlyvs1RPC

+99.4points

  • Availability+40.0
  • Latency*+30.0
  • Correctness*+20.0
  • Head freshness*+9.4

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