fa
Feedback
TON Status

TON Status

رفتن به کانال در Telegram

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.

نمایش بیشتر
کشور مشخص نشده استفناوری و برنامه‌ها662

📈 تحلیل کانال تلگرام TON Status

کانال TON Status (@tonstatus) در بخش زبانی انگلیسی بازیگری فعال است. در حال حاضر جامعه شامل 161 598 مشترک است و جایگاه 662 را در دسته فناوری و برنامه‌ها دارد.

📊 شاخص‌های مخاطب و پویایی

از زمان ایجاد در невідомо، پروژه رشد سریعی داشته و 161 598 مشترک جذب کرده است.

بر اساس آخرین داده‌ها در تاریخ 25 اوت, 2026، کانال فعالیت پایداری دارد. در ۳۰ روز گذشته تغییر اعضا برابر -3 888 و در ۲۴ ساعت گذشته برابر -9 بوده و همچنان دسترسی گسترده‌ای حفظ شده است.

  • وضعیت تأیید: تأیید شده (به صورت رسمی توسط تلگرام)
  • نرخ تعامل (ER): میانگین تعامل مخاطب 3.48% است و در ۲۴ ساعت نخست پس از انتشار، محتوا معمولاً 1.21% واکنش نسبت به کل مشترکان کسب می‌کند.
  • دسترسی پست‌ها: هر پست به طور میانگین 5 623 بازدید دریافت می‌کند. در اولین روز معمولاً 1 949 بازدید جمع‌آوری می‌شود.
  • واکنش‌ها و تعامل: مخاطبان به‌طور فعال حمایت می‌کنند؛ میانگین واکنش به هر پست 0 است.

📝 توضیح و سیاست محتوایی

نویسنده این فضا را محل بیان دیدگاه‌های شخصی توصیف می‌کند:
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.

به لطف به‌روزرسانی‌های پرتکرار (آخرین داده در تاریخ 26 اوت, 2026)، کانال همواره به‌روز و دارای دسترسی بالاست. تحلیل‌ها نشان می‌دهد مخاطبان به‌طور فعال با محتوا تعامل دارند و آن را به نقطه اثرگذاری مهم در دسته فناوری و برنامه‌ها تبدیل کرده‌اند.

161 598
مشترکین
-924 ساعت
-7797 روز
-3 88830 روز

در حال بارگیری داده...

ابر برچسب‌ها
هیچ داده‌ای
مشکلی وجود دارد؟ لطفاً صفحه را تازه کنید یا با مدیر پشتیبانی ما تماس بگیرید.
اشارات ورودی و خروجی
---
---
---
---
---
---
جذب مشترکین
اوت '26
اوت '26
+88
در 69 کانال‌ها
ژوئیه '26
+221
در 69 کانال‌ها
Get PRO
ژوئن '260
در 18 کانال‌ها
Get PRO
مه '26
+123
در 49 کانال‌ها
Get PRO
آوریل '26
+207
در 90 کانال‌ها
Get PRO
مارس '260
در 9 کانال‌ها
Get PRO
فوریه '260
در 7 کانال‌ها
Get PRO
ژانویه '260
در 0 کانال‌ها
Get PRO
دسامبر '250
در 2 کانال‌ها
Get PRO
نوامبر '250
در 44 کانال‌ها
Get PRO
اکتبر '250
در 27 کانال‌ها
Get PRO
سپتامبر '250
در 25 کانال‌ها
Get PRO
اوت '250
در 8 کانال‌ها
Get PRO
ژوئیه '250
در 58 کانال‌ها
Get PRO
ژوئن '25
+638
در 163 کانال‌ها
Get PRO
مه '250
در 4 کانال‌ها
Get PRO
آوریل '250
در 5 کانال‌ها
Get PRO
مارس '250
در 14 کانال‌ها
Get PRO
فوریه '250
در 12 کانال‌ها
Get PRO
ژانویه '250
در 6 کانال‌ها
Get PRO
دسامبر '24
+835
در 10 کانال‌ها
Get PRO
نوامبر '24
+1 520
در 4 کانال‌ها
Get PRO
اکتبر '24
+5 358
در 13 کانال‌ها
Get PRO
سپتامبر '24
+13 413
در 305 کانال‌ها
Get PRO
اوت '24
+9 267
در 222 کانال‌ها
Get PRO
ژوئیه '24
+18 069
در 9 کانال‌ها
Get PRO
ژوئن '24
+40 467
در 101 کانال‌ها
Get PRO
مه '24
+179
در 63 کانال‌ها
Get PRO
آوریل '24
+16 037
در 46 کانال‌ها
Get PRO
مارس '24
+168 159
در 0 کانال‌ها
Get PRO
فوریه '24
+119 660
در 1 کانال‌ها
Get PRO
ژانویه '24
+189 030
در 13 کانال‌ها
Get PRO
دسامبر '23
+660
در 57 کانال‌ها
Get PRO
نوامبر '23
+205
در 2 کانال‌ها
Get PRO
اکتبر '23
+432
در 2 کانال‌ها
Get PRO
سپتامبر '23
+221
در 0 کانال‌ها
Get PRO
اوت '23
+49
در 0 کانال‌ها
Get PRO
ژوئیه '23
+27
در 0 کانال‌ها
Get PRO
ژوئن '23
+49
در 0 کانال‌ها
Get PRO
مه '23
+50
در 0 کانال‌ها
Get PRO
آوریل '23
+54
در 0 کانال‌ها
Get PRO
مارس '23
+55
در 0 کانال‌ها
Get PRO
فوریه '23
+92
در 0 کانال‌ها
Get PRO
ژانویه '23
+62
در 0 کانال‌ها
Get PRO
دسامبر '22
+93
در 0 کانال‌ها
Get PRO
نوامبر '22
+114
در 0 کانال‌ها
Get PRO
اکتبر '22
+125
در 0 کانال‌ها
Get PRO
سپتامبر '22
+36
در 0 کانال‌ها
Get PRO
اوت '22
+80
در 0 کانال‌ها
Get PRO
ژوئیه '22
+45
در 0 کانال‌ها
Get PRO
ژوئن '22
+101
در 0 کانال‌ها
Get PRO
مه '22
+583
در 0 کانال‌ها
Get PRO
آوریل '22
+7
در 0 کانال‌ها
Get PRO
مارس '22
+1
در 0 کانال‌ها
Get PRO
فوریه '22
+16
در 0 کانال‌ها
Get PRO
ژانویه '22
+33
در 0 کانال‌ها
Get PRO
دسامبر '21
+855
در 0 کانال‌ها
تاریخ
رشد مشترکین
اشارات
کانال‌ها
26 اوت0
25 اوت+57
24 اوت+31
23 اوت0
22 اوت0
21 اوت0
20 اوت0
19 اوت0
18 اوت0
17 اوت0
16 اوت0
15 اوت0
14 اوت0
13 اوت0
12 اوت0
11 اوت0
10 اوت0
09 اوت0
08 اوت0
07 اوت0
06 اوت0
05 اوت0
04 اوت0
03 اوت0
02 اوت0
01 اوت0
پست‌های کانال
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.

2
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.
5 189
3
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>
5 522
4
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
4 943
5
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.
5 020
6
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 312
7
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
6 905
8
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
6 472
9
The update instructions will be published within 2 hours.
4 937
10
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 261
11
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
12
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
13
Attention Mainnet validators Please take part in the voting for network config adjustment: Config 8: Increase the network version to 15. This will enable changes to improve network stability. More information can be found here. Config 30: Increase the protocol version to 2. This will enable Plumtree broadcasts feature that was included in 2026.06 upgrade. If you use mytonctrl, please vote for proposal via vo 22448832751201245177779867389173635147154128832671288809721723331941883236888 43582131604392367431420013209904118299054963940426054667194752056057570768252
6 332
14
Attention Mainnet validators: On Wednesday, July 22, starting from 5:30 UTC, we ask that validators set aside time to vote on two proposals. Config 8: Increase the network version to 15. This will enable changes to improve network stability. More information can be found here. Config 30: Increase the protocol version to 2. This will enable Plumtree broadcasts feature that was included in [2026.06] upgrade.
5 752
15
Mainnet validators Please take part in the voting for network config adjustment. In order to improve the stability of the network, we kindly ask that you vote in favor of temporarily reducing the maximum number of shardchains from 16 to 4. This reduction will not affect the performance of the blockchain or the user experience under the current organic load. This reduction is temporary, and we will increase this setting in an upcoming update. If you use mytonctrl, please vote for proposal via vo 106555316457343173969073505303576653234520513474761398896187123848200763819496 You may vote before or after the update to the latest release [v2026.06].
7 666
16
Mainnet Validator Software Update [v2026.06] Please update your node software: Update with mytonctrl: update master upgrade master Target versions: — mytonctrl: 14be068 [v2.17.0] — node 3f598aa [v2026.06] 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 should apply the update within 24 hours of this announcement. Lite Server operators should apply the update no later than EOD Friday, 17th of July. 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
6 790
17
Mainnet validators and node owners Please schedule a time on Wednesday, July 15, at 11:00 UTC (tomorrow) to perform the software update. Furthermore, validators will be asked to vote on adjusting the technical network operating parameters. This update is mandatory for both validators and full node owners. The update will include important changes to improve performance and stability.
9 646
18
Mainnet validators and node owners The scheduled network update planned for July 13, as well as the corresponding vote on network configuration changes planned for July 15, have been postponed. We will communicate the new deadlines soon.
7 567
19
Mainnet block production on shard chains has resumed From approximately 09:30 UTC to 11:12 UTC, there was a significant slowdown in the block rate and message processing on shardchains. Operations have now resumed. We are monitoring the network and investigating the incident.
8 480
20
Mainnet shard processing slowdown Block production and message processing in workchain shards are currently experiencing a slowdown. The TON Core team is aware of this issue and is working to resolve it.
32 417