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

7d window · 44 hours observed · generated 2026-08-26 16:19:52 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV BlockerCloudflare
Rank5679
Score85.378.477.555.6
StatusGoodGoodGoodDegraded
Availability99.96%99.97%99.87%23.09%
p50 latency20.0 ms106.5 ms118.1 ms15.3 ms
p95 latency123.2 ms196.9 ms208.7 ms89.3 ms
p99 latency987.6 ms245.5 ms233.0 ms255.6 ms
Correctness99.98%100.00%99.98%100.00%
Head lag0.51 blocks0.47 blocks0.39 blocksno cohort
Rate limited011,483041
Unsupported014002,081
Samples70,79316,53070,62270,617

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

+6.9points

  • Latency+7.0
  • Head freshness0.0
  • Availability0.0
  • Correctness0.0

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

TenderlyvsMEV Blocker

+7.8points

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

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

TenderlyvsCloudflare

+29.8points

  • Availability+29.7
  • Head freshness*+9.4
  • Latency7.1
  • Correctness2.2

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