# Resource: Directory of 94 Arbitrum One RPC Nodes & Data APIs

**URL:** <https://forum.arbitrum.foundation/t/resource-directory-of-94-arbitrum-one-rpc-nodes-data-apis/29979>\
**Category:** Technical Discussion\
**Created:** [September 16, 2025, 8:52am UTC](https://forum.arbitrum.foundation/t/resource-directory-of-94-arbitrum-one-rpc-nodes-data-apis/29979 "2025-09-16T08:52:33Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Olivia](https://avatars.discourse-cdn.com/v4/letter/o/b9e5f3/32.png) [@Olivia](https://forum.arbitrum.foundation/u/Olivia)\
**Post date:** [September 16, 2025, 8:52am UTC](https://forum.arbitrum.foundation/t/resource-directory-of-94-arbitrum-one-rpc-nodes-data-apis/29979/1 "2025-09-16T08:52:33Z")

</div>

Hey everyone,

I came across a useful resource that might help developers working on Arbitrum projects. CompareNodes recently published a curated directory of **94 arbitrum one RPC nodes & Data APIs** , including both free and paid providers.  
[https://www.comparenodes.com/protocols/arbitrum-one/](https://www.comparenodes.com/protocols/arbitrum-one/)

The list covers things like:

Which providers support Arbitrum One and Sepolia  
Whether the endpoints are public or private  
Uptime status and pricing references  
Links to 37 free/public endpoints

What I liked is that it’s not just a static list it ties into their performance tools, so you can actually compare RPC endpoints from different regions to see which ones respond best for your use case. For me, this solved a lot of guesswork when choosing an RPC provider for testing.

 ![Screenshot 2025-09-16 092853](https://canada1.discourse-cdn.com/flex029/uploads/arbitrum1/original/2X/c/c7696c7d991de2a745cbbafac100ace3b44b7f3b.png)