Starknet Network Outage Hits Ethereum L2: What Happened and What's Next » CoinEagle

Key Points

• Starknet experienced a prolonged network halt after block delays escalated into a full outage.
• Developers are investigating a core execution issue with no recovery timeline announced.

Starknet, a scaling network built on Ethereum, experienced several hours of downtime with no confirmed time for recovery.

The disruption started with delayed block production before progressing into a complete network halt, leaving transactions unprocessed.

The development team acknowledged the issue and stated that work is ongoing, but decentralized applications on the network remain affected.

Cause and Technical Status

Users first reported abnormal behavior on January 5 when new blocks appeared more slowly than usual.

An update on the network’s status page at 09:53 UTC confirmed that block production was taking longer than expected, indicating early degradation.

Roughly 50 minutes later, developers reported they were debugging a mismatch between block execution and the proving system, linked to specific transactions.

Following this discovery, block production stopped entirely, and users reported that no new transactions were being confirmed across the network.

As of midday UTC, the outage had lasted more than two hours, and the official status page continued to list the incident as unresolved with no estimated recovery time.

This event occurred shortly after the network recorded more than $365 million in total consensus value, reflecting a recent rise in activity prior to the halt.

Impact on Users and Community Response

During the downtime, all on-chain activity was effectively frozen, preventing users from sending transactions or interacting with decentralized applications.

The outage prompted frustration among traders, developers, and users, while social media reactions ranged from criticism to satire referencing previous incidents.

Several commentators also recalled earlier disruptions, including a major upgrade in 2025 that caused similar reliability concerns.

Beyond the initial acknowledgment, the development team has not released additional public updates, and the network remains idle until block production resumes.