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-26 22:28:43 UTC

Selected providers compared across every measured metric
MetricTenderlyPublicNodeNodeReal1RPC
Rank1249
Score99.498.482.20.0
StatusExcellentExcellentGoodPoor
Availability99.99%99.92%100.00%0.00%
p50 latency19.4 ms18.5 ms87.3 ms0.0 ms
p95 latency35.5 ms38.8 ms99.5 ms0.0 ms
p99 latency68.9 ms88.7 ms125.5 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.51 blocks0.48 blocks0.33 blocksno cohort
Rate limited0001,527
Unsupported0000
Samples8,8568,9558,6991,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.

TenderlyvsPublicNode

+1.0points

  • Latency+1.0
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsNodeReal

+17.1points

  • Latency+17.3
  • Head freshness0.2
  • Availability0.0
  • Correctness+0.0

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