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 07:27:01 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV BlockerCloudflare
Rank2678
Score98.570.069.551.3
StatusExcellentDegradedDegradedDegraded
Availability100.00%100.00%99.92%23.11%
p50 latency18.4 ms105.1 ms118.7 ms12.9 ms
p95 latency32.0 ms193.2 ms207.0 ms69.4 ms
p99 latency68.5 ms268.8 ms224.4 ms130.6 ms
Correctness100.00%100.00%100.00%100.00%
Head lag0.48 blocks0.59 blocks0.40 blocksno cohort
Rate limited01,39400
Unsupported0150263
Samples8,8181,9698,8028,832

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.5points

  • Latency+28.4
  • Head freshness+0.1
  • Availability+0.0
  • Correctness+0.0

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

TenderlyvsMEV Blocker

+29.1points

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

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

TenderlyvsCloudflare

+47.3points

  • Availability+29.7
  • Latency+10.4
  • Head freshness*+9.4
  • Correctness2.2

The parts add to +47.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