With the official shutdown date (1 December) of The Things Network’s V2 network behind us, we were able to release the DevAddr blocks that were previously in use by The Things Network V2 clusters. We have updated the routes in Packet Broker to forward these old DevAddr blocks to our V3 clusters:
| Block | Previous Cluster | Current Cluster |
|---|---|---|
| 26010000/16 | V2 eu | eu1.cloud.thethings.network |
| 26020000/16 | V2 us-west | nam1.cloud.thethings.network |
| 26030000/16 | V2 brazil | nam1.cloud.thethings.network |
| 26040000/16 | V2 asia-se | au1.cloud.thethings.network |
| 26050000/16 | V2 ch (switch) | eu1.cloud.thethings.network |
| 26060000/16 | V2 au (meshed) | au1.cloud.thethings.network |
| 26070000/16 | V2 uk (digitalcatapult) | eu1.cloud.thethings.network |
| 260B0000/16 | - | eu1.cloud.thethings.network |
| 260C0000/16 | - | nam1.cloud.thethings.network |
| 260D0000/16 | - | au1.cloud.thethings.network |
What this means for devices migrated from V2 to V3:
If you migrated an ABP device (or OTAA session) with a DevAddr in one of these blocks to the corresponding V3 cluster, this device will now benefit from coverage of gateways that are still connected to V2.
We previously said that “migrating active sessions via Packet Broker is not available, i.e. migrating gateways at the same time as migrating devices is a necessity”.
With these changes this is no longer the case, as Packet Broker now also forwards this traffic to V3.
If you haven’t migrated your devices yet, you can still do so until December 7th: