The Things Network Service Status
All Systems Operational

About This Site

This page shows the current status of The Things Network services.

The metrics on this page are updated continuously. Component statuses, incidents and maintenance windows are updated by our operations team.

Incidents and maintenance windows are automatically cross-posted to our forum where the community can discuss them.

If you believe there is an outage that we're not aware of, you can notify the team in the #ops channel on Slack.

Global Services Operational
Website (www.thethingsnetwork.org) Operational
Forum (www.thethingsnetwork.org/forum) Operational
Account Server (account.thethingsnetwork.org) Operational
The Things Stack Community Edition (a.k.a. V3) Operational
Europe 1 (eu1.cloud.thethings.network) Operational
North America 1 (nam1.cloud.thethings.network) Operational
Australia 1 (au1.cloud.thethings.network) Operational
Packet Broker Integration Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
During this maintenance window we will upgrade The Things Network v3.21.0

We do not expect noticeable downtime during this deployment.

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

### Added

- `BatchGetGatewayConnectionStats` RPC to fetch Gateway Connection Stats for a batch of gateways.
- The ability to disable the downlink scheduling mechanism for individual end devices (`mac-settings.schedule-downlinks`).
- This option is useful during a migration procedure in order to force the end device to join the new network. The Network Server will no longer schedule any data downlinks or MAC commands, and will stop answering potential join requests.
- Support for comma-separated (`,`) values in The Things Stack CSV file format for importing end devices.
- Support for the `RxParamSetup`, `RxTimingSetup`, `TxParamSetup`, and `DlChannel` sticky answer mechanism. The commands were supported previously, but subsequent sticky responses would cause the Network Server to drop the MAC command buffer in certain situations.
- Button with connection to the Network Operations Center in the Console.

### Changed

- Deleted users are no longer included in primary email addresses uniqueness checks. This allows a user to create a new account which uses the email address of a deleted account.
- This requires a database schema migration (`ttn-lw-stack is-db migrate`) due to updated indices.
- The CLI settings fields `retry-config.enable_metadata` and `retry-config.default_timeout` have been renamed to `retry.enable-metadata` and `retry.default-timeout` for consistency reasons.
- Generated device ID based on a DevEUI from an imported CSV file is now prepended by `eui-`. This is consistent with generated device IDs by the Console.
- The Claim Authentication Code (CAC) field is stored in the Identity Server instead of the Join Server.
- This requires a database schema migration (`ttn-lw-stack is-db migrate`) because of the added columns.
- CAC values stored currently in the Join Server should be migrated to the Identity Server. One method is to run the following CLI commands on each device with a CAC.
- Read the current values using `ttn-lw-cli dev get --claim-authentication-code`. This will fetch the value stored in the Join Server as a fallback.
- Write back the value read `ttn-lw-cli dev set --claim-authentication-code.valid_from [xxx] --claim-authentication-code.valid_to [xxx] --claim-authentication-code.value `. This will by default write to the Identity Server.
- Note that this requires a minimum CLI version of 3.21.0.
- Device Repository no longer uses the `ApplicationID` for validating requests. Authentication is still necessary, but the `ApplicationID` field has been deprecated in the Device Repository API.

### Fixed

- Console showing `404 Not Found` errors for pages containing user IDs in the path, when the user ID has a length of two.
- CLI no longer panics when deleting a device without JoinEUI, this scenario only occurred when deleting a device that uses ABP.
- Console crashing when navigating to certain Packet Broker network configuration pages.
- Packet Broker network pages becoming inaccessible until refreshing after a user navigates to a non-existing network.
- The batch update query for `EndDevice.LastSeenAt` field now specifies the data type of the placeholders.
- This resolves an issue in the Console where `Last activity` values were inconsistent.

Posted on Aug 5, 18:58 CEST
Connected Gateways ?
Fetching
Received Uplink Messages (from gateways) ?
Fetching
Received Uplink Messages (from Packet Broker) ?
Fetching
Delivered Uplink Messages ?
Fetching
Past Incidents
Aug 7, 2022

No incidents reported today.

Aug 6, 2022

No incidents reported.

Aug 5, 2022

No incidents reported.

Aug 4, 2022

No incidents reported.

Aug 3, 2022

No incidents reported.

Aug 2, 2022

No incidents reported.

Aug 1, 2022

No incidents reported.

Jul 31, 2022

No incidents reported.

Jul 30, 2022

No incidents reported.

Jul 29, 2022

No incidents reported.

Jul 28, 2022

No incidents reported.

Jul 27, 2022

No incidents reported.

Jul 26, 2022

No incidents reported.

Jul 25, 2022

No incidents reported.

Jul 24, 2022

No incidents reported.