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

1h window · 60 minutes observed · generated 2026-08-27 12:27:41 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV Blocker1RPC
Rank1679
Score99.470.469.40.0
StatusExcellentDegradedDegradedPoor
Availability100.00%100.00%99.88%0.00%
p50 latency20.9 ms112.4 ms124.4 ms0.0 ms
p95 latency34.4 ms204.6 ms217.7 ms0.0 ms
p99 latency66.4 ms217.6 ms236.1 ms0.0 ms
Correctness100.00%100.00%100.00%not measured
Head lag0.49 blocks0.23 blocks0.41 blocksno cohort
Rate limited02540276
Unsupported0200
Samples1,6183681,608319

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

+29.0points

  • Latency+29.3
  • Head freshness0.3
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+30.0points

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

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