Upgrade to The Things Network v3.28.0 (completed)

Completed: Upgrade to The Things Network v3.28.0

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

Scheduled: Wed, 25 Oct 2023 13:00:00 +0200 until 17:30:00 +0200

Resolved: Wed, 25 Oct 2023 17:30:41 +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: Tue, 24 Oct 2023 17:58:53 +0200

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

We expect brief service interruptions during this deployment.

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


  • Locations retrieved from gateway status messages are now be displayed in the gateway map in the Console, even when they are not received through a secure connection.
  • The Network Server ID (NSID, EUI-64) used in LoRaWAN Backend Interfaces is now included in the application uplink message network metadata.
  • It is now possible to trigger a resending of the email validation email from within the Console. The new action is part of the error screen that users see when they log into the Console without having their contact info validated yet (and the network requires validation before usage).
  • Updated Japanese translations for the Console and backend.
  • Support for setting multiple frequency plans for gateways from the Console.


  • Users can now request a new email for the account validation from time to time instead of once per validation, the interval between email requests is by default an hour.
  • Traffic related correlation IDs have been simplified. Previously one correlation ID per component was added as traffic passed through different stack components. Now a singular correlation ID relating to the entry point of the message will be added (such as gs:uplink:xxx for uplinks, or as:downlink:xxx for downlinks), and subsequent components will no longer add any extra correlation IDs (such as ns:uplink:xxx or as:up:xxx). The uplink entry points are pba and gs, while the downlink entry points are pba, ns and as.
  • The Application Server webhook health system now records failures only every retry interval while in monitor mode, as opposed to recording every failure.


  • Providing fixed downlink paths to the ttn-lw-cli devices downlink {push|replace} commands using the -class-b-c.gateways parameter. The gateways IDs are comma separated, and the antenna index i can be provided by suffixing the ID with :i (i.e. my-gateway:0 for antenna index 0). The group index j can be provided by suffixing the ID with :j (i.e. my-gateway:0:1 for antenna index 0 and group index 1). The antenna index is mandatory if a group index is to be provided, but optional otherwise.
  • Gateway registration without gateway EUI not working.
  • Listing deleted entities is now fixed for both admin and standard users, which previously returned an account_not_found error.
  • Negative number support in Cayenne LPP.
  • Fix panic in Snapcraft CLI deployment, commands will no longer generate a panic error message when telemetry is enabled.

In Progress

Posted: Wed, 25 Oct 2023 13:00:25 +0200

Scheduled maintenance is currently in progress. We will provide updates as necessary.


Posted: Wed, 25 Oct 2023 17:30:41 +0200

The scheduled maintenance has been completed.

The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.

The incident on our status page was just updated with new information. The first post in this topic has been updated accordingly.