Skip to main content

RPC Providers

There are multiple RPC providers from which you can choose from. These providers will work as intermediaries to help you interact with the NEAR network. You'll experience different latency levels depending on the provider's location. You can potentially use multiple providers for redundancy and balancing.

tip

If you want to use a custom RPC provider with NEAR Wallet Selector, check this example.

Mainnet​

ProviderEndpoint Root
NEARhttps://rpc.mainnet.near.org
Pagodahttps://rpc.mainnet.pagoda.co
1RPChttps://1rpc.io/near
All That Nodehttps://near-mainnet-rpc.allthatnode.com:3030
ankr.comhttps://rpc.ankr.com/near
BlockPI Networkhttps://near.blockpi.network/v1/rpc/public
dRPChttps://near.drpc.org
fast-near web4https://rpc.web4.near.page
FASTNEARhttps://free.rpc.fastnear.com
Gateway.fmhttps://rpc.near.gateway.fm/
GetBlockhttps://getblock.io/nodes/near/
Lava Networkhttps://near.lava.build
Lavender.Five Nodeshttps://near.lavenderfive.com/
NodeRealhttps://nodereal.io/api-marketplace/near-rpc
NOWNodeshttps://near.nownodes.io/
OMNIAhttps://endpoints.omniatech.io/v1/near/mainnet/public
QuickNode-
Seraclehttps://api.seracle.com/saas/baas/rpc/near/mainnet/public/
Zeeve-

Testnet​

ProviderEndpoint Root
NEARhttps://rpc.testnet.near.org
Pagodahttps://rpc.testnet.pagoda.co
FASTNEARhttps://test.rpc.fastnear.com

RPC Failover​

In near-api-js you can use FailoverRpcProvider to automatically switch RPC providers when one provider is experiencing downtime, or implement an RPC selection widget that allows users to add their own RPC provider.

As a user, if a dApp or wallet doesn't support RPC failover and the primary provider is down, you can use an RPC Selector browser extension to redirect all requests to an RPC provider of your choice.

Was this page helpful?