8 Jul
2025
8 Jul
'25
5:19 p.m.
I noticed a discrepancy between the output of my own tool and RIPE Atlas.
My tool reports the offset as a negative value, while RIPE Atlas shows a positive one.
For example: https://atlas.ripe.net/measurements/115803954/results
Any thoughts?
Looking at the code, it seems that the Atlas NTP measurement computes the offset with exactly the opposite sign compared to the NTP RFCs. I never noticed before.