Close up on logo of TON Toncoin on the screen of an exchange. Source: maurice norbert - stock.adobe.com

Key Takeaways:

TON blockchain suffered a 40-minute outage on June 1 due to a masterchain dispatch queue error, quickly resolved with minimal validator updates.
No user funds or transactions were affected during the disruption, ensuring network integrity.
Despite recurring outages, investor confidence remains strong, with TON securing $400M in VC funding as of March 2025.

The Open Network (TON), a layer-1 blockchain tied to the Telegram messaging app, experienced a brief outage on June 1 due to an error in the masterchain dispatch queue.

Block production halted at 12:51 UTC but was restored within 40 minutes after a quick fix was applied to just a few validators.

Block production has been restored ✅

A quick fix was released, and updating only a few master chain validators was sufficient to resume block production.

The incident was related to an error in the processing of the masterchain dispatch queue.

We will release a technical…
— TON 💎 (@ton_blockchain) June 1, 2025

Developers confirmed that no user funds were affected and that all pending transactions remained secure.

Although the issue was resolved swiftly, it’s not the first time TON has faced technical disruptions.

In August 2024, the network suffered multiple outages linked to high congestion caused by DOGS memecoin activity.

On August 27, block production paused at workchain block 45,341,899 and resumed hours later, only to crash again due to continued traffic overload.

Another outage occurred the following day at block 45,350,522 and lasted roughly six hours.

Despite these technical setbacks, TON’s popularity continues to grow.

In March 2025, it raised $400 million from top venture capital firms including Sequoia Capital and Draper Associates.

The incident highlights the challenges high-throughput blockchains face as they scale, though TON’s quick recovery and ongoing investment interest signal strong institutional confidence.

A full technical report on the June 1 incident is expected soon.