The Sui Network resumed normal operations after the Sui Core Team fixed software issues that caused three separate outages on May 28 and May 29. The disruptions resulted in more than 15 hours of total downtime, temporarily preventing users from processing transactions. The outages originated from a bug introduced in version 1.72 of the network software, which created a flaw in the gas charging mechanism, and a second issue affecting how validators stored randomness-related data during system restarts. Validators implemented corrective updates released by the core development team, restoring blockchain functionality.
Version 1.72 Bug Caused First Six-Hour Outage on May 28
The initial outage occurred on May 28 and lasted approximately six hours and forty-four minutes. Block production stopped entirely during this period, leaving users unable to submit or confirm new transactions. According to the Sui Core Team, the issue originated from a bug introduced in version 1.72 of the network software. The update included a new address balance feature but inadvertently created a flaw within the gas charging mechanism. Validators repeatedly crashed, creating a loop that prevented the network from functioning properly. Engineers released a temporary patch to restore services. The first outage began at approximately 7:00 a.m. Pacific Time on May 28 and concluded around 1:30 p.m.
Second and Third Outages Emerged During Recovery on May 29
A second issue emerged during the morning of May 29, leading to another interruption of blockchain operations. This outage lasted several hours before services were restored. The second outage started near 5:00 a.m. Pacific Time on May 29 and ended around 8:30 a.m. A third disruption occurred later the same day during a scheduled epoch transition. Validators were in the process of restarting systems and deploying the latest software corrections when another previously undiscovered bug surfaced. The newly identified flaw affected the way validators stored randomness-related data during system restarts. The third disruption began at roughly 1:30 p.m. and continued until approximately 7:20 p.m., resulting in repeated service interruptions across two consecutive days.
User Assets Remained Secure Throughout All Disruptions
The network maintained the security of user assets throughout the incidents. Completed transactions remained valid, and no previously finalized transactions were reversed during the outages. The Sui Core Team reported that user funds remained secure throughout all three disruptions, helping users avoid direct financial losses despite the operational interruptions.
AI Tools Accelerated Root Cause Investigation
The Sui Core Team conducted a comprehensive review of the affected systems following the incidents. The investigation revealed weaknesses in several operational areas, prompting developers to implement additional safeguards aimed at improving future reliability and reducing the likelihood of similar failures. The Sui Foundation disclosed that artificial intelligence tools played a significant role during the troubleshooting process. AI-powered systems assisted engineers by analyzing system logs and collecting network diagnostics, enabling faster identification of the underlying causes. AI-assisted analysis helped the development team pinpoint the software defects more efficiently, accelerating the deployment of corrective updates and the restoration of services.
SUI Token Declined 17% During Outage Week
The outages affected market sentiment surrounding the network's native token, SUI. During the week of the disruptions, the token experienced a notable decline in value, falling by approximately 17%. The downturn reflected investor concerns over network reliability during the period of repeated interruptions. With both major software bugs now patched and validators operating normally, network activity has returned to expected levels. The Sui Foundation indicated that future efforts will focus on strengthening stability, improving update procedures, and enhancing protections during validator restarts and software deployments.
FAQ
What caused the Sui Network outages on May 28 and May 29?
The outages were caused by two separate software bugs. The first was introduced in version 1.72 of the network software and created a flaw in the gas charging mechanism, causing validators to repeatedly crash. The second bug affected how validators stored randomness-related data during system restarts.
How long did the Sui Network outages last?
The three outages collectively resulted in more than 15 hours of downtime. The first outage on May 28 lasted approximately six hours and forty-four minutes (7:00 a.m. to 1:30 p.m. Pacific Time). The second outage on May 29 lasted several hours (5:00 a.m. to 8:30 a.m. Pacific Time). The third outage on May 29 lasted from approximately 1:30 p.m. to 7:20 p.m. Pacific Time.
Were user funds affected during the Sui Network outages?
No. The Sui Core Team reported that user funds remained secure throughout all three disruptions. Completed transactions remained valid, and no previously finalized transactions were reversed during the outages.
