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 17:32:41 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodedRPC1RPC
Rank1239
Score99.494.989.60.0
StatusExcellentExcellentGoodPoor
Availability99.98%100.00%99.95%0.00%
p50 latency20.3 ms25.5 ms34.6 ms0.0 ms
p95 latency33.4 ms50.5 ms68.5 ms0.0 ms
p99 latency65.9 ms113.5 ms176.3 ms0.0 ms
Correctness99.99%100.00%99.99%not measured
Head lag0.49 blocks0.48 blocks0.36 blocksno cohort
Rate limited00231,553
Unsupported0000
Samples8,9919,0538,8321,782

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

+4.5points

  • Latency+4.5
  • Availability0.0
  • Correctness0.0
  • Head freshness0.0

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

TenderlyvsdRPC

+9.8points

  • Latency+10.0
  • Head freshness0.2
  • Availability+0.0
  • Correctness+0.0

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