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 16:52:36 UTC

Selected providers compared across every measured metric
MetricTenderlydRPCMEV Blocker1RPC
Rank1379
Score99.489.269.50.0
StatusExcellentGoodDegradedPoor
Availability99.98%99.95%99.89%0.00%
p50 latency20.3 ms34.5 ms124.8 ms0.0 ms
p95 latency33.5 ms69.7 ms217.1 ms0.0 ms
p99 latency65.5 ms182.4 ms241.4 ms0.0 ms
Correctness99.99%99.99%100.00%not measured
Head lag0.48 blocks0.37 blocks0.40 blocksno cohort
Rate limited02401,641
Unsupported0000
Samples9,5369,3619,5031,884

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

+10.2points

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

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

TenderlyvsMEV Blocker

+29.9points

  • Latency+30.0
  • Head freshness0.1
  • Availability+0.0
  • Correctness0.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