On 23/02/17 10:38, Rob Janssen wrote: > > It depends on where the routing problems actually are. When the > problem is in some > transatlantic link, there is no issue for the server to be in European > pools.
Well, lets say you host a website. This website pays your bills. You have 1 monitoring system, and it says your website is down sometimes. So you blame the monitoring system, and install a second monitoring system on another ISP. This always reports site up. So you say `My website is up if either monitoring system thinks it is up`. Well, then you are wrong, because actually what you are saying is. `My website is up for half the internet, and down for half the internet` For most people, that is a problem. Some people can't get to your website. (ok, there are some truly crap ISPs around with naff connectivity, peering disputes, full ports, .... Can't be helped) Does this apply to the pool? To me, if a pool server is visible from half the internet, but not the other half. Somebody puts pool.ntp.org into their computer with an SNTP client. DNS gives them an inaccessible client. The time doesn't set. Their conclusion is `The NTP pool is broken` This is even though the same server might be serving other users fine. Tim _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
