Two major Ethereum layer-2 networks, Linea and Polygon, experienced operational setbacks on Sept. 10, adding to concerns about the reliability of scaling solutions.
The incidents come around a week after Starknet, another Ethereum layer-2 network, suffered a four-hour outage, underlining the challenges of keeping rollup systems consistently online.
Linea outage coincides with airdrop plan
Linea, the Ethereum Layer 2 network developed by Consensys, has returned to normal operations following a nearly hour-long unexpected pause in block production.
Data reviewed from Lineascan confirmed a 46-minute gap between blocks 23,144,386 and 23,145,387 before the system returned online.
The disruption was tied to reduced performance from the mainnet sequencer, which stalled activity for more than 40 minutes.
Although the development team has not released an official explanation, Linea’s public status tracker now lists all services as fully functional.
The timing of the incident drew attention because it came just hours before Linea’s token airdrop. The project confirmed last week that the initial claim window for LINEA tokens would open later today.
Notably, anticipation around the launch has attracted malicious actors. In recent days, community members have been targeted by phishing scams, prompting Linea to publish an advisory warning users to remain vigilant.
5 Days to Smarter Crypto Moves
Learn how pros avoid bagholding, spot insider front-runs, and capture alpha — before it’s too late.
Brought to you by CryptoSlate
Despite this turbulence, community interest in Linea remains strong. Data from L2Beat shows that the total value secured on the network increased more than 20% in the past week to around $1.7 billion.
Polygon outage
On the other hand, Polygon’s Foundation announced on X that the network is facing a “temporary delay in finality.”
According to the Foundation:
“While the chain continues to run and blocks and checkpoints are produced, there is currently a 10-15 minute delay in finality due to a milestone issue.”
The project’s status page confirmed that the issue was caused by a bug that affected its Bor and Erigon nodes.
It further stated that this issue impacted some Remote Procedure Call (RPC) services, which is causing the finality delay.
Meanwhile, a fix has been identified and deployed across the validator network as of press time.
Mentioned in this article
