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 10:35:38 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeMerkle1RPC
Rank1269
Score99.498.970.00.0
StatusExcellentExcellentDegradedPoor
Availability99.93%99.98%100.00%0.00%
p50 latency19.2 ms20.2 ms106.2 ms0.0 ms
p95 latency34.2 ms35.9 ms196.0 ms0.0 ms
p99 latency124.3 ms88.8 ms228.8 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.48 blocks0.49 blocks0.60 blocksno cohort
Rate limited001,4351,558
Unsupported00180
Samples9,0479,1212,1051,784

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

+0.5points

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

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

TenderlyvsMerkle

+29.4points

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

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