Skip to content

Providers

MerkleDegraded

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

commercial · rank 9 of 12

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

Measured performance

24h window · 24 hours observed · 1 chain

Composite score

75.0

Rank 9 of 12

7,658 samples

Availability

99.64%

Rate limits and unsupported methods excluded

Latency p95

192.4ms

p50 108.9 · p99 314.1

Correctness

100.00%

278 responses judged

96% of requests were rate limited (6482 of 6761); excluded from availability

12 providers scored against each other.

Score breakdown

How the composite score is composed
ComponentWeightMeasuredScore
Availability40%99.64 %99.6
Latency30%192.40 ms18.6
Correctness20%100.00 %100.0
Head freshness10%0.37 blocks behind95.5

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
Successful2783.63%
Provider failure6,48284.64%
Network failure10.01%
Rate limited6,48284.64%
Unsupported method00.00%
Agent error00.00%
Measurement error89711.71%

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.

  • Requestson Ethereum25 / second

    per account

    “Free up to 25 RPS. Contact us for plans if more RPS is required.”

Quoted, not measured. Read 2026-08-27 from www.merkle.io— a provider can change this without telling anybody, so the date is part of the figure.

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_chainIdon Ethereumsucceeds 100.0%98% refused
  • Throttledeth_getTransactionCounton Ethereumnever answered100% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%98% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_chainIdon Ethereumsucceeds 87.5%95% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%98% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%97% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%95% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%98% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%96% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%96% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%96% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%96% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_syncingon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%97% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%94% refused
  • Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%95% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%94% refused
  • Throttledeth_chainIdon Ethereumsucceeds 100.0%98% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_feeHistoryon Ethereumsucceeds 100.0%94% refused
  • Throttledeth_callon Ethereumsucceeds 100.0%96% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%94% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_gasPriceon Ethereumsucceeds 100.0%97% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_getBalanceon Ethereumsucceeds 100.0%95% refused
  • Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%93% refused
  • Throttledeth_estimateGason Ethereumsucceeds 100.0%94% refused
  • Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%94% refused
  • Throttledeth_blockNumberon Ethereumsucceeds 100.0%95% 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
Virginia30.3 ms60.9 ms3.6%1,935
Coventry116 ms224 ms3.5%1,923
Amsterdam116 ms159 ms4.2%1,905
Frankfurt115 ms220 ms3.3%1,895

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>