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 15:27:08 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkle1RPC
Rank1469
Score99.482.970.90.0
StatusExcellentGoodDegradedPoor
Availability99.98%100.00%100.00%0.00%
p50 latency20.2 ms87.6 ms110.0 ms0.0 ms
p95 latency33.8 ms99.3 ms191.4 ms0.0 ms
p99 latency64.8 ms126.3 ms290.6 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.33 blocks0.45 blocksno cohort
Rate limited001,3871,524
Unsupported00150
Samples8,8508,6822,0561,750

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

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

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