Polygon node
A dedicated Polygon node. A Polygon RPC that never queues.
A Polygon node of your own means a Polygon RPC node that answers only you. Bor and Heimdall, the two services behind every Polygon node, run together on hardware sized for Polygon, and a busy chain never slows your reads.
- Full
- $219/mo
- Archive
- $489/mo
- Ready
- 24 h
02Full or archive
Polygon full node or Polygon archive node?
Polygon carries a lot of data, and its prices reflect that. Here is what each type holds.
Full node
$219/mo
- Keeps
- Current state and recent history, enough for apps, payments and bridges
- Query
- Contract calls, balances, event logs and sending transactions
- Cannot
- Look up deep history at an old block
- Disk
- Polygon lists snapshots of 4 TB for Bor and 500 GB for Heimdall once extracted, 4.5 TB in all
Archive node
$489/mo
- Keeps
- Every historical state, back to the start of the chain
- Query
- Reads at any past block, the basis for analytics and audits
- Good for
- Indexers, subgraph hosts and analytics teams
- Disk
- Polygon publishes no archive size. It says Bor archive mode is replacing the older Erigon archive and needs much less disk
Which one is yours
Reading balances and logs from the recent past? Full node. Rebuilding charts, indexes or audits from the first block? Archive node.
Sources: Polygon docs, snapshots, checked October 2026; Polygon forum, Erigon update and future plans (posted 30 Sep 2025), checked October 2026
03How it works
How a Polygon RPC node works: Heimdall first, then Bor.
A Polygon node is two services, not one. Heimdall tracks validators and checkpoints. Bor builds the EVM blocks your app reads.
Heimdall
Follows validators and checkpoints. It has to be fully synced before Bor starts.
Bor
Holds state and runs the EVM. It fetches spans from Heimdall as it works.
The link between them
Bor asks Heimdall for data. If the two fall out of step, you see bad blocks.
Your endpoint
JSON-RPC from Bor on nodes.herorpc.com. Peers use ports 30303 and 26656.
Both services must run for a full node. Heimdall goes first, and Bor starts once it reports it has caught up.
You get one endpoint, served by Bor. Heimdall stays behind the scenes.
A full Polygon node needs no Ethereum RPC. Only validators connect to Ethereum.
04Know the field
The Polygon disk bill, line by line.
Polygon docs publish exact snapshot sizes. Add them up and you can see why this chain costs more than a typical EVM node.
Bor grows about 100 GB a day and Heimdall about 5 GB a day. Polygon suggests a disk of 8 TB for the snapshot route.
Heimdall (v2)
- Full
- 500 GB extracted
- Archive
- No separate figure
- Source
- Polygon docs, snapshots
Bor
- Full
- 4 TB extracted
- Archive
- Archive mode (PBSS), no size published
- Source
- Polygon docs and Polygon forum
Erigon (older archive path)
- Full
- Archive only
- Archive
- Being replaced by Bor archive mode
- Source
- Polygon forum, 30 Sep 2025
The snapshots page does not label its figures full or archive; it describes mainnet Bor and Heimdall. This table describes the software, not which client a given node runs.
Sources: Polygon docs, snapshots, checked October 2026; Polygon docs, run a full node, checked October 2026; Polygon forum, Erigon update and future plans (posted 30 Sep 2025), checked October 2026
05Polygon, specifically
Six Polygon facts behind the price.
What the docs say, and what it means for a node you rent.
Order matters
Heimdall must be fully synced before Bor. Polygon tells you to check that catching_up is false on Heimdall first.
Five ports
Heimdall peers on 26656. Bor peers on 30303 over TCP and UDP, serves HTTP on 8545 and WebSocket on 8546. Heimdall REST on 1317 is optional.
105 GB a day
Add Bor at about 100 GB and Heimdall at about 5 GB a day, and the chain grows by roughly 105 GB every day.
Snapshots, not patience
A fresh sync takes several days, so Polygon recommends starting from a snapshot.
Bad blocks signal drift
A Bad block or Invalid Merkle error often means Heimdall and Bor fell out of step.
Thin hardware shows
Polygon blames slow Bor sync on weak hardware and suggests roughly doubling it. This chain punishes a cheap server.
Sources: Polygon docs, run a full node, checked October 2026; Polygon docs, snapshots, checked October 2026; Polygon docs, known issues, checked October 2026
06Who rents one
Who rents a dedicated Polygon node.
Polygon is cheap to use and heavy to run, which is the exact reason to rent.
Indexers and subgraph hosts
Heavy log reads and deep history are what shared RPCs throttle first.
Payments and stablecoin apps
Many small transfers, all of them needing a reliable confirmation read.
Gaming and NFT backends
Bursts of cheap transactions that a shared endpoint rate limits.
Bridge and relayer teams
Software that watches Polygon and Ethereum together needs a node it can count on.
07Price check
Why a Polygon node costs more, and what others charge.
The disk and its daily growth set the price, and even Allnodes lists Polygon above Ethereum. It publishes both node types, so the bars are like for like.
Full node
Archive node
Allnodes: the cheapest dedicated plan on its Polygon pricing page.
Source: Allnodes Polygon pricing, checked October 2026
Chainstack
Plan from $199 a month
A dedicated node there sits behind its Pro plan or something larger.
Chainstack pricing, checked October 2026
QuickNode
Price on request
Nothing is listed for Polygon. You ask, and they quote.
QuickNode clusters page, checked October 2026
You save each month
$261 full, $1,431 archive
against the Allnodes list price above
08What you get
Your Polygon RPC node, priced by the month.
Pick the node type and how long to prepay. The price updates as you choose.
Your Polygon node
Node type
Term
- A dedicated server sized for Polygon
- Bor and Heimdall, one endpoint
- A backup node, included
- A private endpoint on nodes.herorpc.com
- Your server logins
- No setup fee, ready within 24 hours
$219
a month, full node
Billed monthly
Pay in BTC, ETH, USDT, USDC, BNB, SOL, TRX, LTC, DOGE or XMR.
10Questions
Polygon node questions
Real questions from node operators, answered plainly.
What is a Polygon RPC node?
A server that runs Bor and Heimdall and answers your app over JSON-RPC. You send it calls and transactions, and nobody else shares its capacity.
Why is my Bor unable to connect to peers?
Open both ports. Polygon needs 30303 on TCP and UDP for Bor and 26656 for Heimdall.
Why does Bor show Bad block or Invalid Merkle?
It often means Heimdall and Bor are out of step. Check Heimdall first and let it catch up fully, because Bor builds on what it reports.
Why is Bor synchronization slow?
Polygon says slow sync usually comes down to hardware that is too weak. Start from a snapshot to skip the long catch up.
What does "Retrying again in 5 seconds to fetch data from Heimdall" mean?
Bor cannot get data from Heimdall yet. Heimdall is probably still syncing, so wait until it reports it has caught up.
Does a Polygon node need an Ethereum RPC?
A full node does not. Only validators need an Ethereum RPC, according to the Polygon docs.
How big is a Polygon node?
The snapshots add up to 4.5 TB extracted, 4 TB for Bor and 500 GB for Heimdall, and the chain grows about 105 GB a day.
What happened to the Polygon Erigon archive?
Polygon Labs announced in September 2025 that Bor archive mode will replace Erigon over time, with much less disk use. No sizes were given.
What is the price of a Polygon node?
Polygon full costs $219 a month and archive costs $489. Setup is free. When you prepay 3, 6 or 12 months, 10, 15 or 25 percent comes off.
How fast can I get a Polygon endpoint?
Within a day of paying. The endpoint and server logins land in your dashboard.
A Polygon RPC with room to spare.
Polygon full is $219 a month and archive $489. Backup node included, endpoint within 24 hours.