This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Incrementing LTS For probe 6106
- Previous message (by thread): [atlas] Incrementing LTS For probe 6106
- Next message (by thread): [atlas] IPv4-only Anchors Now Supported
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Aug 9 17:31:53 CEST 2016
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
- Previous message (by thread): [atlas] Incrementing LTS For probe 6106
- Next message (by thread): [atlas] IPv4-only Anchors Now Supported
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]