Polygon Mainnet RPC Endpoints
Chain ID: 137 • Network ID: 137
Available RPC Endpoints
35 endpoints #1 HTTPS
https://rpc.ankr.com/polygon #2 HTTPS
https://polygon-rpc.com #3 HTTPS
https://rpc-mainnet.matic.quiknode.pro #4 HTTPS
https://polygon-public.nodies.app #5 HTTPS
https://polygon-mainnet.public.blastapi.io #6 HTTPS
https://1rpc.io/matic #7 HTTPS
https://polygon-mainnet.rpcfast.com?api_key=xbhWBI1Wkguk8SNMu1bvvLurPGLXmgwYeC4S6g2H7WdwFigZSmPWVZRxrskEQwIf #8 HTTPS
https://polygon-bor-rpc.publicnode.com #9 WebSocket
wss://polygon-bor-rpc.publicnode.com #10 HTTPS
https://polygon-mainnet.g.alchemy.com/v2/demo #11 HTTPS
https://go.getblock.io/02667b699f05444ab2c64f9bff28f027 #12 HTTPS
https://polygon.api.onfinality.io/public #13 HTTPS
https://polygon.rpc.blxrbdn.com #14 HTTPS
https://polygon.drpc.org #15 HTTPS
https://polygon.gateway.tenderly.co #16 HTTPS
https://gateway.tenderly.co/public/polygon #17 HTTPS
https://api.zan.top/polygon-mainnet #18 HTTPS
https://polygon.meowrpc.com #19 HTTPS
https://public.stackup.sh/api/v1/node/polygon-mainnet #20 HTTPS
https://polygon-mainnet.gateway.tatum.io #21 HTTPS
https://polygon.rpc.subquery.network/public #22 HTTPS
https://polygon-mainnet.4everland.org/v1/37fa9972c1b1cd5fab542c7bdd4cde2f #23 WebSocket
wss://polygon-mainnet.4everland.org/ws/v1/37fa9972c1b1cd5fab542c7bdd4cde2f #24 HTTPS
https://endpoints.omniatech.io/v1/matic/mainnet/public #25 HTTPS
https://polygon.lava.build #26 HTTPS
https://rpc.owlracle.info/poly/70d38ce1826c4a60bb2a8e05a6c8b20f #27 HTTPS
https://polygon.therpc.io #28 HTTPS
https://rpc.poolz.finance/polygon #29 HTTPS
https://poly.rpc.grove.city/v1/01fdb492 #30 HTTPS
https://rpc-mainnet.matic.network #31 HTTPS
https://matic-mainnet.chainstacklabs.com #32 HTTPS
https://rpc-mainnet.maticvigil.com #33 HTTPS
https://matic-mainnet-full-rpc.bwarelabs.com #34 WebSocket
wss://polygon.gateway.tenderly.co #35 WebSocket
wss://polygon.drpc.org About RPC Endpoints
RPC (Remote Procedure Call) endpoints allow your applications to interact with the Polygon Mainnet blockchain. Choose the endpoint that best fits your needs based on protocol (HTTPS/WebSocket) and performance requirements.