TON Status
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.
Show more📈 Analytical overview of Telegram channel TON Status
Channel TON Status (@tonstatus) in the English language segment is an active participant. Currently, the community unites 155 188 subscribers, ranking 708 in the Technologies & Applications category.
📊 Audience metrics and dynamics
Since its creation on невідомо, the project has demonstrated rapid growth, gathering an audience of 155 188 subscribers.
According to the latest data from 13 October, 2026, the channel demonstrates stable activity. Although there has been a change in the number of participants by -3 853 over the last 30 days and by -177 over the last 24 hours, overall reach remains high.
- Verification status: Verified (Officially confirmed by Telegram)
- Engagement rate (ER): The average audience engagement rate is 4.32%. Within the first 24 hours after publication, content typically collects 1.88% reactions from the total number of subscribers.
- Post reach: On average, each post receives 6 709 views. Within the first day, a publication typically gains 2 911 views.
- Reactions and interaction: The audience actively supports content: the average number of reactions per post is 0.
📝 Description and content policy
The author describes the resource as a platform for expressing subjective opinions:
“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.”
Thanks to the high frequency of updates (latest data received on 14 October, 2026), the channel maintains relevance and a high level of publication reach. Analytics show that the audience actively interacts with content, making it an important point of influence in the Technologies & Applications category.
Data loading in progress...
| Date | Subscriber Growth | Mentions | Channels | |
| 13 October | 0 | |||
| 12 October | 0 | |||
| 11 October | 0 | |||
| 10 October | 0 | |||
| 09 October | 0 | |||
| 08 October | 0 | |||
| 07 October | 0 | |||
| 06 October | 0 | |||
| 05 October | 0 | |||
| 04 October | 0 | |||
| 03 October | 0 | |||
| 02 October | 0 | |||
| 01 October | 0 |
ton_proof, verify that your implementation complies with the specification.
— Explorers: We recommend adding support for identifying and displaying Telegram Wallet accounts, displaying key rotation actions, and labeling gasless transactions (example).
— Standalone non-custodial wallets: When creating wallets in your app, continue using the wallet-v5r1 smart contract by default, as tg-wallet-v1 is designed specifically for Telegram. Please add support for importing and using existing tg-wallet-v1 wallets (instruction).| 2 | Mainnet validators and node operators:
Please schedule a time to perform and activate the [2026.10] update in accordance with the schedule outlined below.
This update is mandatory for both validators and full node operators.
The upcoming update will activate optimizations on the TON Mainnet network aimed at increasing security, performance and stability.
Update schedule
- Monday 19 October at 14:00 UTC: update of node software to version [2026.10].
- Wednesday 21 October from 06:00 UTC: validators voting on network configuration changes.
Deadlines:
* Validators are required to update their machines within 24 hours of release.
* Full node operators are expected to update their machines and ensure functionality of QUIC ports on their nodes by the end of next week (Friday 23 October). | 2 659 |
| 3 | TON Connect 5.0.0
TON Connect 5.0.0 is now available with improved support for Gram Wallet in Telegram.
dApp developers, please update:
@tonconnect/sdk@5.0.0
@tonconnect/ui@5.0.0
@tonconnect/ui-react@5.0.0
Important: If your dApp uses ton_proof, ensure your implementation follows the documentation, including the get_public_key fallback when the public key cannot be extracted from walletStateInit.
Many Mini Apps currently omit this fallback, which violates the specification and causes authentication to fail with Gram Wallet in Telegram. | 3 290 |
| 4 | The nominator-pool v1 smart contract is now deprecated.
Operators using nominator-pool v1 should plan their migration based on the number of nominators in their pool:
1. One nominator: migrate to single-nominator v1.1.
2. Multiple nominators: migrate to nominator-pool v2.
Both contracts are supported by MyTonCtrl, the validator management tool.
Both contracts can be used with a vesting contract. | 5 823 |
| 5 | Degraded connectivity in the public overlay
Since September 23, a large number of new nodes that do not forward traffic have appeared in TON’s public overlay. This may degrade external message delivery and block synchronization for participants in the public overlay.
These broken nodes are hosted on the following IP addresses, with multiple nodes per IP:
88.216.36.12
88.216.36.80
88.216.182.81
173.234.137.88
88.216.182.41
5.39.221.152
185.191.116.151
51.75.112.186
51.75.134.122
173.234.75.234
178.63.134.206
46.243.221.126
141.95.206.225
57.129.49.17
84.32.103.165
164.132.187.125
82.23.163.70
185.189.45.145
85.195.124.117
138.124.50.195
37.59.67.41
178.20.209.27
185.191.118.150
Major TON services, including exchanges, wallets, Telegram, and Toncenter API, remain unaffected and continue to operate normally, as they do not use the public overlay.
Activation of the new Plumtree broadcasts in the public overlay is scheduled for October. This will improve delivery reliability even when a large number of nodes do not forward traffic.
Exchanges and custodial services experiencing issues should reach out to their technical contact at TON for assistance.
Other developers are advised to use one of the public HTTP APIs alongside their own nodes. | 5 829 |
| 6 | Attention Mainnet validators
Please vote on the network configuration adjustment.
Config -123: Minor improvements to the tg-wallet-v1 contract code, as well as testing of the wallet code upgrade mechanism on the mainnet.
If you use mytonctrl, please vote for proposal via
vo 80830481238463553029095138363073923401512085865719374095445995292694011185619 | 6 987 |
| 7 | Mainnet Validators
Please schedule time wednesday, September 30, starting from 06:00 UTC to participate in the vote on the mainnet configuration update.
Voting is required. | 8 487 |
| 8 | 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
vo 103977679907079231412971872774910018708729377663169264282575516601797565636726 93463024555200663351131178258216152471992757657627817026564359306222314920856 | 7 319 |
| 9 | 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. | 7 135 |
| 10 | 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
7ADCF5845D9878E3C21AA18C4258187DCEEAA32946042085DFF9DCFB7AB81B34
AEAAA7C47A9F3599A9C7CA11C55E5F88171A09C80D0C3783392686FE9B804BFA
B3E28C2BBF3620C5F91B8C152358123E841586A8267D0D174D9B093ADBA048A5
1CF38919D5EBB5CAE3305ECB03B99FD810F55B8510F080880FAF4941665135C0
5BBB2FEFE0D41448B297C75EDEABD0B212978E8FB4DCE7109ED343CFF8CD3C41
74B134353AB0A79C94BC4633F3045C50638B0C909B02BE032F79B585A1D7B90F
If you find your machine on the list, please urgently check your configuration using the instructions.
3)
Have a system configuration that corresponds to the latest requirements.
Please note that failure to observe the above rules will endanger network stability. If these requirements are not met, we will be forced to submit manual requests to slash specific validators. | 8 331 |
| 11 | 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 and issuing the following command in validator-engine-console:
set-collators-list <collators_list_json> | 7 453 |
| 12 | 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 12097562318048223189791980678866953557765689069632717643120314596680459571900 34208501212381821884916867027323947451549110714692222438954375336280844532496 46820293701090638002625837343589766216202823093489845373581525548982016382986 | 6 330 |
| 13 | 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, please update them one by one: update a validator => wait for synchronization => move to the next one
Deadlines: Validators should apply the update within 24 hours of this announcement.
Node changelog
We remind validators about upcoming steps towards activation of collators:
Monday 17 August at 14:00 UTC: upgrade of node software to version [2026.08].
Tuesday 18 August at 12:30 UTC: voting on network configuration changes.
Thursday 20 August at 12:00 UTC: update of the mycontrol software and activation of collators. | 6 006 |
| 14 | 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: voting on network configuration changes.
Thursday 20 August at 12:00 UTC: update of the mycontrol software and activation of collators.
Please note that validator operators will not need to take any additional actions besides those mentioned above. | 5 979 |
| 15 | 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 | 7 555 |
| 16 | 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, please update them one by one:
update a validator => wait for synchronization => move to the next one validator
Update is mandatory for validators, liteservers and archive liteservers.
Deadlines: Validators and full node should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than EOD Friday, 7th of August.
This release does not include breaking API changes and is fully compatible with recent versions of ton-http-api (acceptable versions: v2.0.64 and higher) and TON Indexer (acceptable versions: v1.2.6 and higher).
Node changelog
Mytonctrl changelog | 7 236 |
| 17 | The update instructions will be published within 2 hours. | 5 274 |
| 18 | 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. | 7 565 |
| 19 | 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. | 9 591 |
| 20 | The proposals to update Config 8 and Config 30 have passed.
The network is now using both the new Plumtree broadcast mechanism and the legacy broadcast mechanism simultaneously.
In approximately one week, we will ask operators to update their validators and nodes. After the update, the network will use only Plumtree broadcasts.
Based on our estimates, this should reduce inbound node traffic by approximately 4× and outbound traffic by 2×. It should also significantly improve synchronization and connectivity for nodes and validators. | 6 957 |
