# Every ping that Newark does it marks as timeout, yet the beta site never indicates such

**URL:** <https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861>\
**Category:** Uncategorized\
**Created:** [December 3, 2020, 11:17pm UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861 "2020-12-03T23:17:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [December 3, 2020, 11:17pm UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/1 "2020-12-03T23:17:37Z")

</div>

The title says it all, here is the logs for beta and real:

EDIT: apparently I can’t add links, ill try replying

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [December 3, 2020, 11:18pm UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/2 "2020-12-03T23:18:52Z")

</div>

Replying didn’t help, my ip is 50.35.185.215

---

<div class="post-metadata">

**Author:** ![stevesommars](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/stevesommars/32/2075_2.png) [@stevesommars](https://community.ntppool.org/u/stevesommars)\
**Post date:** [December 4, 2020, 12:47am UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/3 "2020-12-04T00:47:06Z")

</div>

Was this your server: [https://www.ntppool.org/scores/50.35.68.36](https://www.ntppool.org/scores/50.35.68.36) ?  
[pitime.ddns.net](http://pitime.ddns.net) now resolves to 50.35.185.215

I don’t know how the monitoring software handles this situation.  
I see that Newark is currently (2020-12-02) polling both addresses. Only 50.35.185.215 responds.

The [NTP Pool instructions](https://www.ntppool.org/en/join.html) state " Your computer **must have a static IP address**"

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [December 8, 2020, 1:30am UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/4 "2020-12-08T01:30:58Z")

</div>

Sorry, I just changed computers to a nice server for it. All seems to be working now. Do you know if amazon has some sort of server that has a gps/pps that I could use as a stratum 1 server?

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [December 8, 2020, 8:54am UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/5 "2020-12-08T08:54:04Z")

</div>

And it also seems that newark is timing out at an interval, yet the beta site does not indicate such:

main: [https://www.ntppool.org/scores/50.47.106.71/](https://www.ntppool.org/scores/50.47.106.71/)  
beta: [https://www.ntppool.org/scores/50.47.106.71/log](https://www.ntppool.org/scores/50.47.106.71/log)

---

<div class="post-metadata">

**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\
**Post date:** [December 8, 2020, 9:32am UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/6 "2020-12-08T09:32:10Z")

</div>

The monitoring failures on the production monitoring is very regular. As soon as the score reaches 10, so your NTP server has been put into the active servers pool, for the next monitoring run it falls off. That clearly indicates infrastructure overload. What speed settings have you selected for your server?

---

<div class="post-metadata">

**Author:** ![tennisbowling](https://avatars.discourse-cdn.com/v4/letter/t/71c47a/32.png) [@tennisbowling](https://community.ntppool.org/u/tennisbowling)\
**Post date:** [December 8, 2020, 5:38pm UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/7 "2020-12-08T17:38:29Z")

</div>

1000mbit, probably should turn it down then. My switch is flashing like crazy and I like it. I don’t think its my network as that has gigabit internet (actual is about 700up700down), I think my hardware is the one limiting it. I am running quite a lot of other programs so I will turn most or all of them off to see what result that gives. running `chronyc clients` gives a very large list of users. As I said in my new post, A monitoring solution would be nice. Any reccomendations?

---

<div class="post-metadata">

**Author:** ![apuls](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/apuls/32/1467_2.png) [@apuls](https://community.ntppool.org/u/apuls)\
**Post date:** [December 8, 2020, 7:57pm UTC](https://community.ntppool.org/t/every-ping-that-newark-does-it-marks-as-timeout-yet-the-beta-site-never-indicates-such/1861/8 "2020-12-08T19:57:17Z")

</div>

I would suggest to set to the lowest speed (384kbit). This will also disable the “Global Pool Option” for your NTP Server.  
After a couple of days just raise the speed step by step.  
If you select a speed of 1Mbit or more your server will also be in the “global pool” again.
