[Filtering of NTP-access to swisstime.ethz.ch as of July 1st, 2013]

I'm forwarding this heads-up for the shutdown of the well-known NTP
server swisstime.ethz.ch on behalf of the ETH Zurich.

Alex:

You should also get this posted to the NTP.ORG community.

http://www.pool.ntp.org

Also a Usenet posting (who still uses that, right?) to
comp.protocols.time.ntp will also help get the word out.

Forwarded it to the ntp-pool list.

I wonder how long it will take before anybody actually updates their config.
I once pulled a stratum-2 out of the clocks.txt file - and was still seeing
several hundred unique hosts per hour poking the IP address for time - like over
a decade later.

There is a fair amount of on-topic traffic of recent vintage on that froup.

What is it about people that makes them free-load on services like NTP chimes and DNSBLS but refuse to stay in contact with(or at least contactable by) the providers when important stuff is pending?

Several generations of employees past the ones who made the settings to use
them, and nobody realizes or audits where they are pointed or what they
depend on.

It's on the Internet. Therefore it must be free.

(See also: TV programs who broadcast youtube videos)

- Matt

<http://pages.cs.wisc.edu/~plonka/netgear-sntp/>

Alex:

You should also get this posted to the NTP.ORG community.

http://www.pool.ntp.org

It's been marked as inactive since the end of last year
(http://support.ntp.org/bin/view/Servers/InactiveTimeServers). I
don't know if it was in the NTP pool, but I'm sure the ETH folks have
removed it from there as well if it was.

Would actually be interesting to get a brief update on how many of these
SNTP requests the Madison NTP server still gets.

At the time, Dave hypothesized that the affected devices would have a
half-life of about 5 years - so 10 years on, you would expect this to have
subsided to around 25% of the initially report rate. I wonder if that held
true?

Mike