# Gateway Latency **URL:** \ **Category:** Gateways\ **Created:** [April 26, 2017, 6:58pm UTC](https://www.thethingsnetwork.org/forum/t/gateway-latency/6942 "2017-04-26T18:58:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![htdvisser](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/htdvisser/32/45312_2.png) [@htdvisser](https://www.thethingsnetwork.org/forum/u/htdvisser)\ **Post date:** [April 27, 2017, 6:44am UTC](https://www.thethingsnetwork.org/forum/t/gateway-latency/6942/3 "2017-04-27T06:44:06Z")
> [@chris-1](#): > > 1 second for RX1 can be a bit optimistic unless on a DSL connection, 2 seconds for RX2 however is fairly doable. We try to avoid RX2 if possible. For RX1 we have 8 channels available, while RX2 is fixed on 1 channel and a very inefficient data rate. Therefore, expect most downlink messages to be sent after 1 second. Losing 400 ms on the slow connection is not ideal, but we can handle it. For now just install the latest packet forwarder from Semtech ([GitHub - Lora-net/packet\_forwarder: A LoRa packet forwarder is a program running on the host of a LoRa gateway that forwards RF packets receive by the concentrator to a server through a IP/UDP link, and emits RF packets that are sent by the server.](https://github.com/Lora-net/packet_forwarder)) and we’ll make sure the timing on the server side will be better. In private networks with this issue, you might want to consider increasing the RX\_DELAY to (for example) 5 seconds. That would place RX1 at 5 and RX2 at 6, leaving more than enough time for even a satellite backhaul. --- _[View the full topic](https://www.thethingsnetwork.org/forum/t/gateway-latency/6942)._