Polygon’s proof‑of‑stake (PoS) community suffered a one‑hour outage on July 30 that disrupted apps and customers.
In accordance with Polygon CEO and founder Sandeep Nailwal, the incident didn’t cease block manufacturing.
Nonetheless, QuickNode Standing reported that block manufacturing stopped for one hour at block top 74,592,238, echoing different studies made by customers on X.
Consensus hiccup
In a put up on X, Nailwal stated a number of RPC suppliers “and therefore corresponding apps and customers” confronted points over a two‑to‑three‑hour window. On the identical time, the chain “remained operational and continued to provide blocks and course of person transactions” for unaffected RPCs.
Polygonscan information signifies that the community generated a brand new block two seconds after block 74,592,238, as of press time, regardless of the block explorer displaying stalled block manufacturing at this top.
Nailwal traced the incident to a hotfix and a brief pause on the consensus (Heimdall) layer tied to a current, advanced improve. The execution layer (Bor) continued working, however some RPC nodes fell out of sync after the repair, creating app‑degree failures that felt like a community halt.
He apologized for the top‑person affect and stated Polygon is working with suppliers “to carry everybody on top of things,” anticipating no additional observe‑on points.
Halted block manufacturing
Infrastructure operators described the identical signs. QuickNode reported the mainnet stalled from its vantage level at block top 74,592,238 and warned that the brand new Heimdall v0.2.16 improve was inflicting points with execution purchasers Bor and Erigon.
The corporate paused upgrades “till additional discover,” suggested operators to not proceed, and commenced resyncing full nodes whereas resetting Erigon cases to revive service.
Polygon’s standing web page remoted the fault to the Heimdall‑V2 community. The workforce stated the mainnet Heimdall service grew to become unresponsive, affecting validator and checkpoint visibility by way of Heimdall APIs, however emphasised there was no affect on the Bor layer.
Engineers recognized the problem and deployed a repair earlier than marking the incident resolved.
The timeline reveals how the disruption unfolded and unfold throughout groups. Polygon opened the incident at 09:52 UTC on July 30, recognized the problem by 09:57, and declared it resolved at 11:01.
QuickNode then reported a stall at 11:28, paused the Heimdall v0.2.16 rollout at 11:51 pending steering from the Polygon Basis, and by 15:39 stated it was resyncing and resetting nodes to carry companies again on-line.
Nailwal characterised the episode as a coordination hole between consensus and infrastructure fairly than a protocol failure.