Handling Network Growth and Congestion

A Meshtastic network that works well with five nodes may behave poorly at fifty. Managing growth proactively — rather than reacting after congestion degrades performance — is what separates a durable community network from one that works great until it doesn't.

Early Stage: 1–10 Nodes

At this scale, almost any configuration works. Long Fast is a reasonable default — it has good range and is the most common preset, making it easy for newcomers to join.

Focus at this stage belongs on placement, not optimization. A single well-placed repeater on a hilltop or water tower does more for network coverage than ten ground-level nodes. Get repeaters in good locations first.

Growth Stage: 10–50 Nodes

As the network grows, start monitoring channel utilization. The Meshtastic app displays this metric; check it periodically. Utilization consistently above 15% is a warning sign.

Actions at this stage:

Audit hop limits. High hop limits cause individual messages to generate multiple retransmissions across many nodes. A hop limit of 3 is appropriate for most community networks; higher values compound congestion.
Review node density. Clusters of nodes in the same small area all hear and retransmit each other's traffic. Nodes that add density without extending coverage add congestion without benefit.
Begin discussing a potential preset migration with the community before it becomes urgent.

Scaling Stage: 50+ Nodes

At this scale, Long Fast will likely show sustained high utilization. Seriously consider migrating to Medium Slow or Medium Fast, which use lower data rates (thus more airtime per message) in exchange for significantly better receiver sensitivity and range — the tradeoff that matters when node count is high and coverage gaps are the remaining problem.

This migration must be coordinated as a community. All nodes must change simultaneously, or you split the network — nodes on different presets cannot communicate.

Preset Migration Process

Pick a date and time for the migration window.
Announce in all community channels at least two weeks in advance. Post in Discord, on the website, and in any mailing lists. Include the specific preset being adopted.
Document the change procedure — a step-by-step guide for changing the preset in the Meshtastic app, for both Android/iOS and the web client.
Change infrastructure repeaters first. These are the reference points that participants will see when they join on the new preset.
Ask all participants to update within the migration window. A specific two-hour window on a weekend afternoon works better than "sometime this week."
Run a compatibility bridge temporarily. Leave one repeater on the old preset for 1–2 weeks after migration. This gives stragglers a way to see a message like "Network has migrated to Medium Slow — update your preset to rejoin" and self-serve the fix.

Managing the Public Channel

You cannot control what strangers do on the public channel. Trolling, spam messages, and misconfigured nodes that flood the network with repeated traffic are occasional realities on any open mesh.

Mitigation strategies:

Maintain a secondary private channel for your community's operational use, regardless of network size. The public channel is for newcomers and casual use; the private channel is for your community's serious coordination.
Document and enforce a community hop limit recommendation. Infrastructure nodes can be configured to refuse to relay messages above a certain hop count, which limits cascading retransmissions.
Treat persistent disruptive nodes as a maintenance issue, not a personal conflict. Document the node ID and behavior, and discuss with your community whether any technical mitigations are warranted.

Tracking Growth Health

Watch these indicators month over month:

Node count visible on meshmap.net (total and always-online)
Channel utilization during peak hours
Ratio of infrastructure repeaters to client nodes (more repeaters relative to total nodes = better network health)

Growth that outruns infrastructure is the most common failure mode for community meshes. Adding repeaters ahead of demand keeps the network healthy through growth phases.