Composite score
78.2
Rank 8 of 12
8,892 samples
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
24h window · 24 hours observed · 1 chain
Availability
100.00%
Rate limits and unsupported methods excluded
Latency p95
192.3ms
p50 107.3 · p99 231.9
Correctness
100.00%
2,022 responses judged
74% of requests were rate limited (6101 of 8196); excluded from availability
12 providers scored against each other.
Score breakdown
| Component | Weight | Measured | Score |
|---|---|---|---|
| Availability | 40% | 100.00 % | 100.0 |
| Latency | 30% | 192.26 ms | 29.6 |
| Correctness | 20% | 100.00 % | 100.0 |
| Head freshness | 10% | 0.53 blocks behind | 93.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.
| Outcome | Count | Share |
|---|---|---|
| Successful | 2,022 | 22.74% |
| Provider failure | 6,174 | 69.43% |
| Network failure | 0 | 0.00% |
| Rate limited | 6,101 | 68.61% |
| Unsupported method | 73 | 0.82% |
| Agent error | 0 | 0.00% |
| Measurement error | 696 | 7.83% |
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_syncingon Ethereumsucceeds 100.0%78% refused
- Throttledeth_blockNumberon Ethereumsucceeds 100.0%82% refused
- Throttledeth_gasPriceon Ethereumsucceeds 100.0%76% refused
- Throttledeth_callon Ethereumsucceeds 100.0%78% refused
- Throttledeth_syncingon Ethereumsucceeds 100.0%81% refused
- Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%76% refused
- Throttledeth_estimateGason Ethereumsucceeds 100.0%77% refused
- Throttledeth_getBalanceon Ethereumsucceeds 100.0%78% refused
- Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%79% refused
- Throttledeth_getBalanceon Ethereumsucceeds 100.0%78% refused
- Throttledeth_estimateGason Ethereumsucceeds 100.0%80% refused
- Throttledeth_chainIdon Ethereumsucceeds 100.0%77% refused
- Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%79% refused
- Throttledeth_blockNumberon Ethereumsucceeds 100.0%75% refused
- Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%74% refused
- Throttledeth_gasPriceon Ethereumsucceeds 100.0%72% refused
- Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%75% refused
- Throttledeth_blockNumberon Ethereumsucceeds 100.0%80% refused
- Throttledeth_gasPriceon Ethereumsucceeds 100.0%76% refused
- Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%76% refused
- Throttledeth_estimateGason Ethereumsucceeds 100.0%74% refused
- Throttledeth_chainIdon Ethereumsucceeds 100.0%77% refused
- Throttledeth_callon Ethereumsucceeds 100.0%77% refused
- Throttledeth_blockNumberon Ethereumsucceeds 100.0%80% refused
- Throttledeth_feeHistoryon Ethereumsucceeds 100.0%78% refused
- Throttledeth_feeHistoryon Ethereumsucceeds 100.0%75% refused
- Throttledeth_syncingon Ethereumsucceeds 100.0%73% refused
- Throttledeth_getBlockByNumberon Ethereumsucceeds 100.0%74% refused
- Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%75% refused
- Throttledeth_callon Ethereumsucceeds 100.0%73% refused
- Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%76% refused
- Throttledeth_getBalanceon Ethereumsucceeds 100.0%74% refused
- Throttledeth_getBalanceon Ethereumsucceeds 100.0%70% refused
- Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%75% refused
- Throttledeth_chainIdon Ethereumsucceeds 100.0%78% refused
- Throttledeth_getTransactionCounton Ethereumsucceeds 100.0%77% refused
- Throttledeth_callon Ethereumsucceeds 100.0%77% refused
- Throttledeth_estimateGason Ethereumsucceeds 100.0%73% refused
- Throttledeth_feeHistoryon Ethereumsucceeds 100.0%72% refused
- Throttledeth_gasPriceon Ethereumsucceeds 100.0%76% refused
- Throttledeth_maxPriorityFeePerGason Ethereumsucceeds 100.0%73% refused
- Throttledeth_chainIdon Ethereumsucceeds 100.0%73% refused
- Throttledeth_syncingon Ethereumsucceeds 100.0%73% 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.
Virginia
Frankfurt
Coventry
AmsterdamPercentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.
Endpoints under measurement
EthereumEmbed 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
scoreThe composite score, coloured by band.
Markdown
[](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>