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 13:06:31 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMerkle1RPC
Rank1269
Score99.496.570.10.0
StatusExcellentExcellentDegradedPoor
Availability99.94%99.98%100.00%0.00%
p50 latency20.0 ms23.4 ms108.0 ms0.0 ms
p95 latency35.0 ms45.3 ms200.3 ms0.0 ms
p99 latency103.2 ms116.1 ms231.3 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.48 blocks0.49 blocks0.49 blocksno cohort
Rate limited001,3241,425
Unsupported00160
Samples8,2848,3551,9651,635

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.

TenderlyvsPublicNode

+2.9points

  • Latency+2.9
  • Head freshness+0.0
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMerkle

+29.3points

  • Latency+29.3
  • Availability0.0
  • Head freshness+0.0
  • Correctness+0.0

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