# Could not decode NTP response from trace server

**URL:** <https://community.ntppool.org/t/could-not-decode-ntp-response-from-trace-server/2979>\
**Category:** Uncategorized\
**Created:** [August 3, 2023, 12:41am UTC](https://community.ntppool.org/t/could-not-decode-ntp-response-from-trace-server/2979 "2023-08-03T00:41:36Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [August 4, 2023, 4:13am UTC](https://community.ntppool.org/t/could-not-decode-ntp-response-from-trace-server/2979/4 "2023-08-04T04:13:38Z")

</div>

Yeah, none of you are crazy! Sorry about this, I am looking into it now.

Update: The “ad-hoc” check uses MQTT and the client had a bug so it wouldn’t report its online status after reconnecting. The MQTT server was restarted a few days ago to move to another node in the cluster. I wlll add monitoring for “too few monitors connected via mqtt” and also improve the error handling on the website. I’ve fixed the client, but not tagged it in a release yet so in the meantime I just restarted a few of the monitoring clients.

Thanks for reporting this, @bob, @lukas & @zedsdead!

---

_[View the full topic](https://community.ntppool.org/t/could-not-decode-ntp-response-from-trace-server/2979)._