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:41:40 UTC

Selected providers compared across every measured metric
MetricTenderlyNodeRealMEV Blocker1RPC
Rank1479
Score99.482.869.50.0
StatusExcellentGoodDegradedPoor
Availability99.95%100.00%99.90%0.00%
p50 latency20.1 ms87.8 ms123.3 ms0.0 ms
p95 latency34.9 ms99.6 ms213.7 ms0.0 ms
p99 latency96.9 ms123.7 ms235.3 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.34 blocks0.39 blocksno cohort
Rate limited0011,590
Unsupported0000
Samples9,2299,0739,2051,824

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.

TenderlyvsNodeReal

+16.6points

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

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

TenderlyvsMEV Blocker

+29.9points

  • Latency+30.0
  • Head freshness0.1
  • Availability+0.0
  • Correctness+0.0

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