Datacake - Upgrade The Things Stack Cloud to v3.37.0 – Maintenance details

OCT26

Upgrade The Things Stack Cloud to v3.37.0

CompletedOctober 26, 2026 at 9:00 AM – 11:00 AMUTC

Affects

Datacake LNS

Under maintenance from 9:00 AM to 11:00 AM

Australia 1

Under maintenance from 9:00 AM to 11:00 AM

Asia 1

Under maintenance from 9:00 AM to 11:00 AM

North America 1 (nam1)

Under maintenance from 9:00 AM to 11:00 AM

Europe 1 (eu1)

Under maintenance from 9:00 AM to 11:00 AM

  • CompletedOctober 26, 2026 at 11:00 AMUTC

    The scheduled maintenance has been completed.

  • UpdateOctober 26, 2026 at 10:19 AMUTC

    Verification is currently underway for the maintenance items.

  • In progressOctober 26, 2026 at 9:00 AMUTC

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

  • PlannedOctober 19, 2026 at 3:19 PMUTC

    During this maintenance window we will upgrade The Things Stack Cloud to v3.37.0 on all clusters (eu1, eu2, nam1, au1, as1).

    We expect brief service interruptions during this deployment.

    Some gateways may temporarily disconnect as services are restarted. Gateways are expected to automatically reconnect, but in some cases this may take up to one hour.

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

    Added

    • New gs_gateways_disconnected_total metric, counting gateway disconnections by protocol and disconnect reason. This makes disconnection reasons (such as gateways disappearing without a close handshake, or missing too many pongs) observable as a rate, instead of only through logs.
    • ttgc.managed-gateway-euis configuration option: Gateway EUI prefixes of managed gateways, defaulting to the EUI prefix of The Things Industries managed gateways. Gateways outside these prefixes are reported as not managed in the claiming info.
    • ttgc.lbscups.lns-port configuration option: the LoRa Basics Station LNS port of the Gateway Server, defaulting to 8887.
    • Downlink scheduling on all antennas of a gateway. Previously, only the first antenna could be used as a downlink path.
    • events.redis.store.expire-limiter-size configuration option to tune the memory used by the event stream expiration rate limiter, defaulting to 32 MiB.

    Changed

    • In the Semtech UDP Packet Forwarder protocol, PUSH_ACK and PULL_ACK acknowledgements are only sent after the gateway has connected to the Gateway Server and its data has been accepted.
    • Gateway disconnections are now logged once, as Disconnected, including the reason, instead of logging a Task failed warning for every task attached to the gateway connection. This removes several duplicate warnings per gateway disconnection, which were particularly noisy for gateways on unreliable backhaul.
    • Websocket close errors on the LoRa Basics Station frontend (such as a gateway disappearing without a close handshake) are now reported as a defined error with structured details. The gs.gateway.disconnect event for these disconnections now carries structured error details instead of a plain string; consumers that parse the event data should expect the ErrorDetails format.

    Fixed

    • Federated (OIDC/SSO) login no longer fails with unverified_email for identity providers such as Okta that omit the email_verified claim from the ID token and only provide it via the userinfo endpoint.
    • Parsing of the radio context (rctx) field of uplinks received via the LoRa Basics Station LNS protocol. The antenna index in the uplink metadata now reflects the radio context reported by the gateway and is echoed back in class A downlinks, instead of always being 0.
    • The antenna gain sent to LoRa Basics Station gateways in the router configuration. Each board now uses the gain of its own antenna instead of the first antenna's gain, and fractional gains are no longer truncated.
    • Memory usage of event-publishing components (most visibly the Application Server and Network Server) no longer grows with the number of entities.