The cascade began on May 28 when a bug in gas charging logic, introduced as part of the v1.72 protocol release, sent all validators into a crash loop. Validators are the node operators responsible for confirming transactions; when enough of them fail simultaneously, the network stalls. That first halt lasted approximately six hours and 44 minutes, from roughly 7am to 1:30pm PT.

The network then entered its second halt as teams worked to address the failure. From approximately 5am to 8:30am PT on May 29, the network remained down while an emergency patch was being deployed, a window of roughly three and a half hours. The patch restored block production by around 8:30am PT, but the fix carried a documented risk: the Sui team acknowledged at the time that certain edge cases could bypass the patch and re-trigger the same InsufficientFundsForWithdraw underflow error.

Shortly after 1:30pm PT on May 29, during the rollout of a longer-term fix, the network halted a third time. Validators restarting to load the new software triggered a failure in randomness initialization, a process required at the start of each epoch (a fixed time period used to coordinate validator responsibilities). A separate, previously undiscovered bug prevented that failure from being saved to disk, leaving the network in a deadlock. The third halt lasted approximately five hours and 50 minutes.

The v1.72 release was directly tied to Sui's May 20 launch of gasless stablecoin transfers, which allow peer-to-peer stablecoin payments without requiring the sender to hold SUI tokens to cover transaction fees. The gas charging logic changes needed to support that feature were the origin of the first two halts. In its May 31 post-mortem, the Sui Foundation acknowledged the gap clearly, writing that gas charging logic deserves the same rigorous invariant testing applied to its Move virtual machine and consensus code. The Foundation identified four areas for improvement: stronger end-of-epoch fallback mechanisms, more adversarial testing of gas logic, better failure containment so individual validators can skip problematic inputs rather than crashing entirely, and expanded use of AI-driven diagnostics.

On that last point, the Foundation credited AI tooling with speeding up incident response. "AI agents with access to production state, capable of interactively querying validator logs, inspecting cluster state, and assembling metrics on demand, materially accelerated diagnosis during this week's incidents," the Foundation wrote. The claim comes from the Foundation's own post-mortem and has not been independently confirmed. For developers evaluating AI tooling in production blockchain environments, the detail is worth tracking. This relevance extends to South Asian developer communities in particular, where adoption of agentic AI tooling in blockchain workflows is accelerating and where India's standing as the world's second-largest remittance corridor by inflow makes infrastructure reliability a practical operational concern.

The market impact was measurable. SUI's price fell roughly 8 percent during the outage window, dropping from approximately $0.99 to a low of $0.90 and breaking below the $1.00 support level it had held. When factoring in losses tied to the prior January 2026 outage, SUI's weekly decline reached approximately 19 percent. Approximately $1.88 million in leveraged positions were liquidated across the three halts, with $1.72 million in long positions and $158,000 in shorts. The assets behind that exposure were concentrated in Sui's largest DeFi protocols: Scallop (approximately $600 million in total value locked), Cetus (approximately $500 million), and Navi Protocol (approximately $400 million). The Sui Foundation confirmed that no certified transactions were reverted, no network fork occurred, and no user funds were lost.

Sui's architecture is designed to prioritize safety over continuous operation, meaning the network will stop rather than allow inconsistent state. For holders, that distinction matters; assets were inaccessible but not at risk.

The regional stakes are significant. Just weeks before the outages, Nigerian fintech company Paga announced at Sui Live in Miami that it would build enterprise crypto products on Sui, including dollar-denominated accounts backed by USDsui, a Sui-native stablecoin. Paga and Sui also plan to tokenize real-world assets including real estate, bonds, and solar projects. According to Paga, the company processed $11 billion in payments and around 170 million transactions in 2025 alone, serving users across Nigeria and other African markets.

The gasless stablecoin feature at the center of the v1.72 failure is also the feature most directly relevant to African financial infrastructure, where high remittance costs and local currency volatility make dollar-denominated peer-to-peer payments particularly valuable. A network that halts for over 16 cumulative hours in a 48-hour window is a liability for users in markets where internet access is inconsistent and financial access is already constrained. The Sui Foundation has launched a developer hub in Nigeria to expand its ecosystem presence there, a trust-building initiative that repeated infrastructure failures directly complicate.

This is Sui's third major outage since November 2024. The two events preceding this week's, one in November 2024 caused by a congestion control bug in newly deployed code and one in January 2026 caused by validator consensus divergence, share the same basic pattern: a protocol upgrade introduces or exposes a bug, validators crash, and the network requires coordinated emergency intervention to restart.

With approximately $527 to $542 million in total value locked across 137 DeFi protocols as of late May 2026, the cost of each hour offline extends well beyond SUI token price.

Whether the improvements outlined in the post-mortem close the gap before the next major upgrade will be the more meaningful test.