Update (Sept. 10, 10:35 am UTC): This article has been updated with information throughout.
Update (Sept. 10, 11:50 am UTC): This article has been updated to add comments from a Polygon representative.
Polygon is experiencing a temporary delay in consensus finality because of a bug affecting the Bor and Erigon nodes, according to an official incident report on its status page.
The issue, which began early on Wednesday, disrupted some Remote Procedure Call (RPC) services and caused apps built on the network to encounter access issues. While the Polygon blockchain remains live and continues producing blocks, a number of RPC providers and validators were forced to rewind to the last finalized block and resynchronize.
The Polygon team confirmed that the bug is preventing node progress for certain configurations. However, restarting the affected nodes has resolved the issue for some participants. “We see that a restart of nodes has fixed the issues for many validators and RPC providers,” Polygon said.
Engineers are collaborating with infrastructure providers to accelerate the debugging efforts and full functionality. The team clarified that the incident does not affect core chain operations and assured users of a swift recovery.
Coinpectra reached out to Polygon Labs for comments but did not get a response by publication.
Polygon says the chain is producing blocks
At the time of writing, Polygon’s block explorer and analytics platform Polygonscan shows that the last block produced by the network was made over five hours ago. However, in its latest update, the company redirected users to another link showing block updates.
A Polygon representative told Coinpectra that Polygonscan’s nodes were halted at the bad milestone produced by Heimdall, Polygon’s consensus engine.
“We’re working with them to switch over to functioning nodes that didn’t halt,” the representative told Coinpectra.
At 08:52 UTC, the team emphasized that the blockchain continues to run and blocks are still being produced. “Checkpoint finality is working as expected within 15 mins,” Polygon wrote.
The link shared by Polygon shows that blocks are being produced in real time.
The Polygon team also posted on X that while they are still actively investigating the issue with the nodes causing delays in block finality, they have figured out a solution.
“We have identified a fix and it is being rolled out to all validators and service providers soon,” the team wrote.
The Polygon representative also told Coinpectra that current analysis shows that the finality gadget in Heimdall, which typically produces milestones every few seconds, is not producing new milestones.
“This means that while blocks continue to be produced and added to the chain, finality is delayed until checkpoints are posted on Ethereum every 20 minutes,” the representative said.
Polygon said they are working with major infrastructure providers to minimize the impact of the issue.
Related: Ethereum validator exit queue to spike as Kiln moves tokens
What are the Bor and Erigon nodes?
Bor and Erigon are two key pieces of software that help run the Polygon network behind the scenes. Bor is the main program that produces and organizes new blocks of transactions in the network.
Meanwhile, Erigon is a tool that helps blockchain infrastructure providers access, store and retrieve blockchain data more efficiently. It’s designed for speed, stability and low storage use, making it useful for companies running explorers, analytics platforms or decentralized application (DApp) backends.
Magazine: Korean bill to legalize ICOs, Chinese firm’s Ethereum RWAs mystery: Asia Express