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.