Monday, November 16, 2026

No, TON is producing masterchain blocks

Its newest masterchain block, number 105,719,602, was made 2 s before our check at 02:16 UTC, by the chain's own clock. It normally makes one every 411 ms.

Read from the chain just now

Each mark is a minute of masterchain blocks; a shorter mark means fewer than normal. Hatched stretches are halts we confirmed. Point at the rail or use the arrow keys to read it.

411 msnormal time between masterchain blocks
403 msaverage over the last hour
Instantfinalitymasterchain BFT
532days since the last halt
100%uptime we measured, last 3 days
100%on one client, single implementation

Halts over time

Every halt and finality stall on record for TON since 2024: from postmortems, status pages and news reports, plus the ones we measured ourselves. Point at a dot, or focus the rail and use the arrow keys; Enter opens the incident.

We have measured TON ourselves since 12 Nov 2026; anything earlier is from the public record.

Block production, hour by hour

Average time between masterchain blocks for each hour over the last 7 days, or since we started measuring on 12 Nov 2026. The dashed line is the normal pace. Red hours contain a halt; empty hours are gaps in our sampling.

0 ms411 ms822 ms12 Nov 21:00 UTC: 413 ms per masterchain block12 Nov 22:00 UTC: 413 ms per masterchain block12 Nov 23:00 UTC: 411 ms per masterchain blockFri 1313 Nov 00:00 UTC: 409 ms per masterchain block13 Nov 01:00 UTC: 408 ms per masterchain block13 Nov 02:00 UTC: 409 ms per masterchain block13 Nov 03:00 UTC: 408 ms per masterchain block13 Nov 04:00 UTC: 408 ms per masterchain block13 Nov 05:00 UTC: 408 ms per masterchain block13 Nov 06:00 UTC: 411 ms per masterchain block13 Nov 07:00 UTC: 411 ms per masterchain block13 Nov 08:00 UTC: 411 ms per masterchain block13 Nov 09:00 UTC: 411 ms per masterchain block13 Nov 10:00 UTC: 413 ms per masterchain block13 Nov 11:00 UTC: 412 ms per masterchain block13 Nov 12:00 UTC: 412 ms per masterchain block13 Nov 13:00 UTC: 412 ms per masterchain block13 Nov 14:00 UTC: 415 ms per masterchain block13 Nov 15:00 UTC: 415 ms per masterchain block13 Nov 16:00 UTC: 413 ms per masterchain block13 Nov 17:00 UTC: 413 ms per masterchain block13 Nov 18:00 UTC: 414 ms per masterchain block13 Nov 19:00 UTC: 413 ms per masterchain block13 Nov 20:00 UTC: 413 ms per masterchain block13 Nov 21:00 UTC: 414 ms per masterchain block13 Nov 22:00 UTC: 412 ms per masterchain block13 Nov 23:00 UTC: 412 ms per masterchain blockSat 1414 Nov 00:00 UTC: 412 ms per masterchain block14 Nov 01:00 UTC: 413 ms per masterchain block14 Nov 02:00 UTC: 411 ms per masterchain block14 Nov 03:00 UTC: 411 ms per masterchain block14 Nov 04:00 UTC: 413 ms per masterchain block14 Nov 05:00 UTC: 412 ms per masterchain block14 Nov 06:00 UTC: 412 ms per masterchain block14 Nov 07:00 UTC: 413 ms per masterchain block14 Nov 08:00 UTC: 415 ms per masterchain block14 Nov 09:00 UTC: 413 ms per masterchain block14 Nov 10:00 UTC: 413 ms per masterchain block14 Nov 11:00 UTC: 415 ms per masterchain block14 Nov 12:00 UTC: 415 ms per masterchain block14 Nov 13:00 UTC: 410 ms per masterchain block14 Nov 14:00 UTC: 412 ms per masterchain block14 Nov 15:00 UTC: 414 ms per masterchain block14 Nov 16:00 UTC: 415 ms per masterchain block14 Nov 17:00 UTC: 411 ms per masterchain block14 Nov 18:00 UTC: 409 ms per masterchain block14 Nov 19:00 UTC: 408 ms per masterchain block14 Nov 20:00 UTC: 407 ms per masterchain block14 Nov 21:00 UTC: 406 ms per masterchain block14 Nov 22:00 UTC: 406 ms per masterchain block14 Nov 23:00 UTC: 404 ms per masterchain blockSun 1515 Nov 00:00 UTC: 405 ms per masterchain block15 Nov 01:00 UTC: 404 ms per masterchain block15 Nov 02:00 UTC: 404 ms per masterchain block15 Nov 03:00 UTC: 405 ms per masterchain block15 Nov 04:00 UTC: 404 ms per masterchain block15 Nov 05:00 UTC: 404 ms per masterchain block15 Nov 06:00 UTC: 408 ms per masterchain block15 Nov 07:00 UTC: 410 ms per masterchain block15 Nov 08:00 UTC: 410 ms per masterchain block15 Nov 09:00 UTC: 411 ms per masterchain block15 Nov 10:00 UTC: 411 ms per masterchain block15 Nov 11:00 UTC: 410 ms per masterchain block15 Nov 12:00 UTC: 413 ms per masterchain block15 Nov 13:00 UTC: 412 ms per masterchain block15 Nov 14:00 UTC: 410 ms per masterchain block15 Nov 15:00 UTC: 412 ms per masterchain block15 Nov 16:00 UTC: 412 ms per masterchain block15 Nov 17:00 UTC: 411 ms per masterchain block15 Nov 18:00 UTC: 411 ms per masterchain block15 Nov 19:00 UTC: 412 ms per masterchain block15 Nov 20:00 UTC: 411 ms per masterchain block15 Nov 21:00 UTC: 410 ms per masterchain block15 Nov 22:00 UTC: 410 ms per masterchain block15 Nov 23:00 UTC: 409 ms per masterchain blockMon 1616 Nov 00:00 UTC: 406 ms per masterchain block16 Nov 01:00 UTC: 404 ms per masterchain block16 Nov 02:00 UTC: 403 ms per masterchain blocknormal 411 ms

Halts we detected

None so far. We have been measuring since 12 Nov 2026.

The public record since 2024

From postmortems, status pages and news reports.

DateTypeDurationWhat happenedSources
1 Jun 2025, 12:51 UTCHalt≈40 minAn error in processing the masterchain dispatch queue stopped block production; a quick patch to a few masterchain validators restored it.
Note on times12:51 UTC is when TON announced the issue, not necessarily when the halt began; the ~40 min is from identification to restoration.
cointelegraph.com
28 Aug 2024, 19:19 UTCHalt6.2 hA second halt from heavy load attributed to DOGS minting; validators had to update and restart their nodes.theblock.co
27 Aug 2024, 22:11 UTCHalt≈7.3 hLoad from the DOGS memecoin left several validators unable to clean old transactions from their databases, so they lost consensus; validators restarted to recover.
Note on timesStart per Tonscan via The Block. The 05:30 UTC end is TON Foundation's announcement as quoted in search results, and the coordinated restart was at 04:00 UTC. Reported durations range from 3 to 7 h.
theblock.co

Client software

TON node (C++) Single implementation

Validators run the reference C++ node from the TON core team.

ChainReport review of official repositories and docs, 12 Nov 2026. Compare all chains

Compare

Embed this status

Show the live TON status in your docs, dashboard or README.

Is TON down? Live status by ChainReport

The badge updates about once a minute and links back to this page. Feed for TON incidents: Atom.

Links

We read TON from two places: first source TON Center and second source TonAPI.

Other chains

Also on the Network Desk for TON

How this works and where the data comes from

What we measure. Every minute a server job asks each chain for its newest block and reads the timestamp the chain itself put in that block. "Last block" is now minus that timestamp, so it is accurate even if our own checks run late. "Last hour" is the average spacing between blocks over the past hour, also from block timestamps.

When we call a halt. A chain counts as halted when no new block has appeared for much longer than normal. The limit is set per chain: 2 minutes for most fast chains, 5–7 minutes for Scroll, ZKsync and Cardano, 14 minutes for Dogecoin, 30 minutes for Litecoin and 2 hours for Bitcoin, where long gaps happen by chance. Before declaring a halt we ask a second, independent data provider. If one provider is stale and the other is fresh, the chain is fine and we log the provider as lagging. For Solana, Sui and Cardano we have only one free source, so we wait for three stale checks in a row. Start time is the last block before the stop; end time is the first new block, within about a minute.

Finality. For Ethereum we read the last finalized checkpoint from the beacon chain (normally 2 epochs, about 13–19 minutes behind). For other EVM chains and Polkadot we read the newest "finalized" block from the node. On rollups (Base, Arbitrum, OP, ZKsync, Scroll), "finalized" means settled on Ethereum, which takes longer by design: hours on ZKsync. Free Solana endpoints do not report commitment levels reliably, so we do not show Solana finality.

Limits. We have been measuring since 12 Nov 2026; uptime figures cover only that period and say so. If our job misses minutes, a halt that started and ended entirely inside that gap would show up only as a slow hour in the chart. The historical record before our measurements comes from postmortems and news reports, with approximate times marked "≈". Hyperliquid is measured through HyperEVM, which stops whenever the HyperCore L1 stops.

Sources: TON Center; TonAPI; Historical record: project postmortems, status pages, The Block, CoinDesk, Cointelegraph, Decrypt (linked per row)

Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.

Scroll to Top
Chain Report
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.