- Polygon’s Heimdall consensus layer was down for about one hour today due to a consensus error.
- The Bor layer remained live, and transactions continued to be processed without interruption.
- The error occurred weeks after the network’s most technically complex Heimdall V2 upgrade.
Polygon, one of Ethereum’s leading Layer 2 scaling solutions, experienced a temporary outage on Wednesday, July 30, 2025, when its Heimdall consensus layer stopped responding for roughly one hour.
The interruption was notable because it followed closely on the heels of the network’s largest technical upgrade since launch in 2020.
Validator exit triggered the rare failure
The outage began at approximately 09:30 UTC when Heimdall — the consensus layer responsible for managing validators and synchronizing Polygon’s Proof-of-Stake chain with Ethereum — unexpectedly became unresponsive.
According to an official statement from the Polygon Foundation, the incident was caused by a validator unexpectedly leaving the network — an uncommon event that the system was not designed to handle gracefully.
That unusual validator exit produced a “consensus error” that halted checkpointing and temporarily stopped chain progression.
Polygon confirmed that the chain’s liveness — its ability to accept and execute transactions — remained intact during the disruption because the Bor execution layer continued to produce blocks without interruption.
Bor stays live, but RPCs wobble
Although the network’s core transaction processing continued, the user-facing experience was disrupted.
In an update from the Polygon Foundation, several RPC providers reported synchronization inconsistencies across their Bor nodes due to the outage.
Those inconsistencies confused users and decentralized applications that rely on explorers and API endpoints to verify network status and transactions in real time.
As a result, some users mistakenly believed the entire network had gone offline.
Polymarket, a major prediction market platform built on Polygon, briefly displayed error messages during the downtime, which amplified concerns that funds or trades were stuck.
Polygon’s team later clarified that while validator and checkpoint data were temporarily unavailable, the chain itself never stopped processing transactions.
In their words, the situation “triggered a false alarm” caused by limited handling of validator exits.
An error weeks after a major upgrade
The timing of the event was significant. Earlier in July, Polygon launched Heimdall V2, an upgrade built on CometBFT and Cosmos-SDK v0.50.
The upgrade aimed to reduce finalization times to roughly five seconds and improve scalability.
However, it also introduced additional complexity into the system, creating new potential points of failure.
Polygon co-founder Sandeep Nailwal described the upgrade as the most technically complex hard fork since the protocol’s inception in 2020.
The outage has raised questions about whether the complexity introduced with Heimdall V2 exceeded the system’s preparedness for rare scenarios.
Polygon has faced similar disruptions in the past. In March 2022, a Heimdall V1 bug caused several hours of downtime, and in March 2024 Polygon’s zkEVM network experienced a roughly 10-hour outage related to sequencing issues.
User trust under pressure
The incident occurred at a time when uptime and reliability are critical. With more than $1.4 billion in total value locked on Polygon, many users depend on the protocol’s availability to move and withdraw funds without interruption.
Although transactions continued behind the scenes, RPC and explorer issues dented user confidence and created visible friction.
Polygon’s native token, POL, fell nearly 3% during the incident and traded around $0.22, reflecting trader unease amid rising Layer 2 competition.
Even when a chain remains technically live, the perception of downtime — particularly among traders — can have equally damaging effects.
Other blockchains have faced comparable problems: just a day earlier, Hyperliquid reported an outage caused by traffic spikes, and Solana has experienced multiple outages over time that led to economic losses for some DeFi users.
Polygon says a fix is in place
Polygon’s development team acted swiftly, identified the issue, and deployed an update within an hour. By 11:01 UTC, the Heimdall consensus layer was fully restored.
The Polygon Foundation has since confirmed it is working closely with RPC providers to resolve any lingering synchronization issues and to return full service availability to all users.
The team has not yet provided details about whether future upgrades will include additional mechanisms to better handle unexpected validator exits.