Arbitrum One (L2 )
Arbitrum One runs on Nitro with sub-second blocks. Tessellate plans Arbitrum One RPC for launch in Q1 2027, served from Nitro node pools.
Requests pass through the same Envoy gateway, router and cache as our other chains, with the same plans and limits.
Talk to Us About Arbitrum RPC
Block time
Availability target
Execution client
WebSocket subscriptions
Snapshot cadence
Head lag target
Reorg window
Debug and trace methods
*Targets are measured at our edge, per region, each month, and published on the status page. Contact our team to discuss committed capacity.
Why connect to Arbitrum One with Tessellate?
-
Status: Launch, Q1 2027
-
Nitro node pools behind the same gateway as every other chain
-
Sub-second blocks, with head lag targeted within two blocks
-
A cache keyed by block hash; latest and pending are never cached beyond one block time
-
p95 under 250 ms for eth_call in the nearest region (target)
Explore insights from our engineers
Arbitrum One RPC FAQ
Send JSON-RPC requests to https://arbitrum-one.rpc.thetessellatelabs.com with your API key. Endpoints need an API key created in the Tessellate dashboard.
Nitro, in per-chain node pools. The router selects backends by health, weighted by head lag, error rate and latency. Arbitrum One is planned for launch in Q1 2027.
Archive reads need Build or above and are weighted 5x on Build and 3x on Scale. They are unmetered on Dedicated. Archive depth will be published at launch.
debug_ and trace_ methods are not on Developer or Build, weigh 20x on Scale and are unmetered on Dedicated. Coverage for Arbitrum One will be published at launch.
eth_getLogs accepts a block range of 2,000 on Developer and Build, 10,000 on Scale, and a configurable range (default 50,000) on Dedicated and Enterprise. Result caps are 10,000, 20,000 and 100,000 logs.
No. Wallets are out of scope. Tessellate provides RPC access and never holds customer keys or assets.
Four things shape how a reorganised head reaches you:
Cache keys:
- the cache is keyed by block hash and holds immutable data only.
- Latest and pending: never cached beyond one block time.
- Head lag: the router steers away from backends that fall behind, and we target head within two blocks of canonical for 99.9% of minutes.
- Finality: guidance for Arbitrum One will be published at launch.
WebSocket subscriptions are available from the Build plan, at 10, 50 or 500 per API key depending on plan.
Limits apply per API key: 25 requests per second on Developer, 150 on Build and 800 on Scale. Archive reads are weighted 5x on Build and 3x on Scale. Dedicated plans are not metered.
JSON-RPC batches are 25 requests on Developer and Build, 100 on Scale and 500 on Dedicated and Enterprise. Responses are capped at 10 MB, 25 MB and 150 MB by plan.
The target is 99.9% availability on shared tiers, measured at our edge per region per month and published on status.thetessellatelabs.com, including the months we miss.
If you have any outstanding questions, please feel free to reach out to our team at [email protected].
The information on this page is for general information only. It is not legal, business, tax or investment advice. Figures described as targets are goals, not guarantees; measured results are published on status.thetessellatelabs.com. Please consult your own advisers for advice on the matters covered here.
Explore additional chains
Tessellate supports twelve EVM chains by month twelve. Learn how to connect.
Meet With Us
Bring reliable infrastructure to your organisation.
Tessellate respects your privacy. By submitting this form, you are acknowledging that you have read and agree to our Privacy Policy, which details how we collect and use your information.