# Score won't stay above 10 **URL:** \ **Category:** Server operators\ **Tags:** monitoring\ **Created:** [August 16, 2023, 6:21pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995 "2023-08-16T18:21:40Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![wylie39](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/wylie39/32/1138_2.png) [@wylie39](https://community.ntppool.org/u/wylie39)\ **Post date:** [August 16, 2023, 6:21pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/1 "2023-08-16T18:21:40Z")
I just started hosting an NTP server in the pool and I can’t seem to keep its score above 10, any ideas? The only thing I can see is that the monitor named “every” times out Here is all the info I have right now Link to the main pool score is at 10.4 - [pool.ntp.org: Statistics for 71.162.136.44](https://www.ntppool.org/scores/71.162.136.44) Link to the beta pool score is at 20 most of the time - [pool.ntp.org: Statistics for 71.162.136.44](https://web.beta.grundclock.com/scores/71.162.136.44) The bandwidth is set at 512 so I don’t think it is getting overloaded Offsets are all under 50ms More info below Any ideas would be appreciated ---
**Author:** ![wylie39](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/wylie39/32/1138_2.png) [@wylie39](https://community.ntppool.org/u/wylie39)\ **Post date:** [August 16, 2023, 6:22pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/2 "2023-08-16T18:22:16Z")
Here is an NTP ripe measurement I ran, so it’s definitely online [RIPE Atlas](https://atlas.ripe.net/measurements/58689339/#probes) Here is a ripe Traceroute [RIPE Atlas](https://atlas.ripe.net/measurements/58689971/#probes) ---
**Author:** ![wylie39](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/wylie39/32/1138_2.png) [@wylie39](https://community.ntppool.org/u/wylie39)\ **Post date:** [August 16, 2023, 6:26pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/3 "2023-08-16T18:26:32Z")
Traceroute to 71.162.136.44 1 \* \* 2 (169.254.74.0) 0.125 0.136 3 (10.253.4.207) 0.146 3 (10.253.4.211) 0.173 4 (10.253.4.147) 11.045 11.041 5 [nyk-b4-link.ip.twelve99.net](http://nyk-b4-link.ip.twelve99.net) (62.115.180.4) AS1299 0.486 \* 6 [nyk-bb2-link.ip.twelve99.net](http://nyk-bb2-link.ip.twelve99.net) (62.115.114.180) AS1299 0.968 0.775 7 \* \* 8 \* \* 9 \* \* 10 \* \* 11 wylief.dev (71.162.136.44) AS701 5.530 5.473 ---
**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 16, 2023, 11:03pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/4 "2023-08-16T23:03:59Z")
Thanks for this example @wylie39. I’d have expected the [selector process](https://news.ntppool.org/docs/monitoring/) to pick different monitors to find some that works better. At a glance in the logs it seems like all the monitors have erratic enough results that the system can’t get consensus on some that works. It might be worth checking if you have a firewall or iptables type setup that’s trying to keep state of all the NTP “sessions” and running out of space. ---
**Author:** ![davehart](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/davehart/32/1411_2.png) [@davehart](https://community.ntppool.org/u/davehart)\ **Post date:** [August 16, 2023, 11:17pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/5 "2023-08-16T23:17:55Z")
Welcome, wylie39, and thanks for volunteering your server for NTP service. I added your IP address to my local GPS/PPS ntpd with maxpoll 6 to see how it fares several hours ago: ```auto remote refid st t when poll reach delay offset jitter ============================================================================== o127.127.22.4 .PPS. 0 l 11 16 377 0.000 +0.023 0.012 +71.162.136.44 208.90.144.53 3 u 130 64 16 11.591 +0.597 0.582 ``` It appears from my vantage (96.9.224.210) I’m only seeing responses to a fraction of the polls. The ideal “reach” value is 377 representing all 8 recent polls got a response. The value 16 (octal) indicates only 3 of the last 8 queries got responses. I hope Ask’s suggestion to check for stateful firewalling misbehaving leads you to a solution. ---
**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:** [August 17, 2023, 2:18am UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/6 "2023-08-17T02:18:25Z")
I ran my usual traceroute with UDP-dst = 123 and UDP-dst=37 from a server in London. I believe there is a port-specific block somewhere on the path. Unfortunately a number of hops do not participate in traceroute. First column is # replies This is what port 123 probes show. 8 4 ICMP:TTL 138.197.251.142 8 5 ICMP:TTL 83.231.181.121 8 6 ICMP:TTL 129.250.4.250 7 7 ICMP:TTL 129.250.3.190 8 9 ICMP:TTL 129.250.3.244 10 noresponse 11 noresponse 12 noresponse 4 13 71.162.136.44 (NTP server) Port 37 probes should no losses at the NTP server. Wylie, try doing a traceroute from your NTP server to 178.62.9.15. You won’t get a response, but the results may indicate which ASN is doing rate limiting. [Zayo and Telia are two common culprits] ---
**Author:** ![wylie39](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/wylie39/32/1138_2.png) [@wylie39](https://community.ntppool.org/u/wylie39)\ **Post date:** [August 17, 2023, 10:52pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/7 "2023-08-17T22:52:59Z")
Thanks, everyone, I seem to have it all set, moved the server from a proxmox lcx to a VM and it seems to be working fine. ---
**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 18, 2023, 11:03pm UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/8 "2023-08-18T23:03:09Z")
Thanks for the update, @wylie39! ---
**Author:** ![Knot3n](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/knot3n/32/407_2.png) [@Knot3n](https://community.ntppool.org/u/Knot3n)\ **Post date:** [August 19, 2023, 8:25am UTC](https://community.ntppool.org/t/score-wont-stay-above-10/2995/9 "2023-08-19T08:25:17Z")