Arbitrum RPC Nodes & Endpoints

Arbitrum One public RPC endpoints

Free, third-party public endpoints for reads and prototyping. They are shared and rate-limited, not run by BLAZED.sh, so use a dedicated node for production traffic.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://arb1.arbitrum.io/rpc");
const blockNumber = await provider.getBlockNumber();
console.log("Arbitrum One block:", blockNumber);

Dedicated Arbitrum One RPC node vs shared endpoints

Arbitrum One produces blocks roughly every 250 milliseconds, which changes the math of sharing an endpoint. On a shared public RPC, a single network round trip can span several Arbitrum blocks, so a bot that reads state, decides, and submits is often acting on a chain that has already moved on. Add the rate limits public endpoints apply during volatile markets, exactly the moments perps and arbitrage strategies need throughput, and the free URL becomes the most expensive part of the stack.

A dedicated Arbitrum RPC node gives your workload the whole node: no shared quotas, room for arbtrace calls and wide eth_getLogs ranges, and the option to consume the sequencer feed for the earliest possible view of transaction ordering. On BLAZED.sh the model goes further, running your container on the node host itself so reads stay on a local socket.

Arbitrum One RPC latency: architecture over benchmarks

With 250 millisecond blocks, latency budgets on Arbitrum are tighter than almost anywhere else in the EVM world. A remote gateway adds tens to low hundreds of milliseconds per call across the public internet, which is several block times, before any provider-side queueing. Co-location removes that path: on our live Ethereum product, calls from a container on the node host complete in under 10 milliseconds, and dedicated Arbitrum nodes will follow the same architecture. No remote endpoint, however fast its marketing page, can beat not crossing the network at all.

What a dedicated Arbitrum One node costs

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost 1 credit, a few heavy operations like txpool_content and the trace_replay methods cost 4, and responses over 100KB add 50 credits per MB. The Beta plan is €75 per month with 1M credits, 1 container and 2 scripts; Beta XL is €249 per month with 5M credits, 3 containers and 4 scripts; Enterprise plans add private nodes and archive access. These are the live Ethereum plans today, and pricing is still being finalized. Dedicated Arbitrum One nodes will launch on the same credit model, with the waitlist above deciding rollout priority.

Trading workloads on Arbitrum are read-heavy, and reads are single-credit calls, so even a tight evaluation loop maps to a predictable monthly credit count rather than a compute-unit surprise.

Perfect for

What is Arbitrum One?

Arbitrum Nitro compiles the EVM to WASM and uses fraud proofs to settle to Ethereum, giving developers near-perfect EVM compatibility at a fraction of mainnet gas. It has among the highest total value locked of any L2, so a large share of on-chain trading, lending, and perps activity flows through Arbitrum RPC endpoints. Reads with chain ID 42161 behave like any Ethereum node, but Arbitrum exposes a couple of chain-specific methods (for example arbtrace and L1 gas estimation) that matter for accurate fee prediction. High-frequency strategies and indexers feel every millisecond of RPC latency here, which is exactly the pain a co-located, dedicated node removes.

Arbitrum One RPC: frequently asked questions