Polygon PoS RPC Nodes & Endpoints

Polygon PoS public RPC endpoints

Free, third-party public endpoints for reads and prototyping. They are shared and rate-limited, not run by BLAZED.sh, so use a dedicated node for production traffic.

import { JsonRpcProvider } from "ethers";

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

Dedicated Polygon PoS RPC node vs shared endpoints

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 PoS RPC latency: architecture over benchmarks

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 a dedicated Polygon PoS node costs

BLAZED.sh prices node access in per-request credits granted monthly by your subscription, with a deliberately narrow weight spread: most RPC methods cost 1 credit, a few heavy operations like txpool_content and the trace_replay methods cost 4, and responses over 100KB add 50 credits per MB. The Beta plan is €75 per month with 1M credits, 1 container and 2 scripts; Beta XL is €249 per month with 5M credits, 3 containers and 4 scripts; Enterprise plans add private nodes and archive access. These are the live Ethereum plans today, and pricing is still being finalized. Dedicated Polygon PoS nodes will launch on the same credit model, with the waitlist above 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 PoS RPC: frequently asked questions