On 2016/08/09 17:21 , Clinton Work wrote:

Probe 6106 has an LTS value of at least 187450 and it continues to grow.

The code that manages the lts value does a consistency check with the time on the controller. The problem with the anchor is that the connection to the controller (in Amsterdam) is slow enough that the consistency check fails. I don't know why. The latency to Amsterdam doesn't seem exceptionally high. See https://stat.ripe.net/m/widget/atlas-ping-measurements#w.mode=condensed&w.measurement_id=2030&w.probe_id=6106 Philip