diff --git a/docs/about/overview/mesh-alg.mdx b/docs/about/overview/mesh-alg.mdx
index 73e1e42a..da4eee8f 100644
--- a/docs/about/overview/mesh-alg.mdx
+++ b/docs/about/overview/mesh-alg.mdx
@@ -91,3 +91,25 @@ After node 0 received this rebroadcast, its message is acknowledged. Note that a
 Since node 1 heard the rebroadcast by 2, it will not rebroadcast again. Node 3 heard the message for the first time and the HopLimit is not yet zero, so it starts a rebroadcast for potential other receivers.
 
 ![Mesh algorithm example](/img/SNR_based_flooding.webp)
+
+### Regular Broadcast Intervals
+
+Without additional modules configured, nodes will produce three different types of regularly intervaled traffic as part of the mesh:
+
+1. Device Telemetry
+   - Controlled by `telemetry.device_update_interval`
+   - Default: 30 minutes
+2. Position
+   - Controlled by `position.position_broadcast_secs`
+   - Default: 15 minutes* (with [smart broadcast](/docs/configuration/radio/position/#smart-broadcast) enabled)
+3. NodeInfo user
+   - Controlled by `device.node_info_broadcast_secs`
+   - Default: 3 hours
+
+As meshes grow larger and traffic becomes more contentious, the firmware will increase these intervals. This is in addition to duty cycle, channel, and air-time utilization throttling.
+
+Starting with version 2.4.0, the firmware will scale back Telemetry, Position, and other ancillary port traffic for meshes larger than 40 nodes (nodes seen in the past 2 hours) using the following algorithm:
+
+`ScaledInterval = Interval * (1.0 + ((NumberOfOnlineNodes - 40) * 0.075)))`
+
+For example an active mesh of 62 nodes would scale back `telemetry.device_update_interval` to 79.5 minutes instead of the 30 minute default.