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 09:48:04 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCNodeReal1RPC
Rank2349
Score99.388.180.60.0
StatusExcellentGoodGoodPoor
Availability99.95%99.93%100.00%0.00%
p50 latency18.8 ms31.6 ms87.7 ms0.0 ms
p95 latency33.3 ms66.3 ms104.5 ms0.0 ms
p99 latency122.3 ms160.2 ms139.7 ms0.0 ms
Correctness100.00%99.99%100.00%not measured
Head lag0.49 blocks0.35 blocks0.36 blocksno cohort
Rate limited04001,626
Unsupported0000
Samples9,3859,2389,2511,862

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.

TenderlyvsdRPC

+11.2points

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

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

TenderlyvsNodeReal

+18.7points

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

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

Tenderlyvs1RPC

+99.3points

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

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