> For the complete documentation index, see [llms.txt](https://help.railway.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.railway.xyz/setup/setting-custom-rpcs.md).

# Setting Custom RPCs

**NOTE: Railway Wallet contributors do not maintain or recommend any specific RPC nodes. All RPC nodes are maintained by independent third parties with no connection to Railway Wallet.**

{% embed url="<https://www.youtube.com/watch?v=JVtUweNcpvA>" %}

1. Click "**Settings"** then click “Network & RPCs”

<figure><img src="/files/QAqWty4gMxANISIw0bdQ" alt=""><figcaption></figcaption></figure>

2. Click the **network** you wish to add a custom RPC to. In this case, it's Ethereum.

<figure><img src="/files/JpW5CZHDHBNqdBRyWjch" alt=""><figcaption></figcaption></figure>

3. Click "**Set custom provider"**

<figure><img src="/files/91KJtdIaT3F31bLj2H38" alt=""><figcaption></figcaption></figure>

3. Find an RPC provider that matches your privacy and latency requirements. Choice of RPC provider is entirely up to the user and no one can recommend specific RPCs to you. \
   \
   A good place to start is an independent list of RPCs like [Chainlist](https://chainlist.org)&#x20;
4. Once you've selected an RPC, copy and paste the URL into the custom RPC URL box and click "**Submit**"

<figure><img src="/files/GtNXFiuFYkeWt4Wl4fwb" alt=""><figcaption></figcaption></figure>

5. Your custom RPC is now toggled on by default.&#x20;

<figure><img src="/files/C4KLyWDQehzqhcaU7mUU" alt=""><figcaption></figcaption></figure>

6. To toggle on default RPCs as a backup, click the "**Status**" button. You can also add additional custom RPCs by clicking "**Add custom provider**" again.

<figure><img src="/files/dIQpYACoCGUZ8NRmcxXY" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.railway.xyz/setup/setting-custom-rpcs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.