Starknet mainnet experienced another disruption on July 23, 2026, lasting over two hours and renewing concerns over layer-2 network stability. The team confirmed the outage on X, stating engineers were working to restore operations, but did not disclose the root cause. As a zero-knowledge rollup-based Ethereum L2, Starknet processes transactions off-chain and posts proofs to Ethereum, aiming for lower fees and higher throughput. The outage affected DeFi, gaming, and smart contract activity, with users reporting stalled transactions and delayed confirmations.
Outage Details and Recovery
As of update, downtime exceeded two hours. This latest incident follows multiple mainnet disruptions in 2025 — including a halt during the Grinta v0.14.0 upgrade that caused two chain reorgs, reverting nearly one hour of activity and forcing users to resubmit transactions. An earlier report attributed a nine-hour Grinta-related outage to Ethereum RPC provider failures and sequencer software bugs. Another multi-hour outage earlier in 2025 was linked to sequencer instability.
Market Reaction Surprisingly Calm
Despite the technical setback, the STRK token price held firm during the outage, according to CoinMarketCap data. Analysts suggest the market may have priced in Starknet's operational risks, or short-term selling pressure was absorbed by fresh bids. However, developer confidence is eroding — repeated downtime forces teams building reliable applications to reassess deployment risks. Starknet previously committed to architectural improvements and enhanced monitoring, yet recurring failures underscore ongoing challenges.
BTCFi Ambitions vs. Reliability
Beyond Ethereum scaling, Starknet has expanded into Bitcoin-focused DeFi (BTCFi), positioning itself as infrastructure for Bitcoin-linked financial apps within Ethereum. The latest outage, though brief, casts doubt on its BTCFi ambitions. The community is closely watching whether recovery speed improves as network usage grows. Engineers are focused on restoring full functionality, and the team has not clarified whether this incident relates to previous sequencer or infrastructure issues.