@tomtobback thanks for bringing this old thread up.
The way it works is that we have three TTSCE (community) clusters; nam1, eu1 and nam1, the same three for TTSC (commercial) plus eu2, and we have three Packet Broker clusters that are serving Americas, EMEA and Asia Pacific. The Packet Broker clusters do all the routing between clusters, but there is no interconnection between Packet Broker clusters. So traffic from eu1 does not show up on au1 or nam1, but eu1 and eu2 works.
The short term solution is that people in all Asia use the au1 cluster for now. That region is connected to Packet Broker Asia Pacific which will be used for all Asian traffic.
The medium term solution is that we add one or two Asian clusters to provide enough saturation and clarity what to use where.
The long term solution is that we implement interconnectivity between Packet Broker clusters, so that traffic from the future as1 can flow to eu1 and nam1. We didn’t do that for now because we don’t see LoRaWAN devices to be roaming globally. But we will need it when bands are more harmonized (e.g. EU 915 MHz or LoRaWAN over 2.4 GHz) and for deployments that are in between Packet Broker Europe and Asia Pacific regions (like Russia and India).