On September 10, 2025, Polygon, one of the best Ethereum layer-2 scaling solutions, had a temporary problem with transaction finality due to a defect in its Bor and Erigon nodes. This problem, which started early on Wednesday, caused a delay in the finalization of consensus.
It affected Remote Procedure Call (RPC) services and made some validators have to resynchronize with the network. The Polygon blockchain kept making blocks, but the disruption affected apps that were created on the network, which worried developers and consumers.
The main problem came from a defect that stopped nodes from moving forward in specific settings, which made it hard for various validators and RPC providers to do their jobs. Because of this, the nodes that were affected had to go back to the last finalized block, which was around block number 76,273,070, and sync again.
This made transactions take longer to finalize, with confirmations taking between 10 and 15 minutes instead of the network’s usual near-instantaneous speed. Polygon’s checkpoint validation kept working even as the chain slowed down, so the fundamental functions were still running smoothly.
Polygon’s development Team worked promptly to find the flaw and send out a remedy to all of the validators. For many validators and RPC providers, restarting the impacted nodes fixed the problem and brought the network back to normal.
The Polygon Foundation stressed that the blockchain stayed online during the event and that services that weren’t affected could still execute transactions. Engineers worked with infrastructure suppliers to speed up debugging and make sure everything was back to normal. Updates were posted on Polygon’s official status page.
This event highlights the challenges of maintaining stability in complex blockchain networks, particularly for layer-2 solutions like Polygon, which supports a vast ecosystem of NFT and DeFi applications. The momentary outage affected services such as PolygonScan and Alchemy Polygon; however, the essential functionality of the network remained unchanged.
Polygon’s quick response demonstrates the importance of staying vigilant and acting promptly to maintain user trust. As more people start using blockchain, occurrences like this remind us that we need to make changes to ensure it remains safe and reliable continually.
