Channel
@tonstatus
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
157,630subscribers
-6,487 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 100,000–316,228.
| Telegram ID | -1001744725639 |
|---|---|
| Type | Channel |
| Username | @tonstatus |
| Description | Technical notifications and up-to-date requests for action for TON validators, developers and integrators. If you're a validator or developer of a popular TON service you should be subscribed. |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 36 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/tonstatus |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 16:17 | 157,630 | -1,046 |
| 17 Sept 2026, 05:40 | 158,676 | -229 |
| 15 Sept 2026, 07:20 | 158,905 | -175 |
| 13 Sept 2026, 18:16 | 159,080 | -320 |
| 11 Sept 2026, 23:56 | 159,400 | -312 |
| 9 Sept 2026, 12:37 | 159,712 | -422 |
| 6 Sept 2026, 07:36 | 160,134 | -297 |
| 4 Sept 2026, 03:58 | 160,431 | -208 |
| 2 Sept 2026, 17:02 | 160,639 | -193 |
| 1 Sept 2026, 13:54 | 160,832 | -175 |
| 31 Aug 2026, 10:37 | 161,007 | -236 |
| 30 Aug 2026, 07:57 | 161,243 | -92 |
| 29 Aug 2026, 08:56 | 161,335 | -137 |
| 28 Aug 2026, 08:53 | 161,472 | -103 |
| 27 Aug 2026, 06:46 | 161,575 | -63 |
| 26 Aug 2026, 09:23 | 161,638 | -95 |
| 25 Aug 2026, 12:47 | 161,733 | +63 |
| 24 Aug 2026, 13:28 | 161,670 | -278 |
| 22 Aug 2026, 18:23 | 161,948 | -187 |
| 21 Aug 2026, 09:44 | 162,135 | first reading |
27 posts held, back to 23 May 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 106 pages of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 27 posts for this entry, the most recent from 27 August 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 26 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Attention Mainnet validators Please vote on the network configuration adjustment. Config 30: Increase the value of the leader_window parameter (and the associated leader_window_desync) to boost TPS by up to 30%. Config -123: Add the tg-wallet-v1 contract code to the network configuration. This contract is proposed for use with the native Gram Wallet on Telegram. If you use mytonctrl, please vote for proposals via…
Mainnet Validators Please schedule time tomorrow, August 27, at 15:00 UTC to participate in the vote on the mainnet configuration update. Voting is required.
Attention Mainnet validators Please prepare for an increased network load and ensure that your validator nodes: 1) Have added a public collator list in accordance with the previously posted instructions. 2) Have a working QUIC port. Currently, validators with the following ADNL addresses do not have an operating QUIC port: 81A6ED816FE7C0552CA4CEDBC3BF4F2F03185CCD318CBF61DB06881D33C967CC 7ADCF5845D9878E3C21AA18C4…
Attention Mainnet validators This update is mandatory for validators; full node owners do not need to update. Please update mytonctrl software on your machines: update master Target versions: — mytonctrl: 64c2aa9 [v2.18.0] This step will complete activation of collators on Mainnet network. If you are not using mytonctrl, please add collators to your validators by downloading the default Mainnet collators list…
Attention Mainnet validators Please make sure that you have updated your machines to [2026.08] release and take part in the voting for network config adjustment: Config 29: Increase the maximum block size to fine-tune the performance of the collator's functionality. Config 31 and 46: Enable governance contracts related to the functionality of collators. If you use mytonctrl, please vote for proposal via vo 120975…
Mainnet Validator Software Update [v2026.08] This update is mandatory for validators; full node owners do not need to update. Please update your node software: Update with mytonctrl: upgrade master Target versions: — node: 3d478cb [v2026.08] If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05). If you have several validators,…
Mainnet validators: Please schedule a time in accordance with the schedule outlined below to perform and activate the [2026.08] update. This update is mandatory for validators; full node owners do not need to update. The upcoming update will activate collators on the TON Mainnet network. Update schedule: Monday 17 August at 14:00 UTC: upgrade of node software to version [2026.08]. Tuesday 18 August at 12:30 UTC: …
Attention Mainnet validators Please take part in the voting for network config adjustment: Config 30: Set the protocol to stable version. If you use mytonctrl, please vote for proposal via vo 97476904964537115993827662219965215594287692635916428067774379550074503377880
Mainnet Validator and Node Software Update [v2026.07] Please update your node software: Update with mytonctrl: update master upgrade master reload_global_config Target versions: — node: bb935a8 [v2026.07] — mytonctrl: 90046e0 [v2.17.1] If you are not using mytonctrl or using ubuntu older than 22.04, check this instruction (https://telegra.ph/TON-Node-Upgrade-202511-11-05). If you have several validators, pleas…
The update instructions will be published within 2 hours.
Mainnet validators and node owners: Please schedule a time on Monday 3 August at 11:00 UTC to perform the software update. This update is mandatory for both validators and full node owners. The update will complete the switch to the plumtree broadcast method enabled in release 2026.06, and will disable the legacy broadcast method to reduce network traffic.
Mainnet node owners Please update your nodes to the 2026.06 release now. See https://t.me/tonstatus/225. Failure to update your nodes will result in loss of network synchronization once legacy broadcasts are disabled in approximately one week.
Showing the 12 most recent of 27 posts we hold for @tonstatus. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 112 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 12 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 49 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 25 September 2026 — this entry's latest reading, not the date you are reading this.
“TON Status” (@tonstatus), 157,630 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/tonstatus.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.