In a post on X, Nailwal said several RPC providers “and hence corresponding apps and users” faced issues over a two‑to‑three‑hour window. At the same time, the chain “remained operational and continued to produce blocks and process user transactions” for unaffected RPCs.
Nailwal traced the incident to a hotfix and a temporary pause on the consensus (Heimdall) layer tied to a recent, complex upgrade. The execution layer (Bor) continued running, but some RPC nodes fell out of sync after the fix, creating app‑level failures that felt like a network halt.
He apologized for the end‑user impact and said Polygon is working with providers “to bring everyone up to speed,” expecting no further follow‑on issues.
The company paused upgrades “until further notice,” advised operators not to proceed, and began resyncing full nodes while resetting Erigon instances to restore service.
Engineers identified the issue and deployed a fix before marking the incident resolved.
The timeline shows how the disruption unfolded and spread across teams. Polygon opened the incident at 09:52 UTC on July 30, identified the issue 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 guidance from the Polygon Foundation, and by 15:39 said it was resyncing and resetting nodes to bring services back online.
Nailwal characterized the episode as a coordination gap between consensus and infrastructure rather than a protocol failure.
