What actually happens during a polygon network reorg

23 October 2026

A Polygon network reorg (short for "reorganization") is when a block that was previously confirmed as part of the chain gets discarded and replaced by a different block or set of blocks. For everyday users, the practical effect is usually this: a transaction you thought was final either disappears from the chain or changes status, and you may need to resubmit it. Reorgs are a normal part of how Polygon's consensus works, not a bug or a sign that the network is broken.

To understand why reorgs happen, you need to know a little about how Polygon orders transactions. Polygon runs a proof-of-stake system where a small set of validators propose and confirm blocks. Most of the time, the network reaches agreement quickly, and blocks are added one after another in a straight line. Occasionally, though, two validators produce a valid block at roughly the same time, or a validator proposes a block that conflicts with what another validator just built. The network must choose which chain to keep. The discarded chain is the reorg.

The two-second window you should know about

Polygon aims for a block time of about 2 seconds. That is fast, and it creates a constant, low-level risk of a reorg. Here is the sequence of events in a typical reorg:

1. Validator A produces block #10,000 and broadcasts it.
2. Validator B produces block #10,000 at nearly the same time, based on block #9,999.
3. Some validators see A's block first; others see B's block first. They build block #10,001 on top of whichever they saw.
4. After a few seconds, the network reaches a "checkpoint" - a snapshot of the chain state that gets finalized.
5. If more validators built on A's chain, then B's block #10,000 is discarded, along with anything built on top of it. That is a reorg.

The critical detail is that a transaction included in a block that gets discarded does not automatically fail. It just disappears from the canonical chain. It is as if you submitted it and then someone hit "undo." The transaction is still valid, and it can be picked up again by a future block - but you will need to resubmit it, and you will need to pay the gas fee again.

How you would notice a reorg

Most Polygon users never notice a reorg happening. The window is short, and the network moves on quickly. But you might notice it in a few ways:

• Your pending transaction vanishes. You look at your wallet, and the transaction you sent five minutes ago is gone from the "pending" list. It did not fail; it was just in a block that got reorged.
• A transaction you saw confirmed is no longer there. If you check PolygonScan and see a block number, then check again 30 seconds later and see a different block at that height, you just witnessed a reorg.
• Your balance changes unexpectedly. If you sent tokens and the receiving transaction was in a reorged block, your balance will revert to what it was before the send - until you resubmit.

These events are almost always brief. A reorg on Polygon typically resolves in a few seconds, and the network moves forward. The longer a block has been confirmed, the less likely it is to be reorged. Polygon uses a checkpointing mechanism that references the Ethereum blockchain, so once a batch of Polygon blocks has been checkpointed to Ethereum, those blocks are considered final and cannot be reorged.

What you should do during a reorg

The honest answer is: very little. A reorg is not an emergency. It is a consensus event that the network is designed to handle. Here is what you should do if you suspect one is happening:

1. Wait a few minutes. In almost all cases, the network will resolve itself. Do not resubmit the transaction immediately, because you might end up double-spending or paying extra gas for nothing.
2. Check PolygonScan. Look up your wallet address and see whether the transaction is still pending, confirmed, or gone. If it is confirmed and then later disappears, you have seen a reorg. Wait for it to settle.
3. If the transaction is gone, resubmit it. You will need to pay the gas fee again. There is no way around this - the original transaction was never actually included in the final chain.
4. For large amounts, wait for more confirmations. A rule of thumb: the more confirmations a transaction has, the safer it is. On Polygon, a few minutes is usually plenty. But if you are moving a significant amount and want extra certainty, wait for the next checkpoint to be finalized on Ethereum. You can see this on PolygonScan by looking for the "checkpoint" status.

What a reorg is not

It is worth being clear about what a reorg is not. It is not a chain split where the network permanently diverges into two separate currencies. It is not a hack. It is not a sign that your funds are at risk. And it is not something you caused by using the network incorrectly.

Reorgs are more common on Polygon than on Ethereum mainnet, simply because Ethereum's 12-second block time gives the network more time to reach agreement before the next block is proposed. Polygon's 2-second block time is a trade-off: speed for a slightly higher chance of temporary reorgs. For most everyday use - sending tokens, using a DApp, approving a swap - the risk is negligible. For very large transactions, the prudent move is to wait for a few extra confirmations, just as you would on any chain.

The network's design accounts for this. Polygon validators are expected to produce blocks quickly and to build on the chain that most other validators have seen. When a reorg happens, it is usually resolved before you have time to finish checking your wallet. If you do catch one in progress, the best thing you can do is nothing at all - wait, verify, and then resubmit if needed. The chain will sort itself out, and your funds will still be where you left them.

Back to polygon