RPC 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
This section and the two that follow describe the new transaction submission behavior. It reaches Arbitrum Sepolia first and Arbitrum One later. Until it reaches a chain, the sequencer endpoint on that chain works the old way:
eth_sendRawTransactionreturns after the sequencer includes the transaction in a block.- On queue timeout,
eth_sendRawTransactionreturnscontext deadline exceeded. The sequencer didn't accept the transaction, so you can retry it.
For details, see Transaction submission behavior.
Under nominal load, the sequencer endpoint accepts a submission in well under a second. The sequencer places each submission in a bounded in-memory queue, with a default capacity of 1024. The queue timeout, 12 seconds by default, limits how long a transaction can wait in that queue. It isn't a guarantee of end-to-end inclusion time.
When a submission hits a queue limit, eth_sendRawTransaction behaves as follows:
- Queue full: it returns an error right away.
- Queue timeout: the sequencer drops the transaction.
eth_sendRawTransactionhas already returned the transaction hash, so you get no error and no receipt. The transaction is not included. Check the sender's nonce, then resubmit the same signed transaction or re-sign it with the same nonce. See Handle transactions with no receipt.
Recommended fallback patterns
- Use a third-party node provider as your primary endpoint, or as a fallback when a direct sequencer submission fails.
- Retry on transient errors only. You can retry network and connection errors with backoff. Don't retry terminal errors such as
nonce too low. - Read reverts from the receipt. A revert isn't a submission error. The receipt shows it, with
statusset to0x0. - If a transaction has no receipt by your deadline, check the sender's nonce before you resubmit. See Handle transactions with no receipt.
Monitoring and alerting
A successful eth_sendRawTransaction response means the sequencer admitted your transaction into its queue. It does not mean the transaction is in a block. To confirm inclusion, poll eth_getTransactionReceipt. You can also send the transaction to an RPC node with eth_sendRawTransactionSync, which returns the receipt once the sequencer executes the transaction. For details, see Transaction submission behavior.
Neither response means the transaction is posted to the parent chain in a batch or finalized there. If your application needs parent-chain finality guarantees, track that separately. For monitoring, alert on these cases:
- Submission calls that return errors or exceed your expected latency ceiling.
- Transaction hashes that never get a receipt.
How is this guide?