Sui mainnet outage stretches into second day amid settlement layer issues
Tech & Launches ·
The Sui network has recorded a Major Outage for two straight days, with the blockchain explorer showing no new blocks produced for over an hour at last check.
Sui's official X account confirmed the mainnet was experiencing a network stall and that network activity may be paused, adding that the Sui Core team was actively investigating and would share updates and an incident review once available, according to the announcement. Sui Status attributed the problem to Mainnet settlement, and the outage has now persisted across two consecutive days.
This is not an isolated event. The network experienced a second stall in five months, following a six-hour outage on Thursday that was caused by a bug in version 1.72, per The Block. The recurrence of downtime within a short window has drawn attention to the reliability of Sui's settlement layer specifically, since both incidents trace back to issues at that level of the network rather than isolated application bugs.
The disruption has coincided with a sharp move in the SUI token, which dropped 20% over the week and ranked among the worst performers among the top 100 assets, as reported by wublockchain.xyz. Whether the price decline is directly tied to the outage or reflects broader market conditions has not been established in available reporting.
Separately, researchers have identified a "TrapDoor" attack using 34 malicious npm, PyPI and Rust packages designed to steal wallets and cloud credentials from developers building on Solana, Sui and Aptos. It remains unclear whether this supply-chain campaign has any connection to the settlement layer problems behind the current outage, and no link between the two has been established in the material reviewed.
What remains unresolved is the root cause of the Mainnet settlement issue and how it relates, if at all, to the bug identified in version 1.72 from Thursday's earlier stall. The Sui Core team has not yet published the promised incident review, and the exact duration of the current halt beyond the confirmed hour-plus gap in block production has not been disclosed. Whether validators have coordinated a fix or restart timeline is also not yet known.