# SWOT Analysis on TTN

**URL:** <https://www.thethingsnetwork.org/forum/t/swot-analysis-on-ttn/3023>\
**Category:** Uncategorized\
**Created:** [August 4, 2016, 6:35am UTC](https://www.thethingsnetwork.org/forum/t/swot-analysis-on-ttn/3023 "2016-08-04T06:35:58Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![hoonppark](https://www.thethingsnetwork.org/forum/user_avatar/www.thethingsnetwork.org/hoonppark/32/7999_2.png) [@hoonppark](https://www.thethingsnetwork.org/forum/u/hoonppark)\
**Post date:** [August 5, 2016, 1:27am UTC](https://www.thethingsnetwork.org/forum/t/swot-analysis-on-ttn/3023/10 "2016-08-05T01:27:41Z")

</div>

Hi @htdvisser, one of the limitations of TTN (or all LoRaWAN networks?) is the following:

“[At most 10 downlink messages per day, including the ACKs for confirmed uplinks.](https://www.thethingsnetwork.org/forum/t/limitations-data-rate-packet-size-30-seconds-uplink-and-10-messages-downlink-per-day-fair-access-policy/1300)”

Does it mean even Class C devices can receive up to 10 downlink messages at most?

If it is the case, I think Class C devices do not have much advantage over Class A devices. This means the Class A unconfirmed messaging would be the only useful messaging for TTN. Would you comment on this?

And, does this limitation apply to TTN only or to all LoRaWAN networks?

---

_[View the full topic](https://www.thethingsnetwork.org/forum/t/swot-analysis-on-ttn/3023)._
