Upgrade to The Things Network v3.27.0 (completed)

Completed: Upgrade to The Things Network v3.27.0

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

Scheduled: Wed, 26 Jul 2023 13:00:00 +0200 until 15:30:00 +0200

Resolved: Wed, 26 Jul 2023 15:30:06 +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, 21 Jul 2023 16:16:31 +0200

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

We expect brief service interruptions during this deployment.

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


  • RPCs and CLI command to delete a batch of end devices within an application.
    • Check ttn-lw-cli end-devices batch-delete for more details.
  • Add UserInput component to the Console to handle user id input fields by implementing an autosuggest.


  • Instead of retrying application downlinks indefinitely, the Application Server now retries them for a configured number of times. Each ApplicationDownlink message contains the attempt and max_attempts fields to indicate the current and maximum number of attempts for a specific application downlink.
  • The Application Server configuration has the as.downlinks.confirmation.default-retry-attempts and as.downlinks.confirmation.max-retry-attempts fields that configure the allowed number of retries for application downlinks. The default values are 8 for the as.downlinks.confirmation.default-retry-attempts and 32 for the as.downlinks.confirmation.max-retry-attempts.
  • The as.downlinks.confirmation.default-retry-attempts field is used for all application downlinks that were scheduled before this change and for every application downlink that does not have the max_attempts field set. On the other hand, the as.downlinks.confirmation.max-retry-attempts field ensures that the max_attempts field's upper bound is contained and does not exceed its value.
  • The number of historical frames considered for the multi-frame query window size in the LoRaCloud Geolocation Services integration. The window size is now limited between 1 and 16 frames with 16 being the default value.


  • Command-line interface support for listing QR code formats and generating QR codes. This is considered the responsibility of a LoRaWAN Join Server.


  • End device data stream not being closed when navigating away from end device pages, which could cause event streams stopping to work due to too many open connections.

In Progress

Posted: Wed, 26 Jul 2023 13:00:14 +0200

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


Posted: Wed, 26 Jul 2023 15:30:06 +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.