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 08:35:03 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV Blocker1RPC
Rank2679
Score98.870.069.50.0
StatusExcellentDegradedDegradedPoor
Availability99.98%100.00%99.90%0.00%
p50 latency18.4 ms104.7 ms119.2 ms0.0 ms
p95 latency32.2 ms192.8 ms207.8 ms0.0 ms
p99 latency82.4 ms251.0 ms226.0 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.48 blocks0.62 blocks0.42 blocksno cohort
Rate limited01,41711,562
Unsupported01500
Samples9,0312,0269,0261,785

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.

TenderlyvsMerkle

+28.7points

  • Latency+28.6
  • Head freshness+0.2
  • Availability0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+29.3points

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

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

Tenderlyvs1RPC

+98.8points

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

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