Polygon has restored full network stability after a software bug temporarily disrupted milestone finality and forced some nodes offline, according to an official incident report published on the project’s status 3 issue began early Wednesday when a bug affecting Bor, Polygon’s block producer, and Erigon, its data access layer, caused disruptions across parts of the 4 the blockchain itself continued to produce blocks, some Remote Procedure Call (RPC) services and validators halted, forcing providers to rewind to the last finalized block and 5 Executes Emergency Hard Fork to Resolve Finality Bug Polygon engineers confirmed the bug was preventing node progress under certain configurations, though restarting affected nodes resolved the issue for several validators and RPC 6 the time, Polygonscan, the network’s block explorer, showed no block updates for more than five 7 later explained that Polygonscan’s nodes had halted after a faulty milestone produced by Heimdall, the project’s consensus engine.
A company representative said that the team was working with Polygonscan to switch to functioning nodes that had not halted, stressing that block production remained live. “Checkpoint finality is working as expected within 15 minutes,” the team said in an update at 08:52 UTC, sharing an alternative link where real-time block production could be 8 PoS network faces 10-15 minute transaction delays from a node bug as protocols suspend operations and POL drops 3.42%. #Polygon #POS 0 — 9 (@cryptonews) September 10, 2025 Analysis revealed the problem stemmed from Heimdall’s finality gadget, which is responsible for producing milestones every few 10 checkpoints to Ethereum were still being posted every 20 minutes, milestones, which provide faster, deterministic finality, were not being 11 left local fast finality delayed even as the main chain continued adding 12 address the problem, Polygon rolled out emergency updates: Bor version 2.2.11-beta2 and Heimdall version 0.3.1, the latter requiring a hard 13 upgrade, executed at 3 p.
m. UTC, deleted the faulty milestone and purged it from node 14 confirmed soon after that the hard fork was successfully completed and that both milestones and checkpoints were once again finalizing normally.) September 10, 2025 Polygon Foundation co-founder and CEO Sandeep Nailwal later explained that the disruption originated from a faulty milestone proposal that pushed some Bor nodes onto divergent 15 triggered short-term instability not accounted for in the 16 emphasized that while checkpoint finality on Ethereum had remained active throughout, local milestone finality was delayed. “Milestones are a lightweight alternative to checkpoints, enabling faster, deterministic finality for transactions, even before a checkpoint is submitted to Ethereum,” Nailwal said.
“The root cause came from a faulty milestone 17 rolled out fixes on both Heimdall and 18 today, Polygon PoS experienced a disruption where checkpoint finality on Ethereum was still active, but local fast finality on the chain (i. e. milestones) were 19 context: milestones are a lightweight alternative to checkpoints, enabling faster, deterministic… 1 — Sandeep | CEO, Polygon Foundation (※,※) (@sandeepnailwal) September 10, 2025 With these fixes now live, nodes are not stuck, and consensus is finalizing normally.” Nailwal described the event as part of the growing pains of scaling Polygon’s proof-of-stake chain but said each challenge strengthens its resilience.
“There will be growing pains with any ambitious 20 each one makes Polygon PoS stronger on our road to GigaGas throughput,” he said, adding that more upgrades are planned to boost capacity and 21 engineers continue to monitor the network to ensure stability and are investigating how the faulty milestone was 22 the temporary setback, the network has resumed normal operations, with blocks, milestones, and checkpoints processing in real time Polygon’s Reliability Questioned After Finality Bug, TVL Down 87% From Peak Polygon developers have deployed a hard fork to fix a bug that temporarily halted block production on its proof-of-stake chain, restoring the network after several hours of 23 issue, tied to transaction finality, left exchanges and DeFi protocols unable to process deposits or withdrawals as they waited for confirmation 24 outage drew criticism from Polymarket traders, who argued that a blockchain hosting one of the sector’s largest prediction markets should not face such problems.
“It might have gone unnoticed because no one was using it, but this has been going on for about two hours,” one trader posted, pointing to the risk of reversals during the 25 might have gone unnoticed because no one was using it, but this has been going on for about 2 hours on@0xPolygon. It's concerning that @Polymarket is still on this network 2 26 — barnacle (@barnaclebarny) September 10, 2025 TokenPocket, a multichain stablecoin wallet, also paused Polygon transactions after observing that no new blocks had been finalized for over an 27 incident comes just weeks after Polygon’s Heimdall v2 upgrade , designed to cut finality times to five seconds and improve validator 28 update followed the July 1 Bhilai hard fork , which raised throughput to 1,000 transactions per second and integrated Ethereum’s Pectra 29 these efforts, network reliability remains a concern, as Polygon’s total value locked has dropped from a $9.43 billion peak in 2021 to $1.2 billion today, per 30 chain’s native token, POL, has fallen 3.4% on the day and is down 30% year-to-date, trading at $0.27.
Meanwhile, another Ethereum Layer-2, Linea, faced a separate outage earlier today when its mainnet sequencer stalled, causing a 67-minute pause in block 31 Linea has already deployed a fix , developers are questioning whether the two disruptions are 32 has not disclosed the cause of its 33 events highlight the fragility of scaling networks that have become essential to Ethereum’s broader ecosystem.
Story Tags
Latest news and analysis from cryptonews
