Polygon zkEVM Outage Occurs Over 12 Hours Causing Delay In Network Operations

Key Points:

• Polygon zkEVM mainnet Beta faced a 12-hour outage due to sequencing issues stemming from L1 restructuring.
• Despite its launch nearly a year ago, Polygon zkEVM struggles to match competitors’ transaction volumes.
• The Polygon zkEVM outage adds to recent crypto industry outages, with Coinbase and Solana experiencing disruptions.

Polygon announced on March 24th a sequencing issue affecting its zkEVM mainnet beta version due to L1 restructuring, leading to a network outage lasting over 12 hours.

Polygon zkEVM Outage Takes Place Over 12-Hour

The problem arose from difficulties faced by the sequencer of Polygon zkEVM mainnet beta due to L1 reorganization. Efforts are underway to resolve the issue, with a detailed post-mortem analysis planned. It’s crucial to note that this outage solely impacts Polygon zkEVM, excluding Polygon PoS, Polygon CDK, or any chains deployed via Polygon CDK.

This Polygon zkEVM outage comes as the network, launched on March 27, 2023, struggles to match competitors’ transaction volumes despite offering scalability solutions for Ethereum-based decentralized applications (dApps). The data indicates lower transaction activity compared to other Layer-2 protocols.

During the Polygon zkEVM outage, the Layer-2 blockchain failed to sequence or add blocks, with the last block added more than 12 hours before the disruption, according to multiple block explorers.

Crypto Industry Outages Continue: Coinbase, Solana, and Now Polygon zkEVM

The incident adds to a series of recent crypto industry outages, with Coinbase and Solana also experiencing disruptions. A recent Coinbase outage resulted in around $100 billion in market value loss, underscoring the vulnerability of the crypto market. Similarly, Solana encountered a significant outage on Feb. 6, halting block production for over five hours before validators restored the network.

Polygon’s team is actively addressing the Polygon zkEVM outage, promising a second-generation release in the coming weeks. However, the incident raises concerns about the protocol’s reliability amid intensifying competition within the Layer-2 ecosystem.