Polygon public RPC endpoints, tested

Every keyless Polygon (chain ID 137) endpoint listed on Chainlist and chainid.network, tested the same way on 2026-11-08: does it answer on the right chain, how fast, how far behind the best head, how large an eth_getLogs range it accepts, whether it keeps archive state, and whether its WebSocket actually streams. 12 of 28 HTTP endpoints were working.

Working HTTP endpoints

EndpointLatencyBehind besteth_getLogsState
https://rpc-polygon.blockmachine.io42 ms0 blocksunder 1,000recent only
https://polygon.api.onfinality.io/public474 ms3 blocks1,000none
https://rpc.swiftnodes.io/rpc/polygon (SwiftNodes, keyless: 2 req/s)6 ms4 blocksunder 1,000recent only
https://rpc-mainnet.matic.quiknode.pro8 ms17 blocks10,000+archive (1M+)
https://api.zan.top/polygon-mainnet22 ms12 blocksunder 1,000archive (1M+)
https://polygon-bor-rpc.publicnode.com31 ms17 blocks10,000+none
https://polygon.drpc.org32 ms19 blocksunder 1,000archive (1M+)
https://polygon-bor-rpc.blockreq.com/v1/rpc/public52 ms16 blocks1,000none
https://rpc.nodeflare.app/polygon/public58 ms7 blocks1,000none
https://poly.api.pocket.network65 ms7 blocks10,000+archive (1M+)
https://public.blazingnode.com98 ms13 blocksunder 1,000none
https://matic.rpc.sentio.xyz179 ms5 blocksunder 1,000archive (1M+)

Order: endpoints within 3 blocks of the best head first, then by median latency. Latency is measured from one server, so yours will differ by region; lag and limits do not.

WebSocket endpoints

  • streams poly.api.pocket.network: first head after 795 ms
  • streams polygon-bor-rpc.publicnode.com: first head after 2202 ms
  • streams polygon.drpc.org: first head after 2262 ms
  • does not stream polygon.gateway.tenderly.co: connection failed (connect)
  • does not stream rpc.satelink.network/rpc/ws/polygon: connection failed (connect)
  • does not stream polygon-mainnet.4everland.org/ws/v1/37fa9972c1b1cd5fab542c7bdd4cde2f: connection failed (connect)
  • does not stream rpc.swiftnodes.io/ws/polygon (SwiftNodes): subscribe rejected: WebSocket subscriptions require an API key. Get a free key at https://swiftnodes

Listed but not working

  • rpc.satelink.network/rpc/polygon: no answer (HTTP 404)
  • rpcfree.com/polygon-rpc: no answer (HTTP 200)
  • rpc.hostdefi.com/api/rpc/polygon: no answer (HTTP 403)
  • api.blockvectra.com/v1/polygon_mainnet/public: eth_blockNumber failed
  • xrpc.cl/polygon: chainId: XRPC Cluster: Backend polygon node currently syncing and fallbacks busy
  • rpc.ankr.com/polygon: chainId: Unauthorized: You must authenticate your request with an API key. Create an account on http
  • polygon-public.nodies.app: no answer (HTTP 403)
  • polygon-mainnet.public.blastapi.io: chainId: Blast API is no longer available. Please update your integration to use Alchemy's API inste
  • public.1rpc.io/matic: chainId: You've reached the usage limit for your current plan. To continue with higher limits and un
  • polygon.gateway.tenderly.co: chainId: rate limited
  • lb.routeme.sh/rpc/evm/137: chainId: rate limited
  • rpc.owlracle.info/poly/70d38ce1826c4a60bb2a8e05a6c8b20f: no answer (HTTP 401)
  • gateway.tenderly.co/public/polygon: chainId: rate limited
  • rpc.private.mev-x.com/polygon: chainId: fetch failed
  • polygon-mainnet.gateway.tatum.io: chainId: rate limited
  • api-polygon-mainnet-full.n.dwellir.com/2ccf18bf-2916-4198-8856-42172854353c: chainId: rate limited

Test any endpoint yourself with the RPC tester. Our Polygon endpoint, limits and status: Polygon RPC, uptime history.