Understanding Polygon's outage history helps developers, traders, and dApp operators assess network reliability and plan for redundancy. This page covers every significant Polygon PoS network disruption, including root-cause analysis and resolution timelines.
July 2025: Heimdall Consensus Bug Outage
On July 30, 2025, the Polygon PoS network experienced approximately one hour of downtime caused by a consensus bug in Heimdall, the network's consensus layer. The incident was triggered when a validator exit activated a latent bug introduced during the Heimdall V2 upgrade — the most technically complex hard fork in Polygon's history.
The upgrade was designed to reduce finality times and enhance scalability, but introduced new system complexities that contributed to the bug's occurrence. The Polygon native token POL dipped approximately 3% during the outage before quickly rebounding. The development team deployed a patch within the hour, restoring full network functionality by 11:01 UTC.
This was the second major technical disruption in 2025 and the third since the Heimdall V1 launch in 2022.
December 2025: Bor RPC Partial Disruption
Between December 17 and 18, 2025, Polygon PoS experienced a partial service disruption affecting Bor, the block-producing and transaction execution client. The issue primarily impacted RPC availability, leading to stalled responses across several infrastructure providers. Importantly, the chain itself never went offline — block production continued uninterrupted, validators remained active, and transactions continued to be processed throughout the incident.
The incident was not a consensus failure. It emerged at the execution layer, where multiple Bor nodes stalled simultaneously. Once the issue was detected, Polygon engineers activated a war room to coordinate investigation and remediation across teams and node operators. A targeted patch was deployed, after which nodes began resynchronizing and validators progressively returned to quorum.
What Triggers Polygon Network Outages?
Based on the recorded incident history, Polygon outages have generally originated from two sources:
- Consensus layer bugs — issues in Heimdall that affect validator coordination and finality
- Execution layer stalls — Bor node crashes or RPC endpoint failures that degrade user-facing access without halting block production
- Hard fork complexity — major protocol upgrades introducing new code paths that may expose edge-case bugs under production load
For most users, RPC availability defines whether a blockchain feels online. Even during the December 2025 incident, the Polygon PoS chain continued producing blocks — but degraded RPC access impacted wallets, dApps, explorers, and exchanges that relied on affected endpoints. This distinction between chain liveness and RPC availability is critical for infrastructure planning.
Consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et justo duo dolores et ea rebum.
Vulputate velit esse molestie consequat, vel illum dolore eu feugiat nulla facilisis.
Lorem ipsum dolor sit amet.