# Regarding Qos 0 memory exceeded alert

**URL:** <https://community.hivemq.com/t/regarding-qos-0-memory-exceeded-alert/1781>\
**Category:** Uncategorized\
**Created:** [January 25, 2023, 8:37pm UTC](https://community.hivemq.com/t/regarding-qos-0-memory-exceeded-alert/1781 "2023-01-25T20:37:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![hivemq-support](https://yyz1.discourse-cdn.com/flex035/user_avatar/community.hivemq.com/hivemq-support/32/357_2.png) [@hivemq-support](https://community.hivemq.com/u/hivemq-support)\
**Post date:** [January 25, 2023, 9:48pm UTC](https://community.hivemq.com/t/regarding-qos-0-memory-exceeded-alert/1781/2 "2023-01-25T21:48:53Z")

</div>

Hi Shaku,

You previously asked about a different observed error, “Qos 0 channel not writable”:  
​

[https://community.hivemq.com/t/qos-0-channel-not-writable/1499](https://community.hivemq.com/t/qos-0-channel-not-writable/1499)  
​

For “Qos 0 memory exceeded” errors, everything @michael_w advised should still apply - it’s usually an issue of topic client subscriber consumption being a bottleneck. What was the outcome after reviewing his advice? Did you consider moving to a later version?

This is the Control Center analytics documentation for our current release if it could also be helpful:

[https://www.hivemq.com/docs/hivemq/4.11/control-center/analytic.html#dropped-messages](https://www.hivemq.com/docs/hivemq/4.11/control-center/analytic.html#dropped-messages)

Thanks,  
Seth - HiveMQ Support

---

_[View the full topic](https://community.hivemq.com/t/regarding-qos-0-memory-exceeded-alert/1781)._