# Site to evaluate NTP servers **URL:** \ **Category:** Uncategorized\ **Tags:** monitoring\ **Created:** [July 8, 2025, 7:26am UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931 "2025-07-08T07:26:38Z")\ **Posts on this page:** 10\ **Page:** 2
**Author:** ![hans-mayer](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/hans-mayer/32/1933_2.png) [@hans-mayer](https://community.ntppool.org/u/hans-mayer)\ **Post date:** [September 12, 2025, 8:08pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/22 "2025-09-12T20:08:18Z")
Hi giovane, It’s a nice project. Congratulation. I tested the application a little bit and it seems that it takes the best result out of 3 probes from ripe atlas. But there are a lot of outlier. I run a NTP test with several probes at ripe and I got results from +/- 2 seconds ( not milliseconds, it’s seconds ) for the offset. Only about 60 percent are within 10 milliseconds. So there is a high possibility that you take 3 probes which are not accurate. Of course the intention of ripe is a different one. Are you pre-selecting some probes or is it what you get for a specific area ? Kind regards Hans – ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 21, 2025, 6:24am UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/23 "2025-10-21T06:24:37Z")
hi @hans-mayer Sorry for the delay Making an issue on this.. indeed, thanks for noticing it I just crated a new issue [comment on ntp pool · Issue #43 · NTPinfo/NTPinfo · GitHub](https://github.com/NTPinfo/NTPinfo/issues/43) ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 21, 2025, 6:25am UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/24 "2025-10-21T06:25:32Z")
FWIW ntpinfo will be presented today at RIPE91 > **[Plenary - RIPE 91](https://ripe91.ripe.net/programme/meeting-plan/sessions/17/)** > > Overview of talks during the 'Plenary' session at RIPE 91 ---
**Author:** ![errolt](https://avatars.discourse-cdn.com/v4/letter/e/dc4da7/32.png) [@errolt](https://community.ntppool.org/u/errolt)\ **Post date:** [October 24, 2025, 3:43pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/25 "2025-10-24T15:43:30Z")
🥲 RIPE always fails for my site: 160.119.230.39 ![Screenshot 2025-10-24 at 17-42-55 NTPinfo](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/8/839352d265415d30b1adc36a7956ee0556b65b8d.png) ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 27, 2025, 8:35am UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/26 "2025-10-27T08:35:44Z")
hi @errolt thanks for reporting this. I’ll bring this to github FWIW I’ve tried from my location and I am getting the same error BUT the measurement on Atlas actually ran: > **[RIPE Atlas - RIPE Network Coordination Centre](https://atlas.ripe.net/measurements/134314125/overview)** > > RIPE Atlas is the RIPE NCC's main Internet data measurement system. It’s just one probe that failed or did not report. Maybe the code needs to handle such cases. Will bring it to the devs on [Github](https://github.com/NTPinfo/NTPinfo/issues/43) ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 27, 2025, 8:39am UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/27 "2025-10-27T08:39:27Z")
wait.. after a while the results showed up, whereas before was just the error. It says if a hoover over the red exclamation mark that one probe timed out ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/d/da64c7732edbe7f5e8b1ac8998e832dbaaac6d08.png) ---
**Author:** ![errolt](https://avatars.discourse-cdn.com/v4/letter/e/dc4da7/32.png) [@errolt](https://community.ntppool.org/u/errolt)\ **Post date:** [October 27, 2025, 1:56pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/28 "2025-10-27T13:56:46Z")
Seems to work OK now. No timeout or error, even RIPE reply happens fast? Ahh, all 3 probes succeeded. 🤷 I don’t know how a probe, in my own country though, can say that my time is out by 1900ms. > **[RIPE Atlas - RIPE Network Coordination Centre](https://atlas.ripe.net/measurements/134352308/overview)** > > RIPE Atlas is the RIPE NCC's main Internet data measurement system. But that is a RIPE question, and I won’t hijack this thread. ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 27, 2025, 2:36pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/29 "2025-10-27T14:36:04Z")
> I don’t know how a probe, in my own country though, can say that my time is out by 1900ms. Ripe Altas results are not “ground truth” as the time.nl server For instance, see the result from your measruement above: ![image](https://us1.discourse-cdn.com/flex016/uploads/ntppool/original/2X/f/f18b95bcf64d61d9da164bb5da0ca1ea53b37e30.png) W e have 3 probes, one has an offset of 1ms, other of -600ms, and the last one of -1900ms .. but I ran another measurement with 50 probes to your server: > **[RIPE Atlas - RIPE Network Coordination Centre](https://atlas.ripe.net/measurements/134314281/results)** > > RIPE Atlas is the RIPE NCC's main Internet data measurement system. So many report the same offset.. ---
**Author:** ![Kets\_One](https://avatars.discourse-cdn.com/v4/letter/k/46a35a/32.png) [@Kets\_One](https://community.ntppool.org/u/Kets_One)\ **Post date:** [October 27, 2025, 2:45pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/30 "2025-10-27T14:45:38Z")
Running NTPInfo on one of my servers the results vary: sometimes RIPE reports that there is a problem, sometimes it runs fine. Server: 2a02:a46d:7ac:1:f690:eaff:fe00:700e ---
**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\ **Post date:** [October 30, 2025, 1:49pm UTC](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931/31 "2025-10-30T13:49:24Z")
> [@giovane](#): > > [Fix NTP offset calculations · Issue #130 · RIPE-NCC/ripe-atlas-software-probe · GitHub](https://github.com/RIPE-NCC/ripe-atlas-software-probe/issues/130) this issue has fixed today BTW [Previous page](https://community.ntppool.org/t/site-to-evaluate-ntp-servers/3931.md?page=1)