For those running nodes or services dependent on the public overlay, these issues can result in delayed message propagation and the risk of falling out of sync with network blocks. Developers and custodial services using public overlay nodes are advised to supplement their setups with public HTTP APIs to bridge current relay gaps. A protocol update introducing Plumtree broadcasts is scheduled for October, aiming to improve reliability and message delivery even in the presence of non-forwarding nodes. Until this update rolls out, affected services should reach out to TON technical support if connectivity problems disrupt operations.
Detailed Causes of the Connectivity Problems
The degraded connectivity results from an increase in non-forwarding or "broken" nodes since late September. These nodes, concentrated across a relatively small number of IP addresses, do not pass on messages or blocks, breaking relay chains within the public overlay. The effect is most acute for custom projects, smaller builders, or validators that connect directly through the overlay network.
Primary platforms—including major exchanges, custodial wallets, Telegram Mini Apps, and the Toncenter API—continue to function normally because they use separate communication pathways that do not route through the public overlay. Builders running independent nodes or relying heavily on the overlay segment need to be aware of the increased risk of incomplete blockchains or synchronization delays during this period.
Impacts for Node Operators and Builders
Node operators and developers dependent on the public overlay may see slower message delivery, reduced block sync reliability, and intermittent lags or outages. These issues do not extend to most end users or popular applications, as the majority of major services sidestep the affected public overlay infrastructure entirely.
Exchanges and custodial services experiencing overlay connectivity issues should contact their TON technical representatives for targeted support. Independent developers are encouraged to add public HTTP API access to their architecture. This mitigates the overlay’s current weaknesses until the planned protocol upgrade.
TON Drop Hub take: While day-to-day operations on mainstream services remain stable, builders using the overlay directly must adapt—relying solely on the public overlay exposes users to sync and delivery risks until technical fixes are deployed.
Upcoming Upgrade: Plumtree Broadcasts
A protocol upgrade introducing Plumtree broadcasts within the public overlay is targeted for October. This enhancement is designed to improve message propagation, reducing the impact of nodes that refuse to forward data. The fix is set to enable more reliable delivery, regardless of the presence of unreliable or hostile peers on the network.
The clustering of many non-forwarding nodes on only a few IP addresses suggests possible abuse or misconfiguration. This reduces available routing options and can stall block or message delivery for those dependent on overlay connectivity. Major platforms, however, remain unaffected due to their reliance on separate infrastructure.
The full impact on smaller third-party applications and custom node deployments is not yet clear. As a precaution, those who depend on the public overlay are advised to combine it with public HTTP APIs to avoid operational interruptions until the Plumtree upgrade is live.
TON Drop Hub take: The transition to Plumtree will demonstrate how well TON can maintain overlay network reliability in hostile conditions. Builders should carefully monitor their node delivery once changes go live, and be ready to adjust configuration if issues persist beyond October.
—
For the time being, only participants relying exclusively on the public overlay network face significant risks. Most mainstream services—including exchanges, custodial wallets, Telegram integrations, and the Toncenter API—remain fully operational, as they do not depend on this segment of the network. Developers seeking to ensure robust connectivity should integrate public HTTP APIs with their own node infrastructure. Plumtree broadcasts are scheduled for rollout in October and are expected to improve resilience against network disruptions associated with non-forwarding nodes.
For further updates and coverage, see Latest TON news.
Source reference: original source.