All Systems Operational
About This Site
This page shows the current status of The Things Industries services.
The Things Stack Cloud
Operational
Europe 1 (eu1)
Operational
Europe 2 (eu2)
Operational
North America 1 (nam1)
Operational
Australia 1 (au1)
Operational
Asia 1 (as1)
Operational
Join Server
Operational
Gateway Controller
Operational
Integrations and Third Party Services
Operational
Packet Broker Integration
Operational
Cellular data for The Things Industries gateways
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Upgrade The Things Stack Cloud to v3.37.0 Oct 26, 2026 10:00-12:00 CET
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.
Posted on Oct 19, 2026 - 17:19 CEST
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.
Posted on Oct 19, 2026 - 17:19 CEST