Composite score
25.5
Rank 12 of 12
154,606 samples
Providers
1RPCPoor
Privacy-preserving public RPC relay from Automata Network.
public · rank 12 of 12
Website (opens in a new tab)Documentation (opens in a new tab)
Measured performance
7d window · 7.0 days observed · 2 chains
Availability
8.27%
Rate limits and unsupported methods excluded
Latency p95
6180.3ms
p50 406.8 · p99 8918.9
Correctness
98.41%
5,394 responses judged
54% of requests were rate limited (76383 of 140588); excluded from availability
12 providers scored against each other.
Score breakdown
| Component | Weight | Measured | Score |
|---|---|---|---|
| Availability | 40% | 8.27 % | 8.3 |
| Latency | 30% | 6180.28 ms | 0.0 |
| Correctness | 20% | 98.41 % | 98.4 |
| Head freshness | 0% | not applicable | — |
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 | 5,308 | 3.43% |
| Provider failure | 96,240 | 62.25% |
| Network failure | 39,040 | 25.25% |
| Rate limited | 76,383 | 49.40% |
| Unsupported method | 1 | 0.00% |
| Agent error | 0 | 0.00% |
| Measurement error | 14,018 | 9.07% |
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.
1RPC 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
1RPC 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 1RPC 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, 1RPC 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.
- Outageeth_estimateGason BSCsucceeds 1.5%38% refused
- Outageeth_chainIdon BSCsucceeds 1.8%15% refused
- Outageeth_maxPriorityFeePerGason BSCsucceeds 0.7%33% refused
- Outageeth_blockNumberon BSCsucceeds 1.5%10% refused
- Outageeth_feeHistoryon BSCsucceeds 3.0%39% refused
- Outageeth_gasPriceon BSCsucceeds 1.0%22% refused
- Outageeth_chainIdon BSCsucceeds 2.2%14% refused
- Outageeth_getBlockByNumberon BSCsucceeds 1.5%16% refused
- Outageeth_chainIdon BSCsucceeds 1.3%14% refused
- Outageeth_estimateGason Ethereumsucceeds 0.0%35% refused
- Outageeth_gasPriceon BSCsucceeds 1.7%22% refused
- Outageeth_syncingon BSCsucceeds 1.5%39% refused
- Outageeth_syncingon BSCsucceeds 0.7%36% refused
- Outageeth_chainIdon Ethereumsucceeds 2.1%16% refused
- Outageeth_blockNumberon BSCsucceeds 1.7%10% refused
- Outageeth_blockNumberon Ethereumsucceeds 1.3%10% refused
- Outageeth_estimateGason BSCsucceeds 1.5%38% refused
- Outageeth_getBalanceon BSCsucceeds 1.4%22% refused
- Outageeth_estimateGason BSCsucceeds 1.4%34% refused
- Outageeth_getBalanceon BSCsucceeds 2.1%25% refused
- Outageeth_getBlockByNumberon BSCsucceeds 1.7%15% refused
- Outageeth_callon BSCsucceeds 0.3%23% refused
- Outageeth_blockNumberon BSCsucceeds 2.1%10% refused
- Outageeth_getBalanceon Ethereumsucceeds 1.4%22% refused
- Outageeth_getTransactionCounton BSCsucceeds 1.4%35% refused
- Outageeth_callon BSCsucceeds 1.1%24% refused
- Outageeth_feeHistoryon BSCsucceeds 1.5%39% refused
- Outageeth_callon BSCsucceeds 1.4%23% refused
- Outageeth_feeHistoryon BSCsucceeds 2.1%36% refused
- Outageeth_blockNumberon BSCsucceeds 1.7%9% refused
- Outageeth_getBlockByNumberon BSCsucceeds 2.2%16% refused
- Outageeth_maxPriorityFeePerGason BSCsucceeds 0.7%34% refused
- Outageeth_feeHistoryon BSCsucceeds 2.2%36% refused
- Outageeth_feeHistoryon Ethereumsucceeds 0.0%38% refused
- Outageeth_estimateGason BSCsucceeds 2.2%36% refused
- Outageeth_syncingon BSCsucceeds 1.4%36% refused
- Outageeth_getTransactionCounton BSCsucceeds 0.7%37% refused
- Outageeth_getBalanceon BSCsucceeds 1.0%24% refused
- Outageeth_syncingon BSCsucceeds 1.4%35% refused
- Outageeth_getTransactionCounton BSCsucceeds 0.0%37% refused
- Outageeth_getTransactionCounton BSCsucceeds 1.5%39% refused
- Outageeth_gasPriceon Ethereumsucceeds 0.7%22% refused
- Outageeth_getBlockByNumberon BSCsucceeds 2.2%17% refused
- Outageeth_maxPriorityFeePerGason BSCsucceeds 0.0%35% refused
- Outageeth_callon Ethereumsucceeds 1.4%24% refused
- Outageeth_gasPriceon BSCsucceeds 1.0%20% refused
- Outageeth_callon BSCsucceeds 1.4%25% refused
- Outageeth_getBalanceon BSCsucceeds 2.4%23% refused
- Outageeth_maxPriorityFeePerGason BSCsucceeds 0.7%35% refused
- Outageeth_chainIdon BSCsucceeds 2.0%15% refused
- Outageeth_gasPriceon BSCsucceeds 1.7%23% refused
- Outageeth_getBlockByNumberon Ethereumsucceeds 2.6%17% 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
Amsterdam
Coventry
FrankfurtPercentiles are over successful responses only. A request that timed out is not a latency sample; it is counted against availability instead.
Endpoints under measurement
BSC
EthereumEmbed this
A live badge for 1RPC on BSC, 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/onerpc)HTML
<a href="https://rpcnode.io/providers/onerpc"><img src="https://rpcnode.io/badge/provider/onerpc.svg?chain=bsc" alt="1RPC on RPCNode.IO"></a>