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] Big latency change
- Previous message (by thread): [atlas] Big latency change
- Next message (by thread): [atlas] ICANN in El Segundo (US) has joined RIPE Atlas Anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wilfried Woeber
woeber at cc.univie.ac.at
Thu May 21 14:26:43 CEST 2015
I can see a similar change on the 3 Probes I have access to (1x V1 + 1 Anchor, close to each other, one on a different upstream). The maybe more interesting thing is that for 2 out of the 3, *after* the decrease of RTT, there were short bursts of RTT > than the previouse ~100+ : ~250ms and ~300ms. So, whatever the change was, it would be intersting to ask those folks if the change was intended or a side-effect of another event in the 'net... On 2015-05-15 18:28, Daniel Baeza (Red y Sistemas TVT) wrote: > Hi folks, > > How can I check what happened at 13:00 (Dont know if the time in my probe is UTC or UTC+2) of today in the a.root-servers.net? > > My latency with the a-root changed from 117 to 45ms and Im curious of what happened. > > I've took a look in the RIPEstat routing for the IP Address of the root server, and at the same time the BGP had changes, but there are too many AS involved I cant follow it. > > > Thanks in advance! FWIW, Wilfried
- Previous message (by thread): [atlas] Big latency change
- Next message (by thread): [atlas] ICANN in El Segundo (US) has joined RIPE Atlas Anchors
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]