Upgrade to The Things Network v3.25.2 (completed)

Scheduled: Upgrade to The Things Network v3.25.2

This is a cross-post of an incident on our The Things Network status page.
It will be updated automatically.

Scheduled: Mon, 08 May 2023 13:00:00 +0200 until 15:00:00 +0200

Affected Components

  • Europe 1 (eu1.cloud.thethings.network): Operational
  • North America 1 (nam1.cloud.thethings.network): Operational
  • Australia 1 (au1.cloud.thethings.network): Operational


Posted: Fri, 05 May 2023 13:37:11 +0200

During this maintenance window we will upgrade The Things Network v3.25.2

We expect brief service interruptions during this deployment.

Here is the changelog since the current version v3.25.1:


  • Experimental channel steering API, which allows steering end devices from the wide (250kHz or 500kHz) channels towards the narrow (125kHz) channels.
    • This API is mainly relevant for end devices operating in the US915 and AU915 regions, as they may join via a wide channel, but users may want to steer them towards the narrow channels.
    • The new settings can be found under mac-settings.adr.mode.dynamic.channel-steering.
    • mac-settings.adr.mode.dynamic.channel-steering.mode.lora-narrow steers the end devices towards the LoRa modulated narrow channels.
    • mac-settings.adr.mode.dynamic.channel-steering.mode.disabled does not steer the end devices - end devices are left to operate in their currently active channels, wide or narrow.
    • The default behavior is to avoid steering the end devices, but this is subject to change in future versions. Consider explicitly specifying a certain behavior (lora-narrow or disabled) if you depend on not steering the end devices.


  • Uplink and downlink message frequencies are now validated and zero values are dropped.
    • Such traffic would have always been dropped by the Network Server, but it is now dropped in the Gateway Server.
    • Simulated uplink traffic now requires a frequency value as well.


  • Multiple ADR algorithm bugs:
    • An off-by-one error which caused the ADR algorithm to not take into consideration the signal qualities of the uplink which confirmed a parameter change. In effect, this fix improves the quality of the link budget estimation.
    • A flip-flop condition which caused the algorithm to swap back and forth between a higher and a lower transmission power index every 20 uplinks. In effect, this fix will cause the algorithm to change the transmission power index less often.
    • A condition mistake which caused the algorithm to avoid increasing the transmission power if it would not completely fix the missing link budget. In effect, this will cause the algorithm to increase the transmission power in situations in which the link budget deteriorates rapidly.
  • In fixed channel plans such as US915 and AU915, the the associated wide (500kHz) channel is now enabled by default.
1 Like

What is a “gateway server”?
Is it the gateway or the server the gateway connects to?

The gateway server is a central component that handles connections from the gateway. It is part of the LNS stack.