Starknet resumed block production after a multi-hour outage on 2 September 2025, restoring the ZK-rollup network following a reorganisation from block 1,960,612; transactions submitted between 02:23–04:36 UTC were excluded and must be resubmitted by users and dApps.
-
Starknet restored block production after downtime between 02:23 and 04:36 UTC on 2 Sep 2025.
-
Developers committed a reorganisation from block 1,960,612; excluded transactions require resubmission.
-
Team will publish a full retrospective with timeline, root cause analysis and prevention measures.
Starknet outage restored: Starknet resumed operations after a reorg; check resubmission steps and updates from COINOTAG for guidance and timeline.
What happened during the Starknet outage?
Starknet outage halted block production for roughly two hours on 02 September 2025, disrupting transaction processing across the Layer 2 network. Developers performed a chain reorganisation starting at block 1,960,612, excluding transactions submitted between 02:23 and 04:36 UTC that now require resubmission.
How did Starknet restore block production and stabilise services?
Starknet engineers prioritised restoring consensus and resuming block production. Most RPC providers returned to service quickly, while remaining nodes upgraded software to stabilise the network. Monitoring showed transaction confirmations normalised shortly after blocks resumed.
The team confirmed network security was not compromised and committed to publishing a full retrospective with timeline, root cause and long-term prevention steps.
Starknet is back online and fully operational. Block production is back to normal. Most RPC providers are up-and-running, and the remaining ones will upgrade shortly. To restore service, transactions submitted between 2:23am and 4:36am UTC were not processed. A reorg from block… Starknet (@Starknet) September 2, 2025
Why were transactions excluded and what must users do?
Transactions submitted during the outage window were excluded by a reorganisation to ensure consistent state across validators. Users and dApp operators must identify affected transactions and resubmit them. Failure to resubmit will leave intended state changes unconfirmed on Starknet.
How to resubmit excluded transactions (short checklist)
- Identify transactions submitted between 02:23–04:36 UTC.
- Check your wallet or dApp logs for pending or failed TX hashes.
- Resubmit transactions with current gas parameters and correct nonces.
- Monitor confirmations via your RPC provider and application logs.
- Contact your node/RPC provider support if issues persist.
Frequently Asked Questions
How long was Starknet down and when did it resume?
The network experienced downtime between 02:23 and 04:36 UTC on 2 September 2025. Block production resumed after developers executed a reorganisation beginning at block 1,960,612.
Do users need to take action after the reorg?
Yes. Users and dApp operators must locate transactions submitted during the outage window and resubmit them. Check wallet histories and application logs to identify affected TXs and confirm new submissions.
Key Takeaways
- Immediate restoration: Starknet resumed block production and most RPC providers returned to service quickly.
- Reorg impact: A reorganisation from block 1,960,612 excluded transactions between 02:23–04:36 UTC; these must be resubmitted.
- Transparency commitment: The Starknet team will publish a full retrospective with timeline, root cause and prevention measures to strengthen reliability.
Conclusion
Starknet has resumed operations after a multi-hour outage and chain reorganisation, with developers assuring no security breach and promising a detailed retrospective. Users should identify and resubmit excluded transactions promptly. COINOTAG will monitor updates and publish the official timeline and root cause analysis when released.
By: COINOTAG (reporting by Maxwell Mutuma) — Published: 02 September 2025, 10:40:18 GMT
