# MatchX no TX

**URL:** <https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240>\
**Category:** Gateways\
**Created:** [December 18, 2017, 6:58pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240 "2017-12-18T18:58:03Z")\
**Posts on this page:** 1\
**Showing post:** 24

<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:** [December 21, 2017, 9:57pm UTC](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240/24 "2017-12-21T21:57:22Z")

</div>

> [@Verkehrsrot](#):
>
> the purpose of the long downlink delay of TTN’s servers

All by design:

> [@Multiple new devices trying to OTAA](https://www.thethingsnetwork.org/forum/t/multiple-new-devices-trying-to-otaa/8813/18):
>
> The only reason we queue on the network side, is because some gateways don’t have enough memory to fit more than one scheduled message.

And to allow TTN to use the same gateway for downlinks that are to be sent earlier, TTN cannot send messages to a gateway until they’re almost due.

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/matchx-no-tx/11240)._