Polygon PoS RPC Nodes & Endpoints

Polygon PoS RPC URLs you can use right now

Third-party endpoints, free and shared. Polygon's transaction count is among the highest of any EVM network, so these congest earlier in the day than their equivalents on quieter chains.

import { JsonRpcProvider } from "ethers";

const provider = new JsonRpcProvider("https://polygon-rpc.com");
const blockNumber = await provider.getBlockNumber();
console.log("Polygon PoS block:", blockNumber);

Polygon PoS or Polygon zkEVM: which RPC do you actually want?

Searching for a Polygon RPC URL returns endpoints for two different networks, and they are not interchangeable. This page covers Polygon PoS, chain ID 137, the high-throughput chain with its own validator set that checkpoints to Ethereum and carries essentially all of the gaming, payments, and NFT activity people mean when they say Polygon. Polygon zkEVM is a separate network on chain ID 1101, a zero-knowledge rollup with its own state, its own contract deployments, and its own bridge.

Pointing a wallet or a backend at the wrong one usually fails quietly rather than loudly. The RPC responds, the block numbers look plausible, and the contract address you queried simply reports no code, because that contract lives on the other network. If you inherited an integration and are not certain which network it targets, call eth_chainId and read the answer: 137 is PoS, 1101 is zkEVM. The other lingering source of confusion is the token. Gas on Polygon PoS is denominated in POL, which replaced MATIC, so older documentation and hardcoded symbol strings can be out of date even when the endpoint is correct.

Why Polygon's transaction volume breaks shared endpoints first

Polygon PoS regularly processes more transactions than almost any other EVM chain, and public endpoints deal with that pressure bluntly: aggressive rate limits, small eth_getLogs windows, and throttling during exactly the busy periods that generate the data you want. Teams running NFT reward distribution, payments reconciliation, or game-state indexing on Polygon tend to discover those limits mid-pipeline, as a backfill that stalls somewhere around block forty million.

A dedicated Polygon RPC node means the checkpointing cadence, Bor's block production, and your own query pattern are the only variables, not a stranger's traffic. Wide log ranges, steady websocket subscriptions, and archive reads run at hardware speed. On BLAZED.sh, dedicated also means co-located: your worker runs next to the node and reads over a local socket.

Polygon RPC latency is a distance problem

With two-second blocks and enormous transaction counts, Polygon's practical bottleneck is rarely the chain and almost always the RPC path. A remote gateway spends tens to low hundreds of milliseconds per call on the public internet before any provider-side queueing starts. Removing the network is the structural fix: on our live Ethereum product, co-located calls complete in under 10 milliseconds, and dedicated Polygon nodes will ship on the same architecture.

What dedicated Polygon node hosting will cost

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost a single credit, and only a handful of heavy operations cost more. Dedicated Polygon PoS nodes will launch on the same credit model, with the waitlist deciding rollout priority.

High-volume Polygon pipelines are dominated by single-credit reads and log queries, so the monthly credit allowance translates directly into how many millions of calls your pipeline can make.

Perfect for

What is Polygon PoS?

Polygon PoS has long been one of the most-used EVM networks by transaction count, popular for its sub-cent fees and broad wallet and exchange support. It runs Bor (block production) and Heimdall (validator/consensus) layers and periodically checkpoints to Ethereum. Gas is denominated in POL (the successor to MATIC), but from an integration standpoint you connect exactly like Ethereum using chain ID 137. Its high tx volume means public RPCs get congested quickly, and workloads such as NFT indexing, reward distribution, and analytics routinely need larger log ranges and steadier throughput than shared endpoints allow, and a dedicated node keeps those pipelines from stalling.

Polygon RPC: frequently asked questions