The Sui network has resumed normal operation, and the official will release a complete incident review.

2026-01-15 01:06:10

Abstract generation in progress

【Blockchain Rhythm】The Sui mainnet experienced a network outage yesterday, causing transaction processing to be hindered. Users encountered delays or unresponsive situations when using dApps such as Slush and SuiScan, and the overall network liquidity efficiency significantly declined.

The good news is that the Sui core team responded quickly and actively worked on repairs. At 5:24 AM today, the official announcement confirmed that the network has fully recovered and returned to normal. Currently, transaction circulation is back on track, and all metrics are operating smoothly. If your application still has issues, try refreshing the page or clearing the cache, which usually resolves residual problems.

Regarding the specific cause and technical details of this outage, the official has promised to release a detailed incident review report in the coming days. Interested friends can follow subsequent updates.

SUI0,92%

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

9 Likes

Reward
9
6
Repost
Share

Comment

0/400

CascadingDipBuyer

· 9h ago

This time it was really a bit scary, but luckily it recovered quickly. However, I need to review the report and make sure it's not some other issue. Why does Sui always cause trouble? Need to reflect on this properly. I almost thought my coins were gone yesterday, my mood collapsed. Fortunately, the official fixed it in time. Just refresh the cache? I've tried that a long time ago, let's wait for the official review. This frequency is exhausting; I hope it doesn't happen again. The official needs to explain clearly; user trust is not easy to earn. Another network failure, Web3 infrastructure is still not stable enough. By the way, is Sui's technical architecture really problematic, or is it just like this? A false alarm, but the lesson must be remembered.

View OriginalReply0

OnchainDetectiveBing

· 9h ago

Breaking down and fixing again, this speed is pretty good Yesterday, I thought it was all over, but I woke up and it was fine Waiting to see the review report, need to figure out what exactly happened It's good to recover quickly, just don't let it happen again Refreshing the cache really works, it solved problems for several people The ecosystem is still in the improvement phase, these small glitches are unavoidable Fixed by around five o'clock, the team still has some capability But the key is to look at the root cause, hopefully it's not the same pitfall

View OriginalReply0

gm_or_ngmi

· 9h ago

Oh no, here we go again. Luckily, the reaction was fairly quick. Yesterday was really frustrating, but now it's better, so that's good. Refreshing cache is a great way to save the day, but I still want to see what they have to say. Sui was lucky this time and wasn't criticized for too long. Let's wait for the review to see what the real reason was. These things can't always happen like this. This speed is much better than some projects; gotta give some recognition.

View OriginalReply0

BTCRetirementFund

· 9h ago

Haha, I was still criticizing Sui yesterday, and today it's fine? The reaction speed is indeed impressive. I'd like to see the review report to find out where the bottleneck was. It's the old trick of clearing cache again. When can we finally put an end to this? It scared me to death, thought I was going to suffer another heavy loss. The speed is good, but this kind of thing keeps happening from time to time, it's exhausting.

View OriginalReply0

IfOldLeeksDon’tTas