SUI suffers 15-hour outage

Sui’s latest outage was not just another crypto headline. On May 28, 2026, the network stopped processing transactions and remained impaired for roughly 15 hours, according to Sui’s public status page and contemporaneous reporting from CoinDesk. The interruption was significant enough that media coverage described it as the second Sui outage of the year, while Sui’s own incident history showed the network needed validator participation to recover. For a chain marketed on speed and scale, the episode put basic operational reliability back at the center of the conversation. ### When did the outage happen, and how long did it last? May 28, 2026 is the key date. Sui’s public status page showed the team investigating an issue beginning at 07:15 PDT on May 28, and outside reporting on the same day said transaction processing had ground to a halt. CoinDesk reported the outage as a fresh network failure and said it was the second such incident for Sui in 2026. Roughly 15 hours is the figure that matters. (coindesk.com) That number aligns with the podcast discussion cited in the prompt, and it fits the broad timeline of the May 28 incident reflected in Sui’s status materials and third-party reporting. Sui’s incident history later said the event was resolved after validator participation recovered. ### What actually broke on the network? CoinDesk reported that transactions on Sui “ground to a halt,” which is the clearest plain-English description of what users would have experienced. (status.sui.io) The Block, in separate reporting on the same stretch of instability, described the chain as experiencing a “major outage” and said the network had stopped producing blocks. (status.sui.io) Sui’s own status history did not frame the incident in promotional language. Instead, it focused on validator recovery, saying participation climbed to as much as 93% of stake before the issue was marked resolved. That detail matters because it shows the recovery depended on enough of the validator set returning to coordinated operation. ### Why did people focus on the 93% validator figure? (coindesk.com) The 93% number came directly from Sui’s incident history. In proof-of-stake systems, validator participation is a concrete sign of whether the network is functioning normally again, because validators are the parties confirming blocks and keeping the chain moving. Sui’s update said the team would continue monitoring the network even after marking the incident resolved. (status.sui.io) The figure also gave observers a measurable recovery marker instead of a vague assurance. Rather than saying only that service was back, Sui disclosed a participation threshold that suggested the chain had regained broad validator support. That is one reason the number circulated in later discussion of the outage. ### Was this an isolated incident? January 2026 is part of the answer. (status.sui.io) The Block reported earlier this year that Sui had suffered another network stall in mid-January, when developers said the Layer 1 was “currently experiencing a network stall” and were working on a fix. May 28, 2026 made that pattern harder to ignore. (status.sui.io) CoinDesk explicitly described the late-May event as the second time this year that the Sui network had suffered an outage. That does not by itself establish a long-term trend, but it does place the 15-hour interruption in a shorter record of repeated disruptions. (theblock.co) ### Where should readers look next? Sui’s status page and incident-history page are the main public records to watch. Those pages are where the network posted the May 28 investigation notice and the later resolution update referencing 93% validator participation. Mysten Labs, Sui’s core developer ecosystem, and major block explorers such as Suiscan are also likely to reflect the next material update if another disruption occurs. (coindesk.com) As of June 3, 2026, the most concrete public record of this episode remains the May 28 incident trail on Sui’s own status infrastructure and the contemporaneous reporting that documented the halt in transaction processing. (status.sui.io)