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 06:26:06 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMerkle1RPC
Rank2469
Score98.980.870.10.0
StatusExcellentGoodDegradedPoor
Availability100.00%99.99%100.00%0.00%
p50 latency18.7 ms87.1 ms104.8 ms0.0 ms
p95 latency32.4 ms100.7 ms193.2 ms0.0 ms
p99 latency65.2 ms132.5 ms283.4 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.47 blocks0.35 blocks0.51 blocksno cohort
Rate limited001,3911,514
Unsupported00180
Samples8,7958,6751,9621,736

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

+18.1points

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

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

TenderlyvsMerkle

+28.8points

  • Latency+28.7
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

Tenderlyvs1RPC

+98.9points

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

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