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

30d window · 2.3 days observed · generated 2026-08-27 04:41:44 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkleMEV BlockerCloudflare
Rank2679
Score94.578.978.055.6
StatusExcellentGoodGoodDegraded
Availability99.96%99.98%99.89%23.11%
p50 latency19.8 ms106.5 ms118.5 ms15.1 ms
p95 latency65.5 ms195.9 ms209.3 ms88.3 ms
p99 latency853.6 ms244.4 ms232.9 ms253.8 ms
Correctness99.99%100.00%99.99%100.00%
Head lag0.51 blocks0.47 blocks0.40 blocksno cohort
Rate limited014,600277
Unsupported018002,668
Samples90,78320,99790,61590,601

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

+15.6points

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

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

TenderlyvsMEV Blocker

+16.4points

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

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

TenderlyvsCloudflare

+38.8points

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

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