# Strange behavior on US915

**URL:** <https://www.thethingsnetwork.org/forum/t/strange-behavior-on-us915/27301>\
**Category:** TTKG - The Things Kickstarter Gateway\
**Created:** [June 20, 2019, 5:53am UTC](https://www.thethingsnetwork.org/forum/t/strange-behavior-on-us915/27301 "2019-06-20T05:53:26Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![arjanvanb](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/arjanvanb/32/46626_2.png) [@arjanvanb](https://www.thethingsnetwork.org/forum/u/arjanvanb)\
**Post date:** [June 22, 2019, 11:17am UTC](https://www.thethingsnetwork.org/forum/t/strange-behavior-on-us915/27301/6 "2019-06-22T11:17:53Z")

</div>

> [@arjanvanb](#):
>
> If both respond with a Join Accept, then apparently the network is indeed segregating the network for different regions, boldly forwarding the handling to multiple regions as it’s not expecting multiple regions to handle the same uplink.

But, wait: even if the above is true, then only one of the regions would have an application that knows about the device? Or did you create multiple applications (for different regions) that know about the very same OTAA device, and use the same DevEUI, AppEUI and AppKey? Only when all match, multiple handlers could accept the OTAA Join?

(When you cannot change the keys in the device, then be sure to read [How can I reuse hardcoded AppEUI and AppKey after I deleted an application? - #4 by htdvisser](https://www.thethingsnetwork.org/forum/t/how-can-i-reuse-hardcoded-appeui-and-appkey-after-i-deleted-an-application/5113/4) before deleting anything.)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/strange-behavior-on-us915/27301)._