RPC Providers

To Share and +4 nLEARNs

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.

Mainnet

Provider Endpoint Root
NEAR https://rpc.mainnet.near.org
Pagoda https://rpc.mainnet.pagoda.co
1RPC https://1rpc.io/near
All That Node https://near-mainnet-rpc.allthatnode.com:3030
ankr.com https://rpc.ankr.com/near
BlockPI Network https://near.blockpi.network/v1/rpc/public
dRPC https://near.drpc.org
fast-near web4 https://rpc.web4.near.page
FASTNEAR https://free.rpc.fastnear.com
Gateway.fm https://rpc.near.gateway.fm/
GetBlock https://getblock.io/nodes/near/
Lava Network https://near.lava.build
Lavender.Five Nodes https://near.lavenderfive.com/
NodeReal https://nodereal.io/api-marketplace/near-rpc
NOWNodes https://near.nownodes.io/
OMNIA https://endpoints.omniatech.io/v1/near/mainnet/public
QuickNode
Seracle https://api.seracle.com/saas/baas/rpc/near/mainnet/public/
Zeeve

Testnet

Provider Endpoint Root
NEAR https://rpc.testnet.near.org
Pagoda https://rpc.testnet.pagoda.co
FASTNEAR https://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.

Generate comment with AI 2 nL
Scroll to Top