Arbitrum docsRPC endpoints and providers
List of RPC endpoints and third-party node providers for Arbitrum One, Arbitrum Nova, and the testnets, with public and premium options for your app.
Arbitrum public RPC endpoints
Use these public RPC endpoints to connect to Arbitrum One, Arbitrum Nova, and Arbitrum Sepolia.
- Unlike the RPC URLs, the endpoints support only
eth_sendRawTransactionandeth_sendRawTransactionConditionalcalls. - The Arbitrum public RPC endpoints do not support WebSocket.
- The Arbitrum public RPC endpoints do not support IPv6.
| Name | RPC URL | Chain ID | Block explorer | Underlying chain | Tech stack | Sequencer feed URL | Sequencer endpoint |
|---|---|---|---|---|---|---|---|
| Arbitrum One | https://arb1.arbitrum.io/rpc | 42161 | Arbiscan, Blockscout | Ethereum | Nitro (Rollup) | wss://arb1-feed.arbitrum.io/feed | https://arb1-sequencer.arbitrum.io/rpc |
| Arbitrum Nova | https://nova.arbitrum.io/rpc | 42170 | Blockscout | Ethereum | Nitro (AnyTrust) | wss://nova-feed.arbitrum.io/feed | https://nova-sequencer.arbitrum.io/rpc |
| Arbitrum Sepolia (Testnet) | https://sepolia-rollup.arbitrum.io/rpc | 421614 | Arbiscan, Blockscout | Sepolia | Nitro (Rollup) | wss://sepolia-rollup.arbitrum.io/feed | https://sepolia-rollup-sequencer.arbitrum.io/rpc |
Chain Connect lists more RPC endpoints for Arbitrum One and Arbitrum Nova.
Third-party RPC providers
You can also connect to public Arbitrum chains through many of the node providers that you use on Ethereum.
To add your project to this list and to the Arbitrum portal, complete the portal application form.
To request support for a Nova third-party tool, complete the Nova support form.
| Provider | Arbitrum One | Arbitrum Nova | Arbitrum Sepolia | WebSocket | Stylus tracing |
|---|---|---|---|---|---|
| 1RPC | ✅ | ||||
| Alchemy | ✅ | ✅ | ✅ | Available on paid plans | |
| Allnodes | ✅ | ✅ | ✅ | ||
| All That Node | ✅ | ✅ | ✅ | ||
| Ankr | ✅ | ✅ | Available on paid plans | ||
| BlockPi | ✅ | ✅ | |||
| Chainbase | ✅ | ✅ | |||
| Chainnodes | ✅ | ||||
| Chainstack | ✅ | ✅ | Available on paid plans | ||
| dRPC | ✅ | ✅ | ✅ | ✅ | |
| Dwellir | ✅ | ✅ | ✅ | ||
| GetBlock | ✅ | ✅ | |||
| Infura | ✅ | ✅ | ✅ | Enabled on request | |
| Lava | ✅ | ✅ | |||
| Moralis | ✅ | ||||
| Nirvana Labs | ✅ | ✅ | ✅ | ✅ | |
| NodeReal | ✅ | ✅ | |||
| NOWNodes | ✅ | ||||
| Pocket Network | ✅ | ||||
| PublicNode | ✅ | ✅ | ✅ | ||
| Quicknode | ✅ | ✅ | ✅ | ✅ | Testnet supported in free tier |
| SwiftNodes | ✅ | ✅ | |||
| Tenderly | ✅ | ✅ | ✅ | Testnet supported in free tier | |
| Unifra | ✅ | ||||
| Validation Cloud | ✅ | ✅ | ✅ | Testnet supported in free tier |
Compare provider latency
To compare the live latency of the public Arbitrum endpoints that need no API key, use the OpenChainBench Arbitrum RPC benchmark. OpenChainBench probes each endpoint every minute from three regions. It publishes the p50, p95, and p99 latency under an open methodology and the CC BY 4.0 license.
Sequencer endpoint behavior
Arbitrum One has two public endpoints with different roles. The public RPC URL is for general use. The direct endpoint accepts only eth_sendRawTransaction and eth_sendRawTransactionConditional. The table compares their purpose and operational guarantees.
The two endpoints at a glance
| Endpoint | Purpose | Operational guarantees |
|---|---|---|
https://arb1.arbitrum.io/rpc (public RPC URL) | General-purpose read/write endpoint, useful for development and low-volume reads. | No uptime, latency, or rate-limit guarantees. If your decentralized app depends on availability, use a third-party node provider or run your own node. |
https://arb1-sequencer.arbitrum.io/rpc (sequencer endpoint) | Direct submission path to the chain's sequencer for write traffic. Accepts only eth_sendRawTransaction and eth_sendRawTransactionConditional. | Has the queueing and timeout behavior described below. It is still a best-effort public endpoint with no formal service-level agreement (SLA). |
Latency and timeout behavior
Under normal load, the sequencer endpoint accepts a transaction in less than a second. The sequencer puts each submission in a bounded in-memory queue. By default, the queue holds 1,024 transactions.
The queue timeout is 12 seconds by default. It limits how long a transaction can wait in the queue before the sequencer picks it up or rejects it. The timeout is not an end-to-end inclusion latency guarantee. If the sequencer does not pick up the transaction before the timeout, eth_sendRawTransaction returns context deadline exceeded. In that case, the sequencer did not accept the transaction, and you can safely retry it.
Recommended fallback patterns
- Use a third-party node provider as your primary endpoint, or as a fallback when a direct sequencer submission fails.
- Retry only on transient errors. You can safely retry
context deadline exceededand network or connection errors with backoff. Do not retry terminal errors, such asnonce too lowor contract reverts.
Monitoring and alerting
A successful eth_sendRawTransaction response means that the sequencer has already put your transaction in an L2 block. The call returns only after the sequencer creates the block, not when it adds the transaction to the queue. Treat this response as the sequencer's : the sequencer has ordered and executed your transaction.
The response does not mean that the transaction is posted in a batch to the , or final there. If your app needs parent-chain finality, track it separately. For monitoring, alert on submission calls that return errors or take longer than your latency limit. Do not assume a pending-but-unconfirmed state.
How is this guide?