"No Brokers" Error for ABP Device on TTN V3

As always, let me start by saying that you should not use ABP unless you have a very good reason; OTAA is always preferred. If you do use ABP, you should not just randomly pick a DevAddr; instead you should request one from the Network Server, and use that.


The “router ttn-router-us-west drop … reason:no brokers” indeed doesn’t mean that traffic isn’t forwarded to Packet Broker. I’ll see if we can do something to somehow make this a bit more clear.


All ttn-router-* and *.cloud.thethings.network are connected to Packet Broker. If any cluster receives traffic for DevAddr block 260C0000/16 (see also the list of blocks in this forum comment) , that traffic should end up in nam1.cloud.thethings.network.