The Things Network
Minor Service Outage

About This Site

This page shows the current status of The Things Network services that are operated by the core team of The Things Network Foundation.

The metrics on this page are updated continuously. Component statuses, incidents and maintenance windows are posted manually 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
The Things Network v2 is Permanently Shutting Down on December 1st Partial Outage
V2 Cluster Discovery is Permanently Shutting Down on December 1st Partial Outage
V2 Console is Permanently Shutting Down on December 1st Partial Outage
V2 Europe has Brownouts Until Permanent Shutdown on December 1st ? Partial Outage
V2 United States - West has Brownouts Until Permanent Shutdown on December 1st ? Partial Outage
V2 Asia-Southeast has Brownouts Until Permanent Shutdown on December 1st ? Partial Outage
V2 Brazil has Brownouts Until Permanent Shutdown on December 1st ? Partial Outage
V2 Integrations have Brownouts Until Permanent Shutdown on December 1st Partial Outage
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Update - The list of affected components has been updated.
Nov 12, 15:25 CET
Update - We are now over a month past the September 30 deadline for migrating end devices from The Things Network V2 to The Things Stack (V3) and there are now less than 3 weeks left until the permanent shutdown of The Things Network V2 on December 1st.

In the coming weeks we will schedule brownouts of the V2 community network. The goal of these brownouts is to create temporary interruptions in applications that still rely on V2. We hope that these interruptions will then trigger alerts to the relevant people, who may not be aware that some of their applications still rely on V2. On the other hand, these interruptions will give everyone who did migrate to The Things Stack (V3) the confidence that their applications are indeed fully migrated to V3 and will continue to work correctly after the permanent shutdown of The Things Network V2 on December 1st.

Since we don't want to prevent people from migrating their applications to The Things Stack (V3), we will enable alternative access to V2 APIs so that they can keep using V2 during the brownouts.

During these brownouts, the following will happen:

- Access to the MQTT APIs will be disabled. Alternative access to the MQTT APIs will be available on ports 11883 (TCP) and 18883 (TLS).
- Access to the Storage Integration will be disabled. Alternative access to the Storage Integration will be available on port 10443 (HTTPS).
- External integrations will be paused, uplink traffic be queued and delivered after the brownout.

What will not change during these brownouts:

- Gateways will stay connected, and will keep forwarding traffic to both The Things Network V2 and to Packet Broker.
- Devices will still be able to join and receive ACKs to confirmed uplink messages.
- You can still use the Console to view your devices and schedule downlinks.
- You can still use the migration tool to migrate your devices to The Things Stack (V3).
Nov 10, 15:06 CET
Scheduled - At The Things Conference we announced that The Things Network V2 would permanently shut down in September 2021. Because of the pandemic, we later extended this date to December 2021 to give the community some more time to migrate to The Things Stack (V3).

Any updates regarding the sunset of The Things Network V2 will be posted in this maintenance announcement.
Jan 25, 14:00 CET
Connected Gateways ?
Fetching
Received Uplink Messages (from gateways) ?
Fetching
Received Uplink Messages (from Packet Broker) ?
Fetching
Delivered Uplink Messages ?
Fetching
Past Incidents
Nov 30, 2021

No incidents reported today.

Nov 29, 2021
Completed - The scheduled maintenance has been completed.
Nov 29, 11:30 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 29, 09:30 CET
Scheduled - During this maintenance window we will upgrade The Things Network v3.16.1

We do not expect noticeable downtime during this deployment.

Here is the changelog since the current version 3.16.0:

### Added

- Support for fine timestamps and frequency offsets sent by gateways with SX1303 concentrator using the legacy UDP protocol.
- Support for resetting end device session context and MAC state in the Console.
- The Content-Security-Policy header (that was previously behind the `webui.csp` feature flag) is now enabled by default.
- Default `Cache-Control: no-store` headers.
- `Cache-Control: public, max-age=604800, immutable` headers for hashed static files.
- Experimental support for BasicStation GPS timestamps which use the wrong precision (milliseconds instead of microseconds).
- The Gateway Server will attempt to determine the correct GPS timestamp from the provided `gpstime` based on the time at which the upstream message has been received.
- This workaround will be available until the related gateway vendors will release patches for this issue.
- Firmware version of The Things Kickstarter Gateway are written to the gateway attributes upon receiving a valid status message.
- Desired mac settings to end device general settings in the Console.

### Changed

- Gateway server disconnects LoRa Basics Station gateways that stop sending pongs to server pings. This does not apply to gateways that don't support pongs.
- The new plugin for reading/writing JSON in our API (that was previously behind the `jsonpb.jsonplugin` feature flag) is now enabled by default. All API responses should be equivalent, but in some cases object fields may be in a different order.

### Fixed

- The reported sub-band's `downlink_utilization` in gateway connection stats now represents the utilization of the available duty-cycle time.
- Missing fields when admins list non-owned entities.
- Using the correct timestamp when retreiving the "Last activity" data point for Gateways on initial page loads in the Console.
- Events reappearing in the end device data view after clearing them when navigating back and forth.
- Editing AWS IoT Integration region, stack name or cross-account role ARN makes The Things Stack re-initialize the integration correctly. Previously, the old AWS IoT Core endpoint was being contacted after editing these values.
Nov 28, 15:43 CET
Nov 28, 2021

No incidents reported.

Nov 27, 2021

No incidents reported.

Nov 26, 2021

No incidents reported.

Nov 25, 2021

No incidents reported.

Nov 24, 2021

No incidents reported.

Nov 23, 2021

No incidents reported.

Nov 22, 2021
Completed - The scheduled maintenance has been completed.
Nov 22, 16:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Nov 22, 12:00 CET
Scheduled - The Things Network V2 will have planned downtime: a brownout. This is for users to ensure that they no longer rely on the deprecated The Things Network V2 service as it is being permanently shut down from December 1st, 2021.

If you experience data loss, you might have missed migrating some end devices to the new The Things Stack Community Edition. If you do not experience any data loss during this brownout window, congratulations, you have migrated your end devices correctly.

Should you rely on traffic from end devices during these brownouts, you can still access the data streams on alternative ports. Please see https://status.thethings.network/incidents/zb5mj6jl563c for more information.
Nov 19, 13:12 CET
Nov 21, 2021

No incidents reported.

Nov 20, 2021

No incidents reported.

Nov 19, 2021

No incidents reported.

Nov 18, 2021

No incidents reported.

Nov 17, 2021

No incidents reported.

Nov 16, 2021

No incidents reported.