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 02:08:24 UTC

Selected providers compared across every measured metric
MetricTenderlyMerkle1RPCCloudflare
Rank1689
Score99.477.858.755.3
StatusExcellentGoodDegradedDegraded
Availability100.00%100.00%76.33%23.16%
p50 latency19.1 ms105.7 ms2024.4 ms12.8 ms
p95 latency32.3 ms193.1 ms6590.4 ms72.3 ms
p99 latency69.5 ms229.0 ms9196.2 ms263.3 ms
Correctness100.00%100.00%96.63%100.00%
Head lag0.49 blocks0.45 blocks0.95 blocksno cohort
Rate limited01,3021,3986
Unsupported0180242
Samples8,3081,8501,9628,326

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

+21.7points

  • Latency+21.7
  • Head freshness0.0
  • Availability+0.0
  • Correctness+0.0

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

Tenderlyvs1RPC

+40.7points

  • Latency+30.0
  • Availability+9.5
  • Correctness+0.7
  • Head freshness+0.5

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

TenderlyvsCloudflare

+44.1points

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

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