RPCsUpdated

Arbitrum RPC endpoints: free public URLs and private API-key providers by latency

HTTP round-trip latency for eth_getBlockByNumber against every free, no-key public Arbitrum RPC endpoint (probed every 60 seconds) and, under the Access selector (Private), against the API-key endpoints of Alchemy, Chainstack, GetBlock, Quicknode and Dwellir (every 120 seconds), from 3 regions. The two cohorts are ranked separately, never against each other.

TL;DR. As of , dRPC has the lowest median latency of the 7 free public Arbitrum RPC endpoints measured, 43 ms (p50, 24h, 3 regions). Source: OpenChainBench, https://openchainbench.com/benchmarks/arbitrum-rpc. Chain ID 42161. 7 public endpoints, no key: arbitrum.drpc.org, arbitrum-one-rpc.publicnode.com, gateway.tenderly.co, api.blockvectra.com, arb1.arbitrum.io, arb-pokt.nodies.app, arbitrum.meowrpc.com. Full URLs with their 24h median are listed below; Alchemy, Chainstack, GetBlock, Quicknode, Dwellir, BlockMachine (private, API key) are ranked apart under the Private tab.

Companion page

Comparing free RPC endpoints across every chain we measure? Open the cross-chain RPC matrix →

Arbitrum is the second-largest cohort in the cluster: 7 no-key providers including the Arbitrum Foundation's own `arb1.arbitrum.io/rpc`, and one of the few chains where MeowRPC still competes on a free tier (Lava left on 2026-10-19: its public hosts answer 410 Gone). Foundation endpoints are documented best-effort, and our data shows what that means in practice: a median of 127 ms with a p99 of 186 ms over the last 24 hours. Every provider answers the identical `eth_getBlockByNumber` probe every 60 seconds from us-east, eu-west and Singapore.

Methodology

Arbitrum: 7 free public RPC endpoints answering `eth_getBlockByNumber` every 60 seconds from us-east, eu-west and Singapore, ranked by 24h median. dRPC leads at 43 ms; the chain-official endpoint measures 127 ms. The same page carries the private cohort (API key), Alchemy, Chainstack, GetBlock, Quicknode and Dwellir on their keyed Arbitrum endpoints every 120 seconds: switch the Access selector; Quicknode leads it at 4 ms. We measure the round-trip latency of a single, identical RPC call (`eth_getBlockByNumber`) against every no-key public Arbitrum endpoint that sustains continuous probing, 7 providers, every 60 seconds, from us-east, eu-west and Singapore. The harness also classifies every response (ok / http_err / jsonrpc_err / stale / timeout) and audits archive depth every 5 minutes, so the leaderboard rewards sustained, honest availability rather than a fast error message. The cross-chain view lives on the parent rpc-capabilities benchmark; this page is the Arbitrum-scoped answer with per-region breakdowns as a first-class dimension.

  • Cadence: every 60 seconds per provider, from each of 3 probe regions (us-east Virginia, eu-west Amsterdam, sgp Singapore). Headline p50/p90/p99 aggregate across all 3 regions via Prometheus `avg(quantile_over_time(...))`; per-region breakdowns are first-class on this page via the region tabs.
  • Payload: `{"jsonrpc":"2.0","id":<rotating>,"method":"eth_getBlockByNumber","params":["latest",false]}`. Plain HTTP POST, identical for every endpoint, no API key in any request. The request id rotates, but that does not guarantee a cache miss: many caches normalise `id` away. Measured 2026-10-08, fixed and rotating ids answer within 2 to 4 percent of each other.
  • Latency measurement, call-result classification (`ok`, `http_err`, `jsonrpc_err`, `stale`, `timeout`) and the archive-depth audit follow the cluster method documented on [rpc-capabilities](openchainbench.com/benchmarks/rpc-capabilities#methodology); this page is the Arbitrum-scoped view of the same harness, with the same exclusion rules.
  • Chain scope: every query on this page is pinned to chain="arbitrum". Provider coverage: 7 no-key public-read endpoints live today, each listed with its URL in the endpoints table on this page. Exclusions follow the cluster-wide rules documented on the parent benchmark.
  • Private cohort (Access selector, Private): Alchemy, Chainstack, GetBlock, Quicknode, Dwellir and BlockMachine probed on their keyed Arbitrum endpoints every 120 seconds from the same 3 regions, same call (eth_getBlockByNumber, rotating id), same ok / http_err / jsonrpc_err / stale / timeout classification.
  • Keys live in the probe environment, never in the repo. Plan tiers, disclosed: Alchemy: an Enterprise trial key, measured on that tier since 10 November 2026, not a reader's tier; Alchemy states free and paid keys share one routing; Chainstack: a Global Node on the Growth plan; Quicknode: an endpoint on a Build plan ($49 per month), shared fleet; GetBlock: an endpoint on the Enterprise plan, shared by the three probe regions. Chainstack, GetBlock and Quicknode provided their endpoints.
  • Dwellir plan tier, disclosed: a Developer plan key ($49 per month, 25 million API responses, 100 responses per second; 1 RPC response = 1 API credit, no compute units). Shared nodes, the same product a reader buys. Dwellir publishes no Solana endpoint, so it is absent from that page rather than shown as unavailable.
  • GetBlock regional pairing: each probe region uses GetBlock's nearest endpoint, us-east to New York, eu-west to Frankfurt, sgp to Singapore. Alchemy, Chainstack and Quicknode publish one routed entry point per chain instead, which in the general case does land a probe on a nearby node. Some of any gap between the two arrangements is deployment topology rather than node speed, and a deployment in one of these regions would see the same benefit GetBlock's endpoint gives the probe.
  • Two cohorts, two rankings: the public endpoints are shared, rate-limited gateways probed every 60 seconds; the keyed endpoints are metered or dedicated and probed every 120 seconds. The selector switches the whole page (ranking, chart, region tabs, badges, citation) between them. No figure on this page compares a public endpoint with a keyed one.

Results: 7 free public Arbitrum RPC endpoints ranked by p50 latency (24h, 3 regions)

Arbitrum RPC endpoints: free public URLs and private API-key providers by latency: RPC latency per provider (p50, 24h).
â„–Providersp50p90p99Success
1dRPCDecentralized RPC mesh, consensus-checked43 ms53 ms103 ms100.00% (n=4320)
2PublicNodeAllnodes-operated, 70+ chains, archive on most77 ms102 ms259 ms100.00% (n=4319)
3TenderlyMulti-chain public gateway, 9 chains, no key104 ms111 ms116 ms100.00% (n=4320)
4BlockVectraBlockVectra keyless public Arbitrum One endpoint (3 req/s per IP, 1,000-block history window)113 ms187 ms568 ms89.44% (n=4319)
5ArbitrumArbitrum Foundation public RPC, Arbitrum One only127 ms136 ms186 ms100.00% (n=4321)
6NodiesPOKT Network's decentralized public RPC successor, 7+ chains139 ms157 ms193 ms100.00% (n=4319)
7MeowRPCFree public RPC, no registration195 ms274 ms338 ms100.00% (n=4318)

Public Arbitrum RPC endpoints measured

Chain ID 42161, currency ETH. The 7 no-key endpoints answering our probes today, with their current 24h median. Paste one into a wallet or a client as is: no signup, no key. Alchemy, Chainstack, GetBlock, Quicknode, Dwellir and BlockMachine, private endpoints that need an API key, are ranked separately under the Private tab; keyed URLs are never listed.

  • dRPC logodRPChttps://arbitrum.drpc.org43 ms100.0%
  • PublicNode logoPublicNodehttps://arbitrum-one-rpc.publicnode.com77 ms100.0%
  • Tenderly logoTenderlyhttps://gateway.tenderly.co/public/arbitrum104 ms100.0%
  • BlockVectra logoBlockVectrahttps://api.blockvectra.com/v1/arb_mainnet/public113 ms89.4%
  • Arbitrum logoArbitrumhttps://arb1.arbitrum.io/rpc127 ms100.0%
  • Nodies logoNodieshttps://arb-pokt.nodies.app139 ms100.0%
  • MeowRPC logoMeowRPChttps://arbitrum.meowrpc.com195 ms100.0%

Median round-trip and success rate over the last 24 hours across the probe regions; the ranked table above carries p90, p99 and the per-region split.

Not listed on Arbitrum

  • Ankr: public endpoint requires an API key
  • NodeReal: requires an API key
  • 1RPC: delisted for reliability: under 13 % success at one probe per minute (since 2026-07-09)
  • gateway.fm: 29 requests per IP budget, too small for continuous probing
  • LlamaRPC: Cloudflare 521 from the probe regions
  • BlockPI: Cloudflare 521 from the probe regions
  • OmniaTech: Cloudflare 521 from the probe regions
  • Alchemy demo: rate-limited public demo endpoint; Alchemy's keyed endpoint is in the private cohort on this page

Frequently asked

Which Arbitrum RPCs work without an API key?

The 7 providers on this page are listed with their URLs in the endpoints table above. Every (provider, chain) pair was live-verified no-key before inclusion, and anything that key-gates, region-blocks or rate-limits below our 60-second cadence is excluded rather than listed with an asterisk.

Should I use the official Arbitrum Foundation RPC in production?

The Foundation documents `arb1.arbitrum.io/rpc` as best-effort and rate-limited, intended for development. Our continuous measurement confirms the profile: a p50 of 127 ms against 43 ms for the leader, with a p99 of 186 ms. Read the p99 column against the leader's before choosing it as a primary for a read-heavy path.

Which Arbitrum RPC provider is fastest with an API key?

Per the live data: Quicknode at 4 ms (eth_getBlockByNumber p50 over 24h, averaged across us-east, eu-west and Singapore); Alchemy measures 9 ms, Chainstack 20 ms and Quicknode 4 ms; GetBlock measures 8 ms. On the free cohort dRPC leads at 43 ms, measured on the same call from the same three regions; the two cohorts are never ranked in one table (shared gateways at 60 s against metered endpoints at 120 s). Switch the Access selector to Private for the region tabs and the p99 column; plan tiers are disclosed in the methodology.

Source code github.com/ChainBench/OpenChainBench/tree/main/harnesses/rpc-capabilities