Skip to content

Providers

MerkleGood

Ethereum RPC and transaction services. The public endpoint implements a reduced method set.

commercial · rank 8 of 12

Website (opens in a new tab)Documentation (opens in a new tab)

Measured performance

30d window · 3.5 days observed · 1 chain

Composite score

78.3

Rank 8 of 12

31,987 samples

Availability

99.99%

Rate limits and unsupported methods excluded

Latency p95

195.3ms

p50 106.8 · p99 244.8

Correctness

100.00%

7,076 responses judged

75% of requests were rate limited (22117 of 29466); excluded from availability

12 providers scored against each other.

Score breakdown

How the composite score is composed
ComponentWeightMeasuredScore
Availability40%99.99 %100.0
Latency30%195.34 ms29.5
Correctness20%100.00 %100.0
Head freshness10%0.49 blocks behind94.0

Outcome breakdown

Failures are classified rather than collapsed into one count. Our own failures are shown for transparency but are never counted against the provider.

Request outcomes and how each is treated
OutcomeCountShare
Successful7,07622.12%
Provider failure22,38969.99%
Network failure10.00%
Rate limited22,11769.14%
Unsupported method2720.85%
Agent error00.00%
Measurement error2,5217.88%

What it says it permits

The only figures on this site that are not measurements. A limit is a claim the operator makes, so it is quoted with the page it came from and the day it was read — never inferred from a refused request, which would put a number against a company that never stated it.

Merkle does not publish a numeric limit that could be found in its own documentation. Several public endpoints state only that a request may be refused — which is worth knowing before depending on one, and is why this says so rather than showing nothing.

What it promises about staying up

The status page judges every provider against an objective this site publishes. That is not an SLA, and a provider that misses it has not broken a promise — so what it actually promised, where it promised anything, belongs here in its own words. The objective

Merkle does not publish an availability commitment that could be found in its own documentation. That is the common case for a public endpoint and is worth knowing before depending on one: the availability figures on this site are measurements against a bar this platform set, not against anything Merkle agreed to.

Reliability record

An availability percentage has no shape. This is the shape: what departed from this provider’s own normal behaviour, and what its normal behaviour already is. How an incident is decided

Departures from normal · last 30 days

None. Across the last 30 days, Merkle did not depart from its own usual behaviour on any measured call for long enough to count as an incident.

Persistent conditions

Calls that fail, or are refused, at about the same rate every day. These are not events — they are what this provider does — and none of them will be different tomorrow.

  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%78% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%78% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%80% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%80% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%81% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%78% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%79% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%74% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%80% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%74% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%78% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%77% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%79% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%81% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%76% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%77% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%81% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%73% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%76% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%70% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%77% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%73% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%72% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%73% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%74% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%76% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%75% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%73% refused

From each region

The same measurements, grouped by the vantage point they were taken from. Latency is a property of a network path, so a provider fast from one region is not necessarily fast from another — and the composite score above is an average across whichever regions are reporting.

4 regions

Merkle broken out by region
RegionMedianp95SuccessSamples
Frankfurt114 ms209 ms21.5%7,911
Amsterdam109 ms197 ms21.5%7,914
Coventry107 ms215 ms22.4%7,995
Virginia20.9 ms43.5 ms23.0%8,167

Percentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.

Endpoints under measurement

1 endpoint

Endpoints measured for this provider
ChainTransportURLStatus
Ethereumhttp_jsonrpchttps://eth.merkle.io

Embed this

A live badge for Merkle on Ethereum, free to use. It renders from the current measurement each time it loads, so it cannot be frozen at a good day — which is what makes it worth putting in a README. Every badge and parameter

Merkle score badgescore

The composite score, coloured by band.

Markdown

[![Merkle on RPCNode.IO](https://rpcnode.io/badge/provider/merkle.svg?chain=ethereum)](https://rpcnode.io/providers/merkle)

HTML

<a href="https://rpcnode.io/providers/merkle"><img src="https://rpcnode.io/badge/provider/merkle.svg?chain=ethereum" alt="Merkle on RPCNode.IO"></a>