Based on the name, I’d expect mdrmo1 to be located in Moldova, near the Chișinău Eugen Doga International Airport (RMO). However, looking at the scores of the Moldovan NTP servers, this monitor seems to be 130-140 ms away from all of them.
I found a few NTP servers in the US zone that list mdrmo1 being less than 1 ms away:
I find this confusing. Maybe a mixup between Moldova (.md) and Maryland (MD)?
Do you happen to know the range of the monitor?
As it’s probably one of these. If we know the IP, we can be sure by tracing the route.
I don’t know the monitor’s IP address, but if the monitor’s network distance to some U.S. NTP server is less than one millisecond, the monitor is definitely in the United States and not in Eastern Europe.
For example, the closest monitors of 107.172.43.182 are:
mdrmo1 ???
cayyz1 Canada, Toronto
usdtw1 US, Michigan, Detroit
usmdw1 US, Illinois, Chicago
usewr1 US, New Jersey, Newark
usewr3 US, New Jersey, Newark
usbos1 US, Massachusetts, Boston
so I’d say with a high level of certainty that mdrmo1 is somewhere in northeastern U.S. or maybe in Canada.
Maybe the owner of this monitor could contact the pool management to get the monitor renamed, or alternatively, the pool management could contact the owner of the monitor for clarification. My goal was not to find out the exact location of this monitor server, but to point out that it is certainly not in Moldova. Pool management and/or the operator of that monitor can sort this out between themselves.
OK, I think I found the monitor’s IP address anyway. MaxMind says it’s at Buffalo, New York, United States.
It used to be in Moldova. The server hosting the monitor there had issues, so the registration was parked on another server in the expectation/hopes that the previous location would come back. It now has become clear it won’t, so the original monitor registration will be retired, and a new one set up for the server in Buffalo reflecting its location in the name (though I think that part is more convenience for server operators while the system doesn’t care about that and effectively only considers the RTT from thr monitor to respective servers in its algorithms, in line with people’s assessment pf that aspect and their conclusion).
Thanks for the information! It would have been neat to have a monitor node in Moldova, but sometimes things don’t work out the way we want.
I agree that the issue was entirely cosmetical, I just wasn’t sure of the background story.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.