# Time synchronisation of a Node

**URL:** <https://www.thethingsnetwork.org/forum/t/time-synchronisation-of-a-node/1641>\
**Category:** End Devices (Nodes)\
**Created:** [April 1, 2016, 8:59am UTC](https://www.thethingsnetwork.org/forum/t/time-synchronisation-of-a-node/1641 "2016-04-01T08:59:41Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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 5, 2017, 4:29pm UTC](https://www.thethingsnetwork.org/forum/t/time-synchronisation-of-a-node/1641/14 "2017-06-05T16:29:16Z")

</div>

> [@Verkehrsrot](#):
>
> We’re working on a time sync protocol.

_You_ are probably aware of it: note that the current gateways are half-duplex (so cannot listen on _any_ channel/SF when transmitting a downlink), which is why downlinks are limited to [at most 10 messages per day](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy/1300). So any use case for which the gateway/backend timestamps suffice should really, really, _really_ just rely on that.

(That said: I’m curious what you’ll come up with!)

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/time-synchronisation-of-a-node/1641)._