# Client distribution chart shows 0.000 even with longterm score 20

**URL:** <https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570>\
**Category:** Server operators\
**Tags:** monitoring\
**Created:** [July 7, 2026, 6:10pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570 "2026-07-07T18:10:25Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![meszaros.norbert](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/meszaros.norbert/32/2602_2.png) [@meszaros.norbert](https://community.ntppool.org/u/meszaros.norbert)\
**Post date:** [July 7, 2026, 6:10pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/1 "2026-07-07T18:10:25Z")

</div>

hi everyone, for some days now I have noticed, that my client distribution shows absolute zero even if my score is 20 from all relevant monitors. Have I missed something? Or do I need to do some changes in settings?

Thanks

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [July 7, 2026, 7:54pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/2 "2026-07-07T19:54:30Z")

</div>

That goes hand in hand with the DNS query graphs on the [status page](https://status.ntppool.org/) no longer showing any data. It seems that DNS data is no longer entering the respective pipelines, thus data for the “Client distribution” table has been slowly sliding out of the three day window of data considered for this table.  
As interesting side effect, I did observe countries listed for some of my servers that the server is not registered in, but countries it is registered, and where it sees most traffic, not listed anymore, e.g. for a server in Australia:

```auto
us 8.84 ‱
ch 156.25 ‱

```

Or unusually “round” values, e.g.:

```auto
id 500.00 ‱ 794.78 ‱ (0.63x)
my 2500.00 ‱ 1393.70 ‱ (1.79x)

```

I have sent e-mails to @ask about both symptoms.

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [July 8, 2026, 2:50pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/3 "2026-07-08T14:50:53Z")

</div>

Same here, no numbers, just checked also.

---

<div class="post-metadata">

**Author:** ![StrawberryMew](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/strawberrymew/32/2545_2.png) [@StrawberryMew](https://community.ntppool.org/u/StrawberryMew)\
**Post date:** [July 14, 2026, 2:58am UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/4 "2026-07-14T02:58:04Z")

</div>

Ditto! No numbers here too.

 ![1000016668](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/2/27fb8a39ab0d2a9ee7b4e9b997d6a7637055aed0.jpeg)

---

<div class="post-metadata">

**Author:** ![gunnar](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/gunnar/32/689_2.png) [@gunnar](https://community.ntppool.org/u/gunnar)\
**Post date:** [July 15, 2026, 6:26pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/5 "2026-07-15T18:26:37Z")

</div>

And just to add [https://www.ntppool.org/dns.html](https://www.ntppool.org/dns.html) also shows “0 queries” for each server.

---

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [July 15, 2026, 7:00pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/6 "2026-07-15T19:00:00Z")

</div>

The DNS data shown on an NTP server’s page is flowing through the infrastructure, and it seems something in the pipeline is currently broken so the data doesn’t reach the API anymore from which the JS code on the page picks it. Similar with the graphs on the system status page.

The data on the DNS server status page on the other hand is pulled by the web server directly from the DNS servers, it’s not flowing through any other parts of the infrastructure. And the DNS servers simply do not provide that data (anymore?). I.e., this seems to be intentional, not some bug/temporary breakage. So just like with the [“DNS query rate graphs” link at the bottom](https://github.com/abh/ntppool/pull/284), an update of the page template would be needed to reflect that.

---

<div class="post-metadata">

**Author:** ![theking2](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/theking2/32/1941_2.png) [@theking2](https://community.ntppool.org/u/theking2)\
**Post date:** [July 24, 2026, 6:30am UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/7 "2026-07-24T06:30:46Z")

</div>

Same here. Is there something I can/should do?

With monitoring on I see many request coming in so everything works.

---

<div class="post-metadata">

**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\
**Post date:** [July 27, 2026, 12:43pm UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/10 "2026-07-27T12:43:05Z")

</div>

Numbers are back 👍

---

<div class="post-metadata">

**Author:** ![Fant](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/fant/32/2668_2.png) [@Fant](https://community.ntppool.org/u/Fant)\
**Post date:** [September 29, 2026, 2:46am UTC](https://community.ntppool.org/t/client-distribution-chart-shows-0-000-even-with-longterm-score-20/4570/11 "2026-09-29T02:46:26Z")

</div>

I’ve encountered the same problem and would like to know how to solve it. I’d like to know if my server is still providing time synchronization services in this situation.😟
