Site to evaluate NTP servers

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

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

FWIW ntpinfo will be presented today at RIPE91

:smiling_face_with_tear: RIPE always fails for my site: 160.119.230.39

1 Like

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:

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

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

1 Like

Seems to work OK now. No timeout or error, even RIPE reply happens fast? Ahh, all 3 probes succeeded. :person_shrugging:

I don’t know how a probe, in my own country though, can say that my time is out by 1900ms.

But that is a RIPE question, and I won’t hijack this thread.

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:

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:

So many report the same offset..

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

this issue has fixed today BTW